I'm stuck at the moment, I can't upload and who knows what else doesn't work right now.
Have no clue on this error and it's only on my one machine. Any clues?

SETI@home - 2004-09-15 20:50:37 - Master file fetch failed

It means that one particular file could not be communicated with BOINC. The best advice I can give first to check the URL that you are using. It should be http://setiathome.ssl.berkeley/. It can be checked by inspecting the BOINC directory and looking for an account_*.xml file. The part that I specified with the wild card is the URL that you linked with.

If this is not the correct URL, you will have to either detach/attach or change all instances of the URL that you have with the correct one. There are file names, directory names and file contents to change. All of them in the BOINC folder.

If you did link with the correct file, the best I can tell you to do, is try again after a while. Check the scheduler status on the status page to see if it is up, if it is down, the connection will fail, and you will get yet another of these messages.

Yeah, no luck.
my URL is listed as http://setiathome.berkeley.edu and was working fine until this morning.
My two other boxes are working fine. Scheduler is up.
Altered the account_*.xml file with no luck so I tried detaching/attach and now Boinc "Can't get main page" from neither the setiathome.berkeley or setiathome.ssl.

Thanks for the help, but I'm flummoxed.

> Yeah, no luck.
> my URL is listed as http://setiathome.berkeley.edu and was working fine until
> this morning.
> My two other boxes are working fine. Scheduler is up.
> Altered the account_*.xml file with no luck so I tried detaching/attach and
> now Boinc "Can't get main page" from neither the setiathome.berkeley or
> setiathome.ssl.
>
> Thanks for the help, but I'm flummoxed.
>
If you only run S@H on this box and no other BOINC projects try an uninstall/install.

If you run multiple projects, detach from S@H. Delete all of the S@H files and directories (those with the S@H url in the name). Attach again.

If this fails, you may want to try the latest alpha release. However, these have a higher risk than those released to the other projects.