The web site is back! At least the forums.

. . Yay!!

Stephen

:)

It's Tuesday
"Can't establish connection"

It's Tuesday
"Can't establish connection"

Yes it's Tuesday again according to my calendar also.
Will it take another week for it rise up again?

To detect moving objects you take multiple images over time of the same sky, compare them using a blink comparater and see witch dote moves.
I tried their sight, cant make heads or tails of it.
JP

---

For a moment, I thought today was Tuesday, until I checked the calendar.
Now this is weird. It's back. However I did have the maintenance message up for 4 min.

For a moment, I thought today was Tuesday, until I checked the calendar.

It was a space time lag warp.

For a moment, I thought today was Tuesday, until I checked the calendar.

It was a space time lag warp.

That space time warp is back! Must be Tuesday again (UTC TIME):
SETI@home is temporarily shut down for maintenance. Please try again later.

Edit 02:47 UTC ... And just like that it's magically back up.

Could it be he who shall remain unnamed here tinkering with the SETI servers?

Edit#2 @03:12 UTC down again. And back up at 03:16 UTC.

Yoyi's are more predictable than the SETI servers right now.

For a moment, I thought today was Tuesday, until I checked the calendar.

It was a space time lag warp.

That space time warp is back! Must be Tuesday again (UTC TIME):
SETI@home is temporarily shut down for maintenance. Please try again later.

Edit 02:47 UTC ... And just like that it's magically back up.

Could it be he who shall remain unnamed here tinkering with the SETI servers?

Edit#2 @03:12 UTC down again. And back up at 03:16 UTC.

Yoyi's are more predictable than the SETI servers right now.

Clearly I shall have to revert turning the radio on next time I need to find out what day it is.

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.

Both Seti main, and Beta have now screwed up certificates. It's .pvt (private) certificates issued by centurion.bl.pvt
CN = centurion.bl.pvt

.bl is/was meant as a St.Barthelemy domain, and .pvt is meant for a private Intranet.
However it's unassigned still.

Introduced 21 September 2007
TLD type Country code top-level domain
Status Unassigned
Registry None
Sponsor None
Intended use Entities connected with Saint Barthélemy
Actual use Not available for use
Registration restrictions Not available for registration

Someone have done something.....

I would never override the invalid certificate warning.

I think someone really f* up.
Centurian is the host server name for the SETI website.

Domintools IP resolver shows:

Resolve Host centurion-10g.ssl.berkeley.edu

Firefox says security threat on the site. Not just a expired cert, but for a different domain! Have they been hijacked?

The invalid private certificate means that it takes three clicks to get anywhere on Main.

And I'm getting a 404 Not Found for the Beta front page.

I just wish they'd given us some inkling of what they're trying to achieve.

They worked years with a self signed certificate, maybe they tried going back to one. Anyone mailed David or Eric?

I'm keeping my powder dry with David, waiting for him to finish the BOINC v7.16 release process.

27 days and counting since he was recorded saying "within the next month".

Do you take into account that he doesn't work weekends?

But he does! Sunday night is his prime code bug writing schedule.

They worked years with a self signed certificate.

I think that was before the browsers beefed up their security warnings.

But he does! Sunday night is his prime code bug writing schedule.

I read that as "crime code", then reread it and read that again. :-D

Edit: I emailed Eric and David, let's see if someone answers.

Eric answers:

We're in the process of swapping web servers and the cert generation hasn't caught up yet. I expect that it will be in place in the next day or so.

So just don't go there...