| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: [solved] BOINC manager cannot connect to client |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 5
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello all
----------------------------------------Since I updated my machine to a newer version of Windows 10, I can't get BOINC running anymore. When I start up the client, all I get is "connecting to localhost" on the right bottom of my client? BOINC is also using up 30% of my CPU non stop. I tried reinstalling BOINC multiple times and I added exceptions of port 31416 to my firewall. And of course I searched the web but couldn't find a solution... Ayone in here who knows how to fix this? Thanks! [Edit 1 times, last edit by Former Member at Aug 27, 2018 12:55:55 PM] |
||
|
|
captainjack
Advanced Cruncher Joined: Apr 14, 2008 Post Count: 147 Status: Offline Project Badges: 
|
Robin95
You can try some of the following and see if it helps. Open BOINC Manager Click on "File" then "Select Computer" A window will pop up that will let you enter a host name. Click ok without entering anything and see if that connects to the BOINC client. Or enter "127.0.0.1:31418" (without the quotes) into the host name field and click ok and see if that connects to the BOINC client. Or enter "localhost:31418" into the host name field and click ok and see if that connects to the BOINC client. If none of those work, you might try to enter "localhost" into the host name field and click ok and see if that connects to the BOINC client. Hope that helps. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi
Tried everything of the above with port 31416, opened my firewall port 31416 too. Still not working :( Thanks though! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I don't use windoze so won't be of much help but if, as seems likely, it's as a result of something that's changed in the latest update, why don't you try using the RPC over a different port -- perhaps one that's normally open in the firewall without you having to manually open it?
From the BOINC Wiki : GUI RPC bind to port 31416 failed: 98 This error happens when the user has no permission to use the RPC port number, or forgotten to allow it through the firewall. Happens in combination with Gstate.init() failed, error code: -180 To set BOINC to use a specific port number, one different from the default 31316, do: boinc --gui_rpc_port N, example given boinc --gui_rpc_port 37777, this starts the BOINC client with TCP port 37777. If you don't want to use any GUI to check on this BOINC from a remote location, you can also start BOINC without any GUI RPC: boinc --no_gui_rpc |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Solution: There was no workaround so I just completely reinstalled Windows on my machine.
|
||
|
|
|