Cannot report work due to reported Certificate error
26 May 2020 11:01:43 UTC
Topic 222634
(moderation:
. . For the last hour I have not been able to report completed work and get more tasks. I am getting the error "Cannot authenticate certificate with current CA".
. . This is only on my Windows box, the 4 Linux boxes are running AOK.
Stephen
? ?
. . For the last hour I
)
. . For the last hour I have not been able to report completed work and get more tasks. I am getting the error "Cannot authenticate peer certificate with current CA".
. . This is only on my Windows box, the 4 Linux boxes are running AOK.
Stephen
? ?
Yes me too. Also
)
Yes me too. Also Windows.
Thanks for reporting it, now I know it's not my computer.
Yep
)
Yep
I have three Windows
)
I have three Windows hosts.
One has the problem described, apparently from over three hours ago, but the other two are fine--just reported work and got new work a moment ago.
I don't see a gap in reporting dates on the two healthy machines.
Aha!, perhaps.Over on
)
Aha!, perhaps.
Over on Cruncher's corner, a user reported that they found information on the net blaming this on too old a BOINC version, and that on updating their BOINC, the problem resolved.
Of my three hosts, the two healthy ones are reported at BOINC versions 7.14.0 and 7.14.2, while the suffering one is at 7.8.3. So perhaps this diagnosis fits my situation.
I'll update BOINC and report.
Apparent success here. I
)
Apparent success here.
I downloaded BOINC 7.16.5 from the BOINC 64-bit Windows client page where it shows as the current recommended version dated March 10, 2020.
I did an overinstall (just running the .exe without stopping anything). It took a little time, installed, paused my tasks while running benchmarks, then promptly successfully contacted the project, reported my work backlog, and got new work.
Possibly you may have a reason to avoid this version, but at the moment this seems to have worked for me.
The BOINC version I had been running on that machine dated from late 2017.
all of yall are using very
)
all of yall are using very old BOINC versions.
Read the technical news posts that's been up warning about this for a long time. https://einsteinathome.org/content/upcoming-ssltls-security-updates-old-boinc-client-support
_________________________________________________________________________
Not a THAT old. BOINC 7.10
)
Not a THAT old. BOINC 7.10 was released exactly 2 years ago (May 2018).
So today you just "killed" all clients installed or last updated >= 2 years ago. And also all clients running previous BOINC versions for a reason.
Mad_Max wrote:And also all
)
what reason? because everyone that fixed this issue, fixed it by updating. so obviously nothing was preventing them from updating.
some people are using clients from 7.6.xx (2015) and 7.2.42 (2014). windows systems can download the new version from the boinc website and install it. linux systems can download the AIO package and run it standalone. there's really no reason to stay on such an old version.
_________________________________________________________________________
. . Thanks guys for the
)
. . Thanks guys for the input, and thanks Ian for the link. I will update the client.
Stephen