Maybe I'm going senile, but I am thoroughly confused over the correct URL for the now-public Boinc-based S@H.

As a past S@H Classic user, and a Boinc Beta tester, I "activated" my account on the newly set up S@H project, and received an email telling me to attach to http://setiboinc.ssl.berkeley.edu/sah.

This does indeed seem to point to the right place - where I am posting this msg.

The front page News section of this web site states, however:
"June 22, 2004
The URL of this project is http://setiathome.berkeley.edu. If you joined using a different URL, please detach and attach to this URL".

If I detach from here and re-attach to this setiathome.berkeley.edu URL, the initial attachment seems to work OK, but seems to point to the old Classic web site.

Am I mis-understanding things, or is there a contradiction between my email and this News statement?

This is the way that things will work until S@H1 is terminated. You could use the old link, http;//setiboinc.ssl.berkeley.edu/sah/, for a while, but that link will stop giving work sometime.

jm7

BOINC couldn't get main page for http://setiboinc.ssl.berkeley.edu/sah/.
Please check the URL and try again.



Same result for http://setiathome.berkeley.edu and http://setiweb.ssl.berkeley.edu.

So what is the correct URL?

> BOINC couldn't get main page for http://setiboinc.ssl.berkeley.edu/sah/.
> Please check the URL and try again.
> Same result for http://setiathome.berkeley.edu and
> http://setiweb.ssl.berkeley.edu.
>
> So what is the correct URL?
>

http://setiathome.berkeley.edu is the correct URL for the SETI@home BOINC project, but http://setiboinc.ssl.berkeley.edu/sah/ may work too.

I would say you should check your firewall or proxy settings. This is a typical message if something is blocking yout way to the project URL.

Greetings from Bremen/Germany

Jens Seidler (TheBigJens)

I had the same problem of getting URL and ID errors using http://setiathome.berkeley.edu, so I tried the above option of http://setiboinc.ssl.berkeley.edu/sah/ and seems to be working now.
See how it goes from here.....

Andrew.......

> I had the same problem of getting URL and ID errors using
> http://setiathome.berkeley.edu, so I tried the above option of
> http://setiboinc.ssl.berkeley.edu/sah/ and seems to be working now.
> See how it goes from here.....
>
> Andrew.......
>
>
The correct URL is http://setiathome.berkeley.edu . The setiboinc URL will work now but will eventually be deactivated. If you attached useing the setiboinc URL you will have to detach and reattach useing http://setiathome.berkeley.edu eventually. Be carefull when attaching that you do not include leading or trailing spaces these can cause some annoying problems.


John Keck
BOINCing since 2002/12/08

> > I had the same problem of getting URL and ID errors using
> > http://setiathome.berkeley.edu, so I tried the above option of
> > http://setiboinc.ssl.berkeley.edu/sah/ and seems to be working now.
> > See how it goes from here.....
> >
> > Andrew.......
> >
> >
> The correct URL is http://setiathome.berkeley.edu . The setiboinc URL will
> work now but will eventually be deactivated. If you attached useing the
> setiboinc URL you will have to detach and reattach useing
> http://setiathome.berkeley.edu eventually. Be carefull when attaching that you
> do not include leading or trailing spaces these can cause some annoying
> problems.
>
>
John Keck
> BOINCing since 2002/12/08
The setiboinc URL will no longer work. You must attach with http://setiathome.berkeley.edu now.


John Keck
BOINCing since 2002/12/08

> > > I had the same problem of getting URL and ID errors using
> > > http://setiathome.berkeley.edu, so I tried the above option of
> > > http://setiboinc.ssl.berkeley.edu/sah/ and seems to be working now.
> > > See how it goes from here.....
> > >
> > > Andrew.......
> > >
> > >
> > The correct URL is http://setiathome.berkeley.edu . The setiboinc URL
> will
> > work now but will eventually be deactivated. If you attached useing the
> > setiboinc URL you will have to detach and reattach useing
> > http://setiathome.berkeley.edu eventually. Be carefull when attaching
> that you
> > do not include leading or trailing spaces these can cause some annoying
> > problems.
> >
> >
John Keck
> > BOINCing since 2002/12/08
> The setiboinc URL will no longer work. You must attach with
> http://setiathome.berkeley.edu now.
>
>
John Keck
> BOINCing since 2002/12/08
>

I am getting similar problems. The first thing I did was reset the project and attempt to upgrade. No luck. BTW, I am using http://setiathome.berkley.edu for the project. I detached and then retyped this in to make sure it wasn't an error. No luck. i then reset it, and tried to update several more times with no luck. I turned off the Windows XP SP2 firewall, and still had no luck after a restart and several update attempts. The firewall allows exceptions for boinc_gui. What is wrong? Is the project down? I keep getting no work messages. I have version 3.19.

Okay. First off, I misspelled something. I am connected to http://setiathome.berkeley.edu/ ALso, I got a new message when I hit update:
http://setiathome.berkeley.edu/ - 2004-08-27 20:36:54 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
http://setiathome.berkeley.edu/ - 2004-08-27 20:47:47 - General preferences have been updated
--- - 2004-08-27 20:47:47 - General prefs: from SETI@home (last modified 2004-08-27 20:20:17)
--- - 2004-08-27 20:47:47 - General prefs: no separate prefs for home; using your defaults
SETI@home - 2004-08-27 20:47:47 - Project prefs: no separate prefs for home; using your defaults
SETI@home - 2004-08-27 20:47:47 - Started download of setiathome_3.08_windows_intelx86.exe
SETI@home - 2004-08-27 20:47:47 - Started download of better_banner.jpg
SETI@home - 2004-08-27 20:47:50 - Finished download of better_banner.jpg
SETI@home - 2004-08-27 20:47:50 - Approximate throughput 2482.000000 bytes/sec
SETI@home - 2004-08-27 20:47:50 - Started download of setiathome_3.08_windows_intelx86.pdb
SETI@home - 2004-08-27 20:48:04 - Finished download of setiathome_3.08_windows_intelx86.exe
SETI@home - 2004-08-27 20:48:04 - Approximate throughput 43609.457249 bytes/sec
SETI@home - 2004-08-27 20:48:04 - Started download of 04my04aa.2277.7392.259654.168
SETI@home - 2004-08-27 20:48:07 - Temporarily failed download of 04my04aa.2277.7392.259654.168
SETI@home - 2004-08-27 20:48:07 - Giving up on download of 04my04aa.2277.7392.259654.168: file was not found on server
SETI@home - 2004-08-27 20:48:07 - Unrecoverable error for result 04my04aa.2277.7392.259654.168_0 (file transfer error: couldn't get input files:
04my04aa.2277.7392.259654.168: file was not found on server
)
SETI@home - 2004-08-27 20:48:07 - Deferring communication with project for 1 minutes and 0 seconds
SETI@home - 2004-08-27 20:48:18 - Finished download of setiathome_3.08_windows_intelx86.pdb
SETI@home - 2004-08-27 20:48:18 - Approximate throughput 53494.971559 bytes/sec
--- - 2004-08-27 20:49:08 - Fewer active results than CPUs; requesting more work
SETI@home - 2004-08-27 20:49:08 - Requesting 26637 seconds of work
SETI@home - 2004-08-27 20:49:08 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-08-27 20:49:17 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-08-27 20:49:17 - Message from server: Not sending work - last RPC too recent: 91 sec
--- - 2004-08-27 20:49:17 - General prefs: from SETI@home (last modified 2004-08-27 20:20:17)
--- - 2004-08-27 20:49:17 - General prefs: using your defaults
SETI@home - 2004-08-27 20:49:17 - No work from project
SETI@home - 2004-08-27 20:49:17 - Deferring communication with project for 10 minutes and 0 seconds

> Okay. First off, I misspelled something. I am connected to
> http://setiathome.berkeley.edu/ ALso, I got a new message when I hit update:
> http://setiathome.berkeley.edu/ - 2004-08-27 20:36:54 - Sending request to
> scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
> http://setiathome.berkeley.edu/ - 2004-08-27 20:47:47 - General preferences
> have been updated
> --- - 2004-08-27 20:47:47 - General prefs: from SETI@home (last modified
> 2004-08-27 20:20:17)
> --- - 2004-08-27 20:47:47 - General prefs: no separate prefs for home; using
> your defaults
> SETI@home - 2004-08-27 20:47:47 - Project prefs: no separate prefs for home;
> using your defaults
> SETI@home - 2004-08-27 20:47:47 - Started download of
> setiathome_3.08_windows_intelx86.exe
> SETI@home - 2004-08-27 20:47:47 - Started download of better_banner.jpg
> SETI@home - 2004-08-27 20:47:50 - Finished download of better_banner.jpg
> SETI@home - 2004-08-27 20:47:50 - Approximate throughput 2482.000000
> bytes/sec
> SETI@home - 2004-08-27 20:47:50 - Started download of
> setiathome_3.08_windows_intelx86.pdb
> SETI@home - 2004-08-27 20:48:04 - Finished download of
> setiathome_3.08_windows_intelx86.exe
> SETI@home - 2004-08-27 20:48:04 - Approximate throughput 43609.457249
> bytes/sec
> SETI@home - 2004-08-27 20:48:04 - Started download of
> 04my04aa.2277.7392.259654.168

Everything above here is normal.

> SETI@home - 2004-08-27 20:48:07 - Temporarily failed download of
> 04my04aa.2277.7392.259654.168
> SETI@home - 2004-08-27 20:48:07 - Giving up on download of
> 04my04aa.2277.7392.259654.168: file was not found on server
> SETI@home - 2004-08-27 20:48:07 - Unrecoverable error for result
> 04my04aa.2277.7392.259654.168_0 (file transfer error: couldn't get input
> files:
> 04my04aa.2277.7392.259654.168: file was not found on server
> )

Indicates a failure to download the file

> SETI@home - 2004-08-27 20:48:07 - Deferring communication with project for 1
> minutes and 0 seconds

Not long enough on the backoff, S@H enforces a 10 minute quiet period between connection attampts.

> SETI@home - 2004-08-27 20:48:18 - Finished download of
> setiathome_3.08_windows_intelx86.pdb
> SETI@home - 2004-08-27 20:48:18 - Approximate throughput 53494.971559
> bytes/sec
> --- - 2004-08-27 20:49:08 - Fewer active results than CPUs; requesting more
> work
> SETI@home - 2004-08-27 20:49:08 - Requesting 26637 seconds of work
> SETI@home - 2004-08-27 20:49:08 - Sending request to scheduler:
> http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
> SETI@home - 2004-08-27 20:49:17 - Scheduler RPC to
> http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded

Normal for a starved CPU

> SETI@home - 2004-08-27 20:49:17 - Message from server: Not sending work - last
> RPC too recent: 91 sec

Too soon to connect

> --- - 2004-08-27 20:49:17 - General prefs: from SETI@home (last modified
> 2004-08-27 20:20:17)
> --- - 2004-08-27 20:49:17 - General prefs: using your defaults
> SETI@home - 2004-08-27 20:49:17 - No work from project
> SETI@home - 2004-08-27 20:49:17 - Deferring communication with project for 10
> minutes and 0 seconds

After this, the next connection should get work again.
>
>
>