Looks like the last workunit has timed out or been timed out.

Still got 13 in my Valid list, and the SSP is still broken.

My wingperson for my last valid task will be timed out in 15hrs, but IIRC a few here said that they had 1's that would also meet that fate on the 26th.

Cheers.

I still have 75 valid showing on my account, but I went through every one of the first page tasks and all have the last replication task number timed out in red. Looks like it is just a matter of firing up the database and deleting those last tasks showing. If and when that happens . . . . who knows.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Cross posting from the BOINC website:
Tried to get on the SETI website but got this instead from my Firefox browser:

This Connection is Untrusted

You have asked Firefox to connect securely to setiathome.berkeley.edu, but we can't confirm that your connection is secure.

Technical Details:
setiathome.berkeley.edu uses an invalid security certificate. The certificate is not trusted because it is self-signed.

Edit -- Was able to get on by overriding the invalid certificate issue.

---

Not specific browser related. Getting the same with Chromium.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Cross posting from the BOINC website:
Tried to get on the SETI website but got this instead from my Firefox browser:

This Connection is Untrusted

You have asked Firefox to connect securely to setiathome.berkeley.edu, but we can't confirm that your connection is secure.

Technical Details:
setiathome.berkeley.edu uses an invalid security certificate. The certificate is not trusted because it is self-signed.

Edit -- Was able to get on by overriding the invalid certificate issue.

That's odd...

Take a look at WHAT certificate you've been given?...

Checking on Firefox here just now I get:

Site:        setiathome.berkeley.edu
Owner:       This web site does not supply ownership information.
Verified by: Let's Encrypt
Expires:     15 October 2020

Click on the padlock symbol on the address bar, then the arrow on the right of "connection secure" and then more info...

This is very curious...


Stay safe!
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)

Yep, same here with Edge (Chromium based).

Your connection isn't private
Attackers might be trying to steal your information from setiathome.berkeley.edu (for example, passwords, messages or credit cards).
NET::ERR_CERT_AUTHORITY_INVALID
This server couldn't prove that it's setiathome.berkeley.edu; its security certificate is not trusted by your computer's operating system. This may be caused by a misconfiguration or an attacker intercepting your connection.

Continue to setiathome.berkeley.edu (unsafe)

Edit- and it makes using the forums an extreme PITA.


Edit- looking at the certificate's properties, i came across this.

This CA Root certificate is not trusted because it is not in the Trusted Root Certification Authorities store.

---

Grant
Darwin NT

Looks like the last workunit has timed out or been timed out.

Still got 13 in my Valid list, and the SSP is still broken.

My wingperson for my last valid task will be timed out in 15hrs, but IIRC a few here said that they had 1's that would also meet that fate on the 26th.

Cheers.

There are 3 here for the 26-7 https://setiathome.berkeley.edu/results.php?hostid=8833115&offset=0&show_names=0&state=1&appid=

Tried to get on the SETI website but got this instead from my Firefox browser:

This Connection is Untrusted
You have asked Firefox to connect securely to setiathome.berkeley.edu, but we can't confirm that your connection is secure.
Technical Details:
setiathome.berkeley.edu uses an invalid security certificate. The certificate is not trusted because it is self-signed.

Edit -- Was able to get on by overriding the invalid certificate issue.

. . Exactly the same here, apparently the self created SETI site certificates are no longer acceptable to Firefox.

. . It's a good thing we trust them isn't it :)

Stephen

Tried to get on the SETI website but got this instead from my Firefox browser:

This Connection is Untrusted
You have asked Firefox to connect securely to setiathome.berkeley.edu, but we can't confirm that your connection is secure.
Technical Details:
setiathome.berkeley.edu uses an invalid security certificate. The certificate is not trusted because it is self-signed.

Edit -- Was able to get on by overriding the invalid certificate issue.

. . Exactly the same here, apparently the self created SETI site certificates are no longer acceptable to Firefox.

. . It's a good thing we trust them isn't it :)

Seriously... You shouldn't do...

Such bad certificates silliness usually indicates a DNS misdirection to a 'spoof' site, or that your service provider is doing a sneaky intercept of your connection for nefarious (Marketing?) purposes...


On this occasion, we've had word that is was a problem of the s@h servers getting physically moved around and reorganized and the certificate updates hadn't yet caught up with the new moves.

Good catch by the web browsers!


Keep searchin',
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)

On this occasion, we've had word that is was a problem of the s@h servers getting physically moved around and reorganized and the certificate updates hadn't yet caught up with the new moves.

And it seems to have fixed itself now, as both my phone and Chrome on my system no longer come up with the warning screen. Which leaves... why is Chrome downloading a proxy script from this site?

On this occasion, we've had word that is was a problem of the s@h servers getting physically moved around and reorganized and the certificate updates hadn't yet caught up with the new moves.

And it seems to have fixed itself now

Yay!

---

Grant
Darwin NT

They HAVEN'T fixed the Beta Site Certificate(s), yet...


TL

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

You have to wonder, why keep a beta site in the air of a project that's in hibernation? It just gobbles up electricity.

You have to wonder, why keep a beta site in the air of a project that's in hibernation? It just gobbles up electricity.

There are decades of development history on the Beta website forums.
There also used to be a social community there as well as here.

Some of the Beta members used to avoid the SETI Main forums.

The site also probably runs on the same hardware as SETI Main.

It might be useful if Eric could do the same RAC trick that he did here to allow posting in the Beta forums again.

It might be useful if Eric could do the same RAC trick that he did here to allow posting in the Beta forums again.

As long as no one emails or PMs him about it, how is he to know?

https://setiweb.ssl.berkeley.edu/ the alternate URL for this site is still broken too.

I wonder if it was Eric or D Aderso that broke the websites :-)

You have to wonder, why keep a beta site in the air of a project that's in hibernation? It just gobbles up electricity.

There are decades of development history on the Beta website forums.
There also used to be a social community there as well as here.

Some of the Beta members used to avoid the SETI Main forums.

The site also probably runs on the same hardware as SETI Main.

It might be useful if Eric could do the same RAC trick that he did here to allow posting in the Beta forums again.

The Cafe is the only section of Beta where you need RAC to post.

And even after all that time, the last of my Valids haven' been cleared.

Appears that they have been waiting for all tasks in a WU to get to deadline (either by completing task or by missing deadline) before taking off list, even though task marked as valid. My last WU (3944583333) has 3 valid tasks, including mine. However, 4th task is waiting for 7/24 deadline by an anonymous host which hasn't checked in since 6/15/20. Pretty sure won't make deadline!!

Well, I find myself wrong. The above task 8703556929 is now past deadline and is still considered "in progress." This is my last Seti WU. :-(

Also, my BOINC manager is trying frantically to connect to S@H about every 5 minutes, without success (of course). My Event Log keeps showing first:

7/24/2020 11:50:56 PM | SETI@home | Sending scheduler request: To fetch work.
7/24/2020 11:50:56 PM | SETI@home | Requesting new tasks for Intel GPU
7/24/2020 11:50:58 PM | SETI@home | Scheduler request failed: HTTP file not found
7/24/2020 11:52:28 PM | SETI@home | Fetching scheduler list
7/24/2020 11:52:30 PM | SETI@home | Master file download succeeded
7/24/2020 11:52:35 PM | SETI@home | Sending scheduler request: To fetch work.
7/24/2020 11:52:35 PM | SETI@home | Requesting new tasks for Intel GPU
7/24/2020 11:52:37 PM | SETI@home | Scheduler request failed: HTTP file not found

And then continuously repeating:

7/25/2020 12:03:10 AM | SETI@home | Sending scheduler request: To fetch work.
7/25/2020 12:03:10 AM | SETI@home | Requesting new tasks for Intel GPU
7/25/2020 12:03:12 AM | SETI@home | Scheduler request failed: HTTP file not found

In intervals starting at about 2 mins. apart and now about 20 mins. apart. No doubt similar hijinks will continue through the weekend now.

---

7/25/2020 12:03:10 AM | SETI@home | Sending scheduler request: To fetch work.
7/25/2020 12:03:10 AM | SETI@home | Requesting new tasks for Intel GPU
7/25/2020 12:03:12 AM | SETI@home | Scheduler request failed: HTTP file not found

The actual reply message we get back from the server is

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL was not found on this server.</p>
<hr>
<address>Apache/2.4.29 (Ubuntu) Server at setiathome.ssl.berkeley.edu Port 443</address>
</body></html>

- the 'requested url' being

25/07/2020 12:17:38 | SETI@home | [http] [ID#1] Sent header to server: POST /sah_cgi/cgi HTTP/1.1

That's quite a big SNAFU. I've sent an email to as many of the staff as I think might be in a position to help - not least to say "You're wasting money" [that should get their attention!]. A simple 'Back off for 24 hours - we're hibernating' would save a lot of bandwidth.

. . Exactly the same here, apparently the self created SETI site certificates are no longer acceptable to Firefox.
. . It's a good thing we trust them isn't it :)

Seriously... You shouldn't do...
Such bad certificates silliness usually indicates a DNS misdirection to a 'spoof' site, or that your service provider is doing a sneaky intercept of your connection for nefarious (Marketing?) purposes...
On this occasion, we've had word that is was a problem of the s@h servers getting physically moved around and reorganized and the certificate updates hadn't yet caught up with the new moves.
Good catch by the web browsers!
Keep searchin',
Martin

. . Normally if I got a message like that with any other site I would run like my tail was on fire. But as I said, knowing the nature of S@H and trusting them I (and others) persevered :).

Stephen

:)