I cannot attach a project. I get the following error measage when I enter http://setiathome.berkeley.edu.

The URL you supplied is not that of a BOINC-based project. Please check the URL and try again.

I have tried several different URL with negitive results. Suggestions please

---

Please post this in the Help Desk forums at the Seti Forums.

Post what version of Boinc you use, what OS you use, what version of firewall if necessary. Also tell what specific error message you come across.

---

Please post this in the Help Desk forums at the Seti Forums.

Post what version of Boinc you use, what OS you use, what version of firewall if necessary. Also tell what specific error message you come across.

O/S is XP Professional
Boinc 5.2.13
I have no idea of what the network architecture is. There is a proxy server (corporate network) but I did not have any problem with SETI@Home Classic.

---

Please post this in the Help Desk forums at the Seti Forums.

Post what version of Boinc you use, what OS you use, what version of firewall if necessary. Also tell what specific error message you come across.

"The URL you supplied is not that of a BOINC-based project. Please check the URL and try again" is the error message.

---

You still need to be posting this SETI problem on the SETI boards, and not here...

---

You still need to be posting this SETI problem on the SETI boards, and not here...

This is not confined to SETI, all of the project URL cause the same error

---

This is not confined to SETI, all of the project URL cause the same error

That pretty much means it is an issue in your proxy setup, local or corporate firewall, etc., that BOINC is not able to get through to any of the project servers.

Jord? Tony? Other network gurus?

---

The URL you supplied is not that of a BOINC-based project. Please check the URL and try again

I've had a look at the client GUI source and this message is generated for any failure to connect to the project, not just an incorrect response from the other end. It also covers things like DNS lookup failures and blocking by a proxy or firewall, so Bill is on the right line. Not being able to attach to any project definitely points towards proxy or firewall blocking.

This seems to be causing a lot of grief and really ought to be changed to generate a different error for networking problems.

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

Thanks all for your input. I'll take this up with my network guys.

---

I am having the same problem. The slight difference is that my machine has the problem when it is attached to the corporate network and when it is on my home network where there is no proxy. Could the issue be with how BOINC tries to use a proxy that may or may not exist? I do not have to make any changes to my browser settings when I connected to my home network to successfully browse the internet. Any new suggestions?

---

The other thing this might be related to is a HTTP 500 error condition I've been investigating on the CPDN coupled model spinup project.

If BOINC version 5.2.* receives an HTTP 100-contine intermediate response to a request it currently closes the socket without waiting for the subsequent HTTP 200-OK message with the scheduler's reply. I've submitted a change to fix this.

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer