Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 11
Posts: 11   Pages: 2   [ Previous Page | 1 2 ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 2431 times and has 10 replies Next Thread
hchc
Veteran Cruncher
USA
Joined: Aug 15, 2006
Post Count: 748
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: "SSL Connect Error" BOINC 7.20.2 for Windows

I reinstalled 7.20.2 x64 and got the same "SSL Connect Error," so I downgraded to 7.16.11 x64 and it appears to be working again. No issues with Internet connectivity (e.g. it tries to connect to https:// www. google .com) and I believe it connected successfully to WCG servers, but they're currently out of work.

I wanted to know the differences between the 7.16.x and 7.20.x branches, so the BOINC Release Notes state:

Changes in 7.20.0
  • Client: use system's OS bundle rather than our own


I assume this means "Use system's OS certificate bundle," which explains why downgrading back to 7.16 works, since before 7.20.x BOINC uses its own CA bundle at C:\Program Files\BOINC\ca-bundle.crt

The question then is what is missing (permissions or certs) in my copy of Windows 10 Pro 22H2 that is not allowing BOINC to access the Windows native CA certificate store. Either a Windows 10 bug or a BOINC bug.
----------------------------------------
  • i3-8100 (Coffee Lake, 4C/4T) @ 3.6 GHz
  • i5-4590 (Haswell, 4C/4T) @ 3.3 GHz
  • E5800 (Wolfdale, 2C/2T) @ 3.2 GHz

----------------------------------------
[Edit 2 times, last edit by hchc at Dec 18, 2022 9:37:25 PM]
[Dec 18, 2022 9:33:45 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 11   Pages: 2   [ Previous Page | 1 2 ]
[ Jump to Last Post ]
Post new Thread