To add to this mystery, I'm now having this exact same problem on two of my old PowerPC Macs. I set one of them up just last month, and never did get it to connect to Einstein. The other Mac is one that I set up a few years ago, and so it had an older version of BOINC. Today, I had to replace the hard drive after it failed. After doing a clean install of OS X Leopard and installing the current version of BOINC, it no longer connects, either. The error output from both machines is identical to what the Debian user has posted here.
Hi Donald,
i was running in same error. First thing i was replacing file ca-bundle.crt in /Library/Application Support/BOINC Data/ with a newer one. Happy to solved the problem i start boincclient and saddly noticed error messages, we run into SSL connect error ... hmpfff...
ok looks like openssl 0.9.7... is now really EOL, means old/latest BOINC Manager for PPC (6.12.35) isn't support meaningful SSL/encrypted connections anymore.
But Einstein scheduler server is also available through http instead of https, this information will be provided also in /Library/Application Support/BOINC Data/ at file client_state.xml.
Quit Boincmanager/Client and open this file in Textedit or vi/nano etc. and search for scheduler_url change then protocol https:// to http:// for serveradress looks like http://scheduler.einsteinathome.org/EinsteinAtHome_cgi/cgi
Safe this file and start boincmanager/client it should now be able to get workunits ...
Hi all, thanks for working through this, I am a few miles below your levels of expertise, but I was also having this issue on LMDE 2 with the ...deb8u1 ca-certificates.
I was informed that with the update to Debian Jessie 8.5 on June 4th a new OpenSSL version was introduced that fixes the problem with certificate validation. You can now unhold the ca-certificates package and update to 8.5 like this:
I was informed that with the update to Debian Jessie 8.5 on June 4th a new OpenSSL version was introduced that fixes the problem with certificate validation. You can now unhold the ca-certificates package and update to 8.5 like this:
Yes, I just tested this in the same VM I used to confirm the bug which still had the old openssl version and new ca-certificates package. After doing the upgrade the scheduler connection worked again. I forgot to explicitly mention to restart boinc-client after upgrading just to make sure the new library is loaded.
I updated one of my Pis by removing the hold and doing an apt-get upgrade. The ca-certificates package rolled forward (as did OpenSSL). I rebooted the Pi, and seen it successfully connect to the project and report results/get new work.
I was informed that with the update to Debian Jessie 8.5 on June 4th a new OpenSSL version was introduced that fixes the problem with certificate validation. You can now unhold the ca-certificates package and update to 8.5 like this:
20.11.2019 2:27:35 | Einstein@Home | Scheduler request failed: Peer certificate cannot be authenticated with given CA certificates
20.11.2019 2:27:46 | | Project communication failed: attempting access to reference site
20.11.2019 2:27:47 | | Internet access OK - project servers may be temporarily down.
Looks like the scheduler isn't running at all. I guess I'm not the only one with this. My tasks statistics haven't been developing for a while and there's no backlog on validation. Maybe it's because no tasks are coming in from anybody, so the validator got nuthin' to do.
RE: RE: Hi Christian! To
)
Good to know, I'll give it a try. Many thanks!
RE: Edit: Here is what I
)
Hi all, thanks for working through this, I am a few miles below your levels of expertise, but I was also having this issue on LMDE 2 with the ...deb8u1 ca-certificates.
sudo apt-cache policy ca-certificates ca-certificates: Installed: 20141019+deb8u1 Candidate: 20141019+deb8u1 Version table: *** 20141019+deb8u1 0 500 http://ftp.us.debian.org/debian/ jessie/main amd64 Packages 100 /var/lib/dpkg/statusI was able to perform the fix quoted above and after installing, I was able to attach to EAH.
I also did the :
and am trucking along! Thanks again, much appreciated.
I was informed that with the
)
I was informed that with the update to Debian Jessie 8.5 on June 4th a new OpenSSL version was introduced that fixes the problem with certificate validation. You can now unhold the ca-certificates package and update to 8.5 like this:
RE: I was informed that
)
Has this been confirmed?
My YouTube Channel: https://www.youtube.com/user/KF7IJZ
Follow me on Twitter: https://twitter.com/KF7IJZ
Yes, I just tested this in
)
Yes, I just tested this in the same VM I used to confirm the bug which still had the old openssl version and new ca-certificates package. After doing the upgrade the scheduler connection worked again. I forgot to explicitly mention to restart boinc-client after upgrading just to make sure the new library is loaded.
Thanks! This will make
)
Thanks! This will make setting up E@H easier on Pi for new folks!
My YouTube Channel: https://www.youtube.com/user/KF7IJZ
Follow me on Twitter: https://twitter.com/KF7IJZ
I updated one of my Pis by
)
I updated one of my Pis by removing the hold and doing an apt-get upgrade. The ca-certificates package rolled forward (as did OpenSSL). I rebooted the Pi, and seen it successfully connect to the project and report results/get new work.
My YouTube Channel: https://www.youtube.com/user/KF7IJZ
Follow me on Twitter: https://twitter.com/KF7IJZ
Tested as working here as
)
Tested as working here as well, on both my RPi's
RE: I was informed that
)
For some reason, the aptitude command didn't work, so instead, I used:
sudo apt-mark unhold ca-certificatesand that worked.
Cheers,
// Brian
Expanding the edge of Science.
I see this problem currently
)
I see this problem currently ...
20.11.2019 2:27:35 | Einstein@Home | Scheduler request failed: Peer certificate cannot be authenticated with given CA certificates
20.11.2019 2:27:46 | | Project communication failed: attempting access to reference site
20.11.2019 2:27:47 | | Internet access OK - project servers may be temporarily down.
Looks like the scheduler isn't running at all. I guess I'm not the only one with this. My tasks statistics haven't been developing for a while and there's no backlog on validation. Maybe it's because no tasks are coming in from anybody, so the validator got nuthin' to do.