read this message from Evan which elaborates on DEK's solution.

another solution is to just let boinc manager keep trying to connect to the old location and eventually it will get tired of that and go look for the master file which contains the new server address.

I recommend letting your client deal with it. It might take some time before the client decides it has to reread the master url but you will not have to do anything.

the scheduler url changed from:

https://boinc.bakerlab.org/rosetta_cgi/cgi

to

http://srv4.bakerlab.org/rosetta_cgi/cgi

THE ONLY DIFFERENCE IS 'boinc' changed to 'srv4'

I recommend letting your client deal with it. It might take some time before the client decides it has to reread the master url but you will not have to do anything.

True. I visited one location where I've set a machine up and found that it had sorted itself out and was running quite merrily without the owner flapping or panicking like me. Ho hum...

---

I found the easiest way round this was to detach from the project and then re-attach (as if it was a new project).

---

Before following Kevbert's advice, you will want to consider your existing complete tasks. The client will find the new scheduler after about 10 retries, so the problem will take care of itself. But if you reset the project, you are dumping all of your completed work that has not been reported yet. You also have to download all the initial files again.

---

Rosetta Moderator: Mod.Sense