Unable to connect to the core client

Author	Message
Radagast97 Send message Joined: 12 Sep 13 Posts: 3 Credit: 9,292 RAC: 0	Message 1421764 - Posted: 29 Sep 2013, 1:11:56 UTC I'm sure this has been answered dozens of time, but I'm not finding the responses. When I start boinc, it's not finding my project (Seti@home) showing no projects and the update greyed out and add project not doing anything when clicked. The simple screen gives "Unable to connect to the core client". There are no projects in the project dropdown list. Not sure what to do from here. ID: 1421764 ·

OzzFan Volunteer tester Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28	Message 1421773 - Posted: 29 Sep 2013, 1:44:26 UTC - in response to Message 1421764. Switch to Advanced View if you're not already using it (View -> Advanced View...). Then from the Advanced drop-down menu, select Select Computer... then in the host name field type "localhost" (without the quotes). The password field should auto-fill. Click OK. Did that work? ID: 1421773 ·

Radagast97 Send message Joined: 12 Sep 13 Posts: 3 Credit: 9,292 RAC: 0	Message 1421816 - Posted: 29 Sep 2013, 3:51:34 UTC - in response to Message 1421773. Well, it did autofill and start trying to connect to the localhost, but it tried to connect to the localhost before. After about two minutes, I get unexpected exit in a popup, with it saying it's tried to connect three times and failed, giving the option to try again. This is what I get from the start, each time I reboot my system. If I revert to simple view, it just says Unable to connect to core client. ID: 1421816 ·

arkayn Volunteer tester Send message Joined: 14 May 99 Posts: 4438 Credit: 55,006,323 RAC: 0	Message 1421819 - Posted: 29 Sep 2013, 4:08:58 UTC - in response to Message 1421816. Well, it did autofill and start trying to connect to the localhost, but it tried to connect to the localhost before. After about two minutes, I get unexpected exit in a popup, with it saying it's tried to connect three times and failed, giving the option to try again. This is what I get from the start, each time I reboot my system. If I revert to simple view, it just says Unable to connect to core client. Did you install a new firewall recently, or new antiviral software? ID: 1421819 ·

rob smith Volunteer moderator Volunteer tester Send message Joined: 7 Mar 03 Posts: 22200 Credit: 416,307,556 RAC: 380	Message 1421962 - Posted: 29 Sep 2013, 12:30:13 UTC I've had this a couple of times. Once it was over enthusiastic anti-virus software which was cured by excluding the BOINC directory and all its contents from scanning or other actions, the second time it was a hard disk handing its notice in, cured by a new disk :-( Bob Smith Member of Seti PIPPS (Pluto is a Planet Protest Society) Somewhere in the (un)known Universe? ID: 1421962 ·

Radagast97 Send message Joined: 12 Sep 13 Posts: 3 Credit: 9,292 RAC: 0	Message 1421973 - Posted: 29 Sep 2013, 13:15:41 UTC - in response to Message 1421962. No new firewall, no new AV sw. This was what it was like the first few times I installed Boinc. The last time, the connection occurred, but I just bounced the machine and it's back where it was. ID: 1421973 ·

arkayn Volunteer tester Send message Joined: 14 May 99 Posts: 4438 Credit: 55,006,323 RAC: 0	Message 1421999 - Posted: 29 Sep 2013, 15:10:23 UTC Is BOINC allowed through the Firewall? ID: 1421999 ·

OzzFan Volunteer tester Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28	Message 1422077 - Posted: 29 Sep 2013, 18:10:23 UTC - in response to Message 1421816. Well, it did autofill and start trying to connect to the localhost, but it tried to connect to the localhost before. After about two minutes, I get unexpected exit in a popup, with it saying it's tried to connect three times and failed, giving the option to try again. This is what I get from the start, each time I reboot my system. If I revert to simple view, it just says Unable to connect to core client. BOINC Manager tries to connect to the BOINC Core Client over TCP port 31416. If this port is blocked, the comms will fail. In the few times I've seen this happen on some of my machines (even with the firewall disabled), the only resolution I've ever found was to completely remote BOINC and all of the folders left behind, all registry keys, and perform a clean re-install. I never found the source of the problem beyond that. ID: 1422077 ·

Theodore Lesnett Send message Joined: 24 Apr 02 Posts: 1 Credit: 378,512 RAC: 1	Message 1436385 - Posted: 1 Nov 2013, 6:40:33 UTC - in response to Message 1421764. Had that problem with the new version of BOINC manager. Lots of posts about ports and all that. The solution was to go back and download an older version which works just fine. Delete current manager and load 7.0.28 and try that. ID: 1436385 ·

©2024 University of California

SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.