I had installed 5.2.2 a few days ago. was running ok. this morning computer needed to be rebooted and now BOINC MANAGER says 'connection failure' and does not show any information. I do not kwno state of BM before the reboot. This is something I normally do each Monday morning is to reboot all my systems. I can start BOINC manually and it runs.

There are times when the BOINC Manager gets started before the BOINC daemons are running, and you see this message. Depending on your OS and type of BOINC install, you may be able to manipulate which items start first, giving the daemon time to get going before the Manager starts. If the problem only happens once in a while (as it does to me on Windows) you can just ignore it, quit and restart the Manager when you want to see what's going on and see that it is disconnected. The daemons should be fine with or without the Manager. You can verify this with Activity Monitor, or top, or the task manager, depending on your OS.

Unless you're on a Mac, and are running the full GUI BOINC; then the Manager has to be running or the daemons won't be. But if you're on a Mac, you should be running 5.2.4 not 5.2.2. Linux I believe likewise, so I assume you're Windows...

---

There are times when the BOINC Manager gets started before the BOINC daemons are running, and you see this message. Depending on your OS and type of BOINC install, you may be able to manipulate which items start first, giving the daemon time to get going before the Manager starts. If the problem only happens once in a while (as it does to me on Windows) you can just ignore it, quit and restart the Manager when you want to see what's going on and see that it is disconnected. The daemons should be fine with or without the Manager. You can verify this with Activity Monitor, or top, or the task manager, depending on your OS.

BOINC has been running all day. If I try now to start BOINC Manager I get same error. Using Windows XP. As stated earlier I had to start BOINC manually i.e. It was not automatically stared at startup. This is the first time I have ever seen this, but I've only had 5.2.2 running for 2 or 3 days. Never saw this error before.

BOINC has been running all day. If I try now to start BOINC Manager I get same error. Using Windows XP. As stated earlier I had to start BOINC manually i.e. It was not automatically stared at startup. This is the first time I have ever seen this, but I've only had 5.2.2 running for 2 or 3 days. Never saw this error before.

Can you try to "Select computer" and choose "localhost", with a blank password? If it complains unable to connect then, someone with more 5.x knowledge will have to help... if it complains about the password, there is a gui_rpc_auth.cfg file that is initially set to contain a random password. You can either use that, change it to a blank, or (preferably, IMHO) put in something meaningful to you, and retry.

Not having seen exactly what you're seeing, that's about all I can come up with... but I'm sure someone else will jump in shortly!

---

What you say is exact: simply editing gui_rpc_auth.cfg to specify a meaningful password will do.
Blank passwords are sometimes tricky: some apps will not handle this correctly (is it a blank password, or is there no password ....), so I wouldnt do that

---

[quote]Can you try to "Select computer" and choose "localhost", with a blank password? If it complains unable to connect then, someone with more 5.x knowledge will have to help... if it complains about the password, there is a gui_rpc_auth.cfg file that is initially set to contain a random password. You can either use that, change it to a blank, or (preferably, IMHO) put in something meaningful to you, and retry.[/qoute]

There where no choices under select computer, only a blank box. All tabs in Boinc Manger where blank. I tried almost every menu choice but nothing changed.

I don't think I did anything with the password. It was working before with whatever was assigned. Also BoincView which has the password was able to communicate with Boinc Core Client during this time.

I found the cause.

I use Earthlink and had installed an update called Protection Manager on Friday probally. I think Boinc Manger was running at the time and I do not know if it stopped communication with Boinc Core Client or not. I usually use BoincView to monitor my hosts. Earthlink Protection Manager is a Virus/SpyWare/Firewall. I had the firewall set to disable because I use Windows XP firewall and did not have time to make all the correct entires, but I think I had made an entry in Earthlink Protection Manager for port 1043 to all RPC to work before I set it to disable. So it may have knocked out communication between those two then but whent unnoticed. Once I rebooted and the programs were starting up is when I noticed the problem. Even if I exited the program there was still no commuication between Boinc Manager and Boinc Core Client. I'm not sure what the conflict was, maybe the virus or spyware part of it. But upon totally uninstalling Earthlink Protection Manager the Boinc Manager went back to communication with BOINC Core Client. Problem has not repeated or appeared on any other host. I have not had time to try to re-install and play with the settings of that program to see exactly which part might be the cause.

I'll have to investigate how Boinc Manager communicates with Boinc Core Client.

You may have to open two ports in the system 1043, and 31xxx (can never remember the number) should be in the Wiki though ... I know I put it in there.

---

and 31xxx (can never remember the number)

Then remember pi, Paul: 31416. :)

---

Well, that is not good ... *I* remember Pi as

3.1415926535897

I found memorizing that much a bit more accurate .. so ...

should i tell them the port is what I remember it as? :)

---

Heh, well pi by approximation then. Since TCP allows port numbers to be in the range from 0 to 65535 only, any higher was impossible anyway. ;)

---

What you say is exact: simply editing gui_rpc_auth.cfg to specify a meaningful password will do.
Blank passwords are sometimes tricky: some apps will not handle this correctly (is it a blank password, or is there no password ....), so I wouldnt do that

You bet. I set up a network share to a PC with no password set for the administrator account. Whenever I started up the PC, it asked for the usercode/password for the share. It absolutely refused to accept that there was no password!

---

I'm having these same connection issues too.

Here's some background... Running 5.27, behind a router, using WinXP-Pro on both. One runs flawlessly the other has now developed connection issues. I have turned off the firewall and exited the client and restarted it and still the same. It was uninstalled, rebooted on both boxes and then a fresh install. It installed fine and chugged throughout the night running 4 projects but a restart has made it unable to connect again to itself. The other box is still running fine, even after some restarts and behind the same router.

This one, nadda. I tried to enter localhost with no password and had no luck. I opened up the gui_rpc_auth.cfg file and all that's in there is a long string, and no password visible. Entering that long string as the password for localhost also was a fail.

I've gone through the wiki but there is no error code for Connection Failed.

I installed this on my brothers computer too and after uninstalling the older version and completely throwing away the whole Boinc folder, it will not run there either. When I try to attach to new projects it gives me a proxy window I cannot get past. Again, turning on and off the firewall does no good and it's doing nothing at all now.

I've been running this since the first day of S@H1 beta and this gets more complicated with more difficulty and in installation than ever. I hope that my frustrations are only my own as I know anyone else would have given up by now.

Thank you for your help,

Tachyon

I upgraded to Bonic v 5.2.7 and now get the "connection failure" message. When I go to the task manager only bonicmgr.exe is running. If I manually start bonic.exe it will start working. Is there any way to fix this? I am running XP/Pro with no proxy.

---

OK, the disconnected issue means that the BOINC manager is not able to talk to the BOINC daemon. Whether or not you are uploading/downloading/crunching at this point must be determined with the task list (I do not rememeber how to bring this up for 95/98/me).

The usual reason for this problem is that the BOINC manager is starting and trying to talk before the BOINC daemon is ready to listen. The usual fix is to wait a minute or two and see if connecting to "" or "localhost" or "127.0.0.1" works.

If the above fails, then there is a possibility that the BOINC daemon is not starting. If that is the case, then staring it manually may help. If it is installed as a service, run "net start boinc" from a command line. If it is installed as single or multi user, cd to the install directory, and run boinc.exe. If it is now running, you are the victim of a bug that has hopefully been fixed in 5.1.

If it is still not working, you have a problem with one of the XML files, and you will probably have to delete the directory and start over. (I have seen this problem much less with 5.1).

---

BOINC Wiki

I have uninstalled, deleted the directory and reinstalled. I still get the "connection failure" message and boinc.exe still does not appear in the task manager. The only way I can get it to work is to open boinc.exe manually then run boincmgr.exe.

---

I have the same problem on two computers (both Windows XP SP2, and both single user installation): installing 5.2.5/5.2.6 in one case, and 5.2.7 on the other. At first Boinc works fine, but after a restart boinc.exe doesn't start.

When starting it manually, the boinc manager still can't connect, at least not on localhost or 127.0.0.1. After adding the computer's IP to the remote_hosts.cfg file, the manager can connect when I use the computer's own IP instead of localhost.

---

I have uninstalled, deleted the directory and reinstalled. I still get the "connection failure" message and boinc.exe still does not appear in the task manager. The only way I can get it to work is to open boinc.exe manually then run boincmgr.exe.

Same here now that I tried that. Interestingly enough my boinc folder did not have a remote_hosts.cfg (should it?) and creating one with all known ip addresses or localhost etc didn't help either.

Any suggestion on this issue or the other one on the Bro's box with the proxy stuff that pops up when attaching to a project?

Thanks again for your help.

---

I'm having this problem on two of my systems. WinXP Pro, BOINC 5.2.6 single user install, no proxie, hardware firewall. I manually start boincmgr and get the Connection Failed error message about 50% of the time. Trying to connect to localhost or 127.0.0.1 doesn't work and I don't have a remote_hosts.cfg file anywhere either. Oddly enough, simply rebooting my system will sometimes allow boincmgr to start just fine. Running boinc.exe first and then boincmgr.exe will work, but it leaves an open window for boinc.exe that can't be closed.

I'll be eager to see a fix for this too!

---

I believe that in this thread are more then one problem mixed.

At first, please don't use a empty password file "gui_rpc_auth.cfg". There is a problem in release 5.2.7. You should have a least one char in the file. And don't forget to restart all BOINC programs after changing the password.

A "remote_hosts.cfg" file is only neeed if you want to connect from a different host then localhost.

The web connection between BOINC and the project servers and the GUI connection between BOINC and the BOINC Manager are two different things.

Web communication is done on port 80 and 443 (http and https), as with every web browser. If you have problems with this connection, check for router, proxy and firewall issues.

The GUI communication is done on port 1043 on localhost, which is reserved for BOINC. But not every time all programs respect this and sometime local firewalls block all communication on localhost too. If you get problems with this connection, check GUI password usage, firewall rules and other programs using the BOINC port.

---

The GUI communication is done on port 1043 on localhost, which is reserved for BOINC. But not every time all programs respect this and sometime local firewalls block all communication on localhost too. If you get problems with this connection, check GUI password usage, firewall rules and other programs using the BOINC port.

I've checked my firewall, even disabled it, but that doesn't change what happens:
- When trying to connect to localhost, I get a connection failure
- When connecting 'remotely' to 192.168.0.4 in this case (the computer's own IP), the manager, etc, can connect.

If another program is using port 1043, shouldn't the latter fail as well?

This happened on two computers, both are running Windows XP SP2, and in both cases it happened after upgrading to boinc 5.2.x and then rebooting the computer

---