Robi wrote:

just FYI:
http://setiathome.ssl.berkeley.edu/tech_news.html

[snip]

So, if you are getting such errors, check your URL - make sure that
the beginning is:
http://setiathome2.ssl.berkeley.edu
and not
http://setiathome.ssl.berkeley.edu.

That doesn't solve the problem, no matter if setiathome or setiathome2, the
only thing visible is a Server error.

They care, but they are also working on BOINC and that leaves them
little time for these fixes.

I for myself share the opinion lots of people posting in the seti forum
have: we (the users) donate them CPU power for free, so at least they should
care for the only motivation they offer for the users: the stats. Working on
a new project is certainly ok but that's no excuse for leaving a server of a
current active project unuseable for several days.

Of course it's always possible for a server to fail, but letting a web
server fail for several days shows a very very bad light on the responsible
staff and the amount of care they offer for the system...

Benjamin