Message boards : Questions and problems : BoincTasks cannot connect to BOINC 7.16.5
Message board moderation
Author | Message |
---|---|
Send message Joined: 8 Sep 17 Posts: 28 ![]() |
I am running BoincTasks V1.78 and it connects to 5 Windows 10 PCs and 2 Linux NAS devices with no problem. The Windows 10 PCs are running BOINC version 7.14.2. I updated BOINC on one of the Windows 10 PCs to version 7.16.5 and BoincTasks can no longer connect. I tried disabling the firewall on the updated PC and also on the one running BoincTasks. No go. GUI RPC allowed from any host is enabled. Password file is correct. Rebooted both PCs. Still no go. Anyone else see this? Any ideas? Don |
Send message Joined: 8 Sep 17 Posts: 28 ![]() |
The 7.14.2 version was 32 bit. The 7.16.5 version was 64 bit. Reinstalled the 32 bit version of 7.14.2 and it is working again. I don't see a 32 bit version of 7.16.5 available for download. |
![]() ![]() Send message Joined: 17 Nov 16 Posts: 904 ![]() |
The only problem with the 7.16.5 64 bit version is the inability to work with low powered cpus like Atom processors or other low powered cpus used in laptops or handhelds. Problem is with the SSL certification on 64 bit devices. Either update the certs package or stick with the 32 bit version of BOINC. |
Send message Joined: 5 Oct 06 Posts: 5149 ![]() |
Have you tested that with an actual Atom? My testbed Celeron J3455 couldn't run 64-bit v7.14.2, but is running v7.16.5 64-bit version just fine. A fix was applied, and worked in that case. |
![]() Send message Joined: 29 Aug 05 Posts: 15625 ![]() |
I don't see a 32 bit version of 7.16.5 available for download.That's because there isn't one. From 7.16 onwards we only have 64bit BOINC versions, mostly because there's hardly anyone anymore who releases 32bit CPUs as new. If BOINCTasks doesn't work, you should let its developer know. I see you posted on Fred's forums. I hope he's still around and reading. |
Send message Joined: 8 Sep 17 Posts: 28 ![]() |
Have you tested that with an actual Atom? My testbed Celeron J3455 couldn't run 64-bit v7.14.2, but is running v7.16.5 64-bit version just fine. A fix was applied, and worked in that case. What fix was applied? |
Send message Joined: 8 Sep 17 Posts: 28 ![]() |
The only problem with the 7.16.5 64 bit version is the inability to work with low powered cpus like Atom processors or other low powered cpus used in laptops or handhelds. Problem is with the SSL certification on 64 bit devices. Either update the certs package or stick with the 32 bit version of BOINC. Processor is an Intel Celeron J4105 CPU. How to update the certs package? |
![]() Send message Joined: 29 Aug 05 Posts: 15625 ![]() |
The fix was for the BOINC client, a library in it didn't work with the low powered CPUs and the client would crash the moment it started. It will not fix connection problems between BOINCTasks and the BOINC client, for that you have to ask the developer of BOINCTasks for a fix. Edit: no, that's for TThrottle |
Send message Joined: 5 Oct 06 Posts: 5149 ![]() |
Updated versions of libeay32.dll and ssleay32.dll (version 1.0.2s).Have you tested that with an actual Atom? My testbed Celeron J3455 couldn't run 64-bit v7.14.2, but is running v7.16.5 64-bit version just fine. A fix was applied, and worked in that case.What fix was applied? |
Send message Joined: 8 Sep 17 Posts: 28 ![]() |
Thinking it might have been an upgrade issue I uninstalled BOINC and deleted the data directory. Rebooted. Installed BOINC. Rebooted. Changed password and set allow_remote_gui_rpc. Rebooted. Still no connection. So I put on my miners hat and started digging deeper. Going back to my original thought of what the issue was I started to check the firewall settings. Even though I previously tried turning off the firewall it still didn't work. So checking the settings BOINC was allowed through the firewall but it was the wrong one. The rule allowed the 32 bit one through and not the 64 bit one (different directory). Once I changed the rule it started working! Thank you all for all of your assistance. |
Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.