I just downloaded 5.4.9, trying to run it on a Dual 2GHz G5 running Mac OS X 10.3.9. When I start it up, I get the "Connecting to localhost..." message in the lower right corner, and after a while, it times out and I get a dialog box:

BOINC Manager - Connection Failed

BOINC Manager is not able to connect to a BOINC client. Would you like to try to connect again?

---

I tried allowing connections on port 31416, which shouldn't be necessary for a loopback connection, but not dice. If I run the client from the command line and then run BOINC Manager, I get a dialog box that says:

BOINC Manager - Connection Error

The password you have provided is incorrect, please try again.

---

This is reasonable, since I haven't provided a password, nor do I know where I would provide one or what the password is for.

So, how do I get this working? I have a G3 running 10.3.9 that seems to do fine, with the older 5.2.13, I believe, client.

---

The password is in the file gui_rpc_auth.cfg and will automatically be created if not set. Sometimes restarting the client and/or computer is needed to get the password registered properly.

I think the firewall was blocking BOINC at first and that is why the message changed.

---

BOINC WIKI

BOINCing since 2002/12/8

The password is in the file gui_rpc_auth.cfg and will automatically be created if not set. Sometimes restarting the client and/or computer is needed to get the password registered properly.

I think the firewall was blocking BOINC at first and that is why the message changed.

I tried restarting to no avail. I also tried manually entering the password via Advanced/Select computer... Note that nothing I did with the firewall had any effect on the error message; the difference was that I started the client manually, rather than letting the BOINC Manager start it.

By the way, selecting Advanced/Options crashes BOINC Manager every time.

Try following some, or all of the options given in this thread.

---

Sometime, your provider use dynamic dns ip. These ip have a short live time. So to resolve the probleme, add some dns ip in your ethernet card tcp/ip property in alternative dns ip field add some of your provider (or other) dns ip
to permit navigator and/or boing manager to find the ip he need.

---

DNS is something different from IP, although they work together. You don't type in 66.249.93.99 if you want to go to Google.com, but http://www.google.com ... DNS translates this text to the 66.249.93.99 IP address.

The text address is easier to remember than all the IP addresses. A DNS IP address doesn't exist. It's just a dynamic IP address or static IP address.

---

Try following some, or all of the options given in this thread.

I tried everything relevant to Mac OS X. Rebooted machine. Still didn't work. So, I completely uninstalled BOINC (all the files listed on the installation instructions page) and reinstalled (even downloaded it again). Even temporarily turned off firewall (rather than just opening port 31416). Still cannot connect to client.

To reply to later suggestions, my machine has a static IP address, no NAT or anything else. I don't think that this should be relevant to a loopback connection, though.

---

Hi Michael, sorry it took a while to get back to you, but I'd sent off the question to one of the developers. Here's what he answered, and let's see if any of this helps you.

I can only guess at the problem.

He said that the message changed when he started the client manually.

I don't know if he did this using the separate, stand-alone BOINC
client. If so, that will definitely not work, due to permissions
problems and default directory. It is important NEVER to mix the
stand-alone BOINC client and the BOINC Manager on the same computer.

(To clarify, this applies only to the Macintosh, which has a copy of
the BOINC client embedded in the BOINC Manager bundle. It does not
apply to other computer platforms.)

If he launched the BOINC client which is embedded inside the BOINC
Manager bundle, he must first set the current directory to the BOINC
Data directory.

In either of these cases, the Client won't be able to read the same
gui_rpc_auth.cfg password file as the Manager.

After the BOINC manager fails to connect, he can use the Activity
Monitor application (in/Applications/Utilities/) to determine if the
BOINC client is running (it will be listed simply as "boinc").

He should also make sure that the BOINC Manager application, embedded
client, and the gui_rpc_auth.cfg password file all have the same
owner.

If he has not done so, I would suggest running the installer again,
making sure that he is logged in as a user with administrative
privileges.

Another thing he might try is quitting BOINC Manager, then deleting
the gui_rpc_auth.cfg password file from the directory
/Library/Application Support/BOINC Data/ then restarting the computer.

I hope this helps.

Cheers,
--Charlie

If you want to, you can contact me (Ageless) on [email protected]
Else please answer here on the forums and I'll ferry answers to and fro. :)

---