Project communication failed: attempting access to reference site

Author	Message
gparrott Send message Joined: 10 Nov 21 Posts: 3 Credit: 3,732,000 RAC: 4,747	Message 1393 - Posted: 16 Dec 2021, 2:23:50 UTC When I try to add SiDock as a project in BOINC on one laptop, I get the "Project communication failed: attempting access to reference site" error in the log. On another laptop, it installs fine. Both are Windows 10 lenovo laptops, new within the last three months and fully updated. Thoughts? GP ID: 1393 · Rating: 0 · rate: / Reply Quote

Crystal Pellet Send message Joined: 26 Oct 20 Posts: 53 Credit: 2,520,836 RAC: 0	Message 1394 - Posted: 16 Dec 2021, 7:35:53 UTC - in response to Message 1393. There was a problem with certificates. Probably you are not running the newest BOINC version on your problem laptop. ID: 1394 · Rating: 0 · rate: / Reply Quote

gparrott Send message Joined: 10 Nov 21 Posts: 3 Credit: 3,732,000 RAC: 4,747	Message 1397 - Posted: 21 Dec 2021, 23:07:59 UTC - in response to Message 1394. Nope. It's running 7.16.11 (x64). I wished it were that easy :-) Is there any useful debug info I can capture? I didn't see much in the event log. GP ID: 1397 · Rating: 0 · rate: / Reply Quote

PDW Send message Joined: 24 Oct 20 Posts: 10 Credit: 19,996,025 RAC: 6,625	Message 1398 - Posted: 21 Dec 2021, 23:33:29 UTC - in response to Message 1397. 7.16.20 is the latest release, you should upgrade to that and report back if it doesn't fix the problem. ID: 1398 · Rating: 0 · rate: / Reply Quote

gparrott Send message Joined: 10 Nov 21 Posts: 3 Credit: 3,732,000 RAC: 4,747	Message 1400 - Posted: 24 Dec 2021, 1:52:19 UTC - in response to Message 1398. That did it. Thanks! Not sure why the check for update feature in the boinc manager said it was up to date. I'll know to check the website directly in the future. GP ID: 1400 · Rating: 0 · rate: / Reply Quote

Dr Who Fan Send message Joined: 24 Oct 20 Posts: 19 Credit: 458,046 RAC: 19	Message 1412 - Posted: 26 Dec 2021, 19:20:23 UTC - in response to Message 1400. That did it. Thanks! Not sure why the check for update feature in the boinc manager said it was up to date. I'll know to check the website directly in the future. GP Due to the expired certificate file the BOINC PROGRAM COULD NOT ACCESS THE BOINC SERVER to see it was out of date. Kind of self defeated the built in update request you could say. ID: 1412 · Rating: 0 · rate: / Reply Quote

jwaggy Send message Joined: 17 Feb 22 Posts: 2 Credit: 4,977,522 RAC: 2	Message 2060 - Posted: 2 May 2023, 5:57:19 UTC I'm having this same problem years later but am currently running 7.20.2 which is the current boinc version. Any thoughts? ID: 2060 · Rating: 0 · rate: / Reply Quote

Brian Nixon Send message Joined: 10 Feb 21 Posts: 21 Credit: 4,618,677 RAC: 1,021	Message 2061 - Posted: 2 May 2023, 11:30:51 UTC - in response to Message 2060. Try adding the http_debug flag (Manager, Advanced View » Options » Event Log options) and then looking in the BOINC event log for entries containing HTTP error:, which should give additional detail about the problem. ID: 2061 · Rating: 0 · rate: / Reply Quote

jwaggy Send message Joined: 17 Feb 22 Posts: 2 Credit: 4,977,522 RAC: 2	Message 2062 - Posted: 2 May 2023, 20:40:04 UTC 5/2/2023 1:35:23 PM \| \| [http] [ID#2] Info: schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline. Is the first error I see then after that is 5/2/2023 1:35:23 PM \| \| [http] HTTP error: SSL connect error ID: 2062 · Rating: 0 · rate: / Reply Quote

Brian Nixon Send message Joined: 10 Feb 21 Posts: 21 Credit: 4,618,677 RAC: 1,021	Message 2063 - Posted: 2 May 2023, 20:48:39 UTC - in response to Message 2062. Also reported on the main BOINC forums here. Not sure it ever got resolved. ID: 2063 · Rating: 0 · rate: / Reply Quote