Difference between revisions of "Project communication failed: attempting access to reference site. Access to reference site succeeded - project servers may be temporarily down."
From BOINC Wiki
(Saving FAQ 288) |
(adding table) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | Project communication failed: attempting access to reference site. Access to reference site succeeded - project servers may be temporarily down. | + | '''Project communication failed: attempting access to reference site.''' |
| + | |||
| + | '''Access to reference site succeeded - project servers may be temporarily down.''' | ||
| + | |||
This can mean one of a few things: | This can mean one of a few things: | ||
| − | |||
| − | |||
| − | |||
| − | The reference site that BOINC calls upon is www.google.com. Why Google? Because Google is always up. So if BOINC finds that it can reach Google but not the project, | + | * The project server is down. Nothing you can do about it, except wait until it's back up. If the project's website is available for browsing, check the front-page news or message boards for information about outages. |
| + | * The project server is up, but your internet connection isn't reaching it. This is called a 'black hole server', where the line you're following goes into a server node on the Internet and doesn't come out, usually because the node is down. Updating to a newer version of BOINC might help, especially if you're still using v4.x or 5.4.x. Quitting and relaunching BOINC may refresh its routing information; failing that, try rebooting the computer. | ||
| + | * The client is being blocked by a firewall or proxy, one that does allow pings through on port 80, but not much else by way of communication. Make sure BOINC has permission to go through the firewall and, if you're behind a proxy, that BOINC is set up to use the correct proxy address. | ||
| + | |||
| + | |||
| + | The reference site that BOINC calls upon is www.google.com. Why Google? Because Google is always up. So if BOINC finds that it can reach Google but not the project, it's not the client's fault and the Internet connection itself is OK. | ||
| + | |||
| + | |||
| + | |||
| + | {| class="wikitable" style="text-align: center;" | ||
| + | ! Original writer | ||
| + | ! Original FAQ | ||
| + | ! Date | ||
| + | |- | ||
| Jorden | | Jorden | ||
| − | | | + | | [http://boincfaq.mundayweb.com/index.php?language=1&view=288 288] |
| − | + | | 12-02-2008 | |
| − | + | |- | |
| − | + | |} | |
| − | |||
| − | |||
| − | |||
| − | | | ||
| − | | | ||
| − | | | ||
Latest revision as of 15:03, 29 August 2016
Project communication failed: attempting access to reference site.
Access to reference site succeeded - project servers may be temporarily down.
This can mean one of a few things:
- The project server is down. Nothing you can do about it, except wait until it's back up. If the project's website is available for browsing, check the front-page news or message boards for information about outages.
- The project server is up, but your internet connection isn't reaching it. This is called a 'black hole server', where the line you're following goes into a server node on the Internet and doesn't come out, usually because the node is down. Updating to a newer version of BOINC might help, especially if you're still using v4.x or 5.4.x. Quitting and relaunching BOINC may refresh its routing information; failing that, try rebooting the computer.
- The client is being blocked by a firewall or proxy, one that does allow pings through on port 80, but not much else by way of communication. Make sure BOINC has permission to go through the firewall and, if you're behind a proxy, that BOINC is set up to use the correct proxy address.
The reference site that BOINC calls upon is www.google.com. Why Google? Because Google is always up. So if BOINC finds that it can reach Google but not the project, it's not the client's fault and the Internet connection itself is OK.
| Original writer | Original FAQ | Date |
|---|---|---|
| Jorden | 288 | 12-02-2008 |
