| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: unable to connect to core client on linux |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 4
|
|
| Author |
|
|
Sol33t303
Cruncher Joined: Jan 11, 2017 Post Count: 2 Status: Offline Project Badges: 
|
I just moved to Linux recently and I keep running into the same error "Unable to connect to core client" and I can't seem to get it to work, I'm using Ubuntu 16.04 with a cinnamon desktop, I'm still rather new to Linux so please try to explain how to get it to work thoroughly and keep it relatively simple. I can supply further information if needed.
 |
||
|
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2346 Status: Offline Project Badges: 
|
You might want to try this:
- Create an empty line in the file ~boinc/gui_rpc_auth.cfg $ sudo su boinc -c "echo > ~boinc/gui_rpc_auth.cfg" https://boinc.berkeley.edu/dev/forum_thread.php?id=3903 http://boinc.berkeley.edu/wiki/Installing_BOINC_on_Debian#Optional_setup_hints "If you do only the basic installation as described above, BOINC manager will not be able to automatically connect to the client. To connect the client you will be required to give the GUI RPC password every time you start BOINC manager. That is not a bug, it is a security feature to prevent other users from using the manager to manipulate the client, changing your projects, etc." |
||
|
|
Sol33t303
Cruncher Joined: Jan 11, 2017 Post Count: 2 Status: Offline Project Badges:
|
Thanks, but for whatever reason, it seems like it's working now. I didn't change anything, all I did was leave to go to high school for the day after turning my PC off and when I came home it just started to work. If I run into the problem again I'll try that though.
|
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
AFAIK there's no message distinction between not being able to connect due lack of permission and the daemon not having started, there is no client running to connect to, which my guess is, it started after you powering up.
----------------------------------------[Edit 1 times, last edit by SekeRob* at Apr 26, 2017 7:01:41 AM] |
||
|
|
|