Hi,

as reported in this message on WCG forums , my host, with BOINC 6.12.34 installed, can't connect to WCG, every communication attempt resulting in a "HTTP error 0" message.

I tried uninstalling BOINC 6.12.34 and reverting to BOINC 6.10.60 and everything with WCG went back OK.

Then I uninstalled BOINC 6.10.60 and reinstalled 6.12.34 and the issue reappeared.

I also tried with BOINC 6.13.1 (beta) but this didn't fix the issue.

Currently, I reverted once again to 6.10.60, but it looks like the issue is related to BOINC 6.12.34, WCG and (possibly) the way I communicate to the Internet, though I tried with my standard Internet proxy and TOR, none of which gives me problems with other projects.
Also, I don't get any such issue with other BOINC-projects while running BOINC 6.12.34.

I posted this message on WCG forums as well

Bye

darkpella

---

Hello,
i have the same problem !

Any news to fix this issue ? I have bunch of tasks done only waiting to be sent... If i downgrade to 6.10.60 then i cannot see any tasks in my system at all. So it doesn't work. And 6.13.1 doesn't fix this issue.

Can anyone who ran into this problem with 6.12.34 test if 6.12.38 is still doing it? Available for Linux, Windows and Mac at this download list.

---

If i downgrade to 6.10.60 then i cannot see any tasks in my system at all. So it doesn't work. And 6.13.1 doesn't fix this issue.

That proves 6.13. works as it should. It's changed your client_state.xml file exactly as it says it will in INCOMPATIBILITY WARNING FOR UPCOMING 6.13 BUILDS thread.

As for the "HTTP error 0 with World Community Grid and BOINC 6.12.34" problem, the solution is posted here on the WCG forums.

Don't know whether reverting to 6.12.33 can be taken as a solution overall, anything starting form 6.12.34 won't simply work with WCG and proxies.

darkpella

---

ive just upgraded to 7.0.25, after having to stay on 6.12.33 to get comms, this version seems to have the same problem any fixes?

---

ive just upgraded to 7.0.25, after having to stay on 6.12.33 to get comms, this version seems to have the same problem any fixes?

An apparently successful workround is posted at

https://secure.worldcommunitygrid.org/forums/wcg/printpost_post,372940

just tried it and it doesnt work:

17/04/2012 13:26:39 | | Project communication failed: attempting access to reference site

17/04/2012 13:26:39 | World Community Grid | Scheduler request failed: Failure when receiving data from the peer

17/04/2012 13:26:59 | | BOINC can't access Internet - check network connection or proxy configuration.

---

A couple of problems with the post at WCG:

1. It doesn't say for instance that you need to exit BOINC (BOINC Manager->Advanced view->File->Exit, check "Quit running tasks when exiting the Manager" (or similar words)->OK).
2. It also doesn't say that the file you're downloading is a ZIP archive file, a compressed file which needs to be decompressed before the file inside the archive is available for use. BOINC won't unzip it for you.

So, did you just drop the *.zip file in your BOINC programs directory and hoped for the best, or did you use WinZip, WinRAR, 7-zip or Windows its own archive decompresser, to get a file called libcurl.dll out of the archive and did you put that one in the BOINC programs directory, overwriting the original one?

The default directory where BOINC will install its executables to is:
Windows 32bit: C:\PROGRAM FILES\BOINC\
Windows 64bit: C:\PROGRAM FILES (x86)\BOINC\
Linux: wherever you are unpacking it/BOINC/
Macintosh: /Applications/BOINC/

After you're done, restart BOINC (Windows: Start->(All) Programs->BOINC->BOINC Manager).

---

hello.

i exited boinc closing tasks i then unzipped the new dll and replaced it. i then restarted the machine just for good measure.

---

Update to 7.0.26, links available from the last post in the change log thread.

---

tried 7.0.26 and got the same problem. were using microsoft TMG and websense. if i knew which ip/web address boinc was trying to access the world community servers with, i could check our filter.

---

any ideas? or should i go back to the old client 6.12.33?

p.s. ive 7.0.27 and same problem. is it a change in the way boinc authenticates with proxies?

---

There is no change between BOINC 6.12 and 7.0 on how to communicate with proxies. However, 7.0.27 does use the newer libCurl.

In any case, we have too little information to be able to help you. You could try to run with the <http_debug/> and <http_xfer_debug/> tags in cc_config.xml
Or just try to force authentication through the same cc-config.xml file, with the <force_auth>basic | digest | gss-negotiate | ntlm</force_auth> tag.

Example given:

<cc_config>
<log_flags>
<http_debug>1</http_debug>
<http_xfer_debug>1</http_xfer_debug>
</log_flags>
<options>
<force_auth>ntlm</force_auth>
</options>
</cc_config>

---

where does the output go?

---

In the Event Log (CTRL+SHIFT+E), and stdoutdae.txt in the data directory.

---

ill send this as a pm.

---

The example cc_config.xml I gave was really an example. You will have to change the authentication forcing if it uses something different than NTLM.
As now you end at:

21-May-2012 14:38:51 [World Community Grid] [http] [ID#1] Received header from server: HTTP/1.1 407 Proxy Authentication Required ( Access is denied. )

If not sure, don't use authentication forcing:

<cc_config>
<log_flags>
<http_debug>1</http_debug>
<http_xfer_debug>1</http_xfer_debug>
</log_flags>
<options>
</options>
</cc_config>

As stated in the log, WCG lives at 172.16.222.51
WCG uses a HTTPS address which requires that TCP port 443 is accessible.

---

our system does use NTLM.

---