Questions and Answers :
Unix/Linux :
Can't connect to setiathome.berkeley.edu with boinc
Message board moderation
Author | Message |
---|---|
agcarver Send message Joined: 14 May 99 Posts: 21 Credit: 150,823 RAC: 0 ![]() |
I'm running the Solaris version of Boinc behind a firewall. The firewall has both an HTTP proxy and a SOCKS4 proxy available. I've set the environment variables to fit plus I've also tried to edit the client_state.xml file for the appropriate settings but boinc constantly fails: 2005-10-22 13:16:33 [http://setiweb.ssl.berkeley.edu/] Master file fetch failed 2005-10-22 13:16:33 [http://setiweb.ssl.berkeley.edu/] Master file fetch failed BOINC couldn't get main page for http://setiathome.berkeley.edu/. Please check the URL and try again. DNS lookups for regular sites seem to work just fine. I was able to do a lookup on www.berkeley.edu and have it come back with an IP address. But, DNS lookups for any of the setiathome address fail silently through the firewall (they work fine from the firewall computer). I've also tried manually entering the IP addresses into the local hosts file to bypass the DNS issue. Even without DNS, there's no evidence of boinc attempting to use the proxies (their logs show no connection attempts). Ideas? Suggestions? |
Zardoz Send message Joined: 21 Nov 03 Posts: 13 Credit: 17,383,109 RAC: 0 ![]() |
Boinc should be picking up the proxy settings you've put into your client_state.xml file. When you modified the file with your proxy information did you remember to ADD the line telling Boinc to start using a proxy; i.e., "<use_http_proxy/>"? The proxy section of the client_state file should look something like this: <proxy_info> <use_http_proxy/> <socks_version>4</socks_version> <socks_server_name></socks_server_name> <socks_server_port>80</socks_server_port> <http_server_name>192.168.111.111</http_server_name> <http_server_port>8888</http_server_port> <socks5_user_name></socks5_user_name> <socks5_user_passwd></socks5_user_passwd> <http_user_name>myusername</http_user_name> <http_user_passwd>mypassword</http_user_passwd> </proxy_info> ...with the obvious changes to the proxy server names and port numbers for your environment. Hope this is of some help... ==> dave |
©2025 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.