Message boards : BOINC client : "SSL Connect Error" BOINC 7.20.2 for Windows 10 22H2
Message board moderation
Previous · 1 · 2
Author | Message |
---|---|
Send message Joined: 27 Jun 08 Posts: 641 |
I have 100's of these messages, they only go away after attaching using http JYSArea51 86 World Community Grid 4/14/2023 10:37:06 PM This project seems to have changed its URL. When convenient, remove the project, then add http://www.worldcommunitygrid.org/ 87 World Community Grid 4/14/2023 11:12:06 PM This project seems to have changed its URL. When convenient, remove the project, then add http://www.worldcommunitygrid.org/ 88 World Community Grid 4/14/2023 11:14:09 PM This project seems to have changed its URL. When convenient, remove the project, then add http://www.worldcommunitygrid.org/ 89 World Community Grid 4/14/2023 11:16:13 PM This project seems to have changed its URL. When convenient, remove the project, then add http://www.worldcommunitygrid.org/ EDIT: should have mentioned that I have several 22h2 systems, win 10 & 11 and show http as well as https (like you) and I do not have any problem connecting to worldcommunitygrid l |
Send message Joined: 29 Aug 05 Posts: 15566 |
But this is the message line that you only see when adding http_debug, otherwise it's silent. It's not the same one as the one where you add the project and BOINC then first (or second, or 100th) talks to the scheduler which checks what project URL is used. This URL is used by Curl, I think. |
Send message Joined: 27 Jun 08 Posts: 641 |
But this is the message line that you only see when adding http_debug, otherwise it's silent. It's not the same one as the one where you add the project and BOINC then first (or second, or 100th) talks to the scheduler which checks what project URL is used. This URL is used by Curl, I think. You are probably correct. I did a "find" and https shows up on 22h2 systems that are attached correctly using http. However, it would be nice if BOINC updated ALL_PROJECTS_LIST.XML to have the correct attachment url. This is what I am guessing is happening and IANE on networks http and https difference is that ssl and tls certificates are checked when using https A connection is being made to wcg but it goes through a driver that has a problem. For example, when I enabled core isolation (an hour ago on a new system) I got an iqvw64e.sys driver error https://answers.microsoft.com/en-us/windows/forum/all/iqvw64esys-a-driver-cannot-load-on-this-device/dcc336f6-8815-4346-952b-fff97fe81523?page=2 That is a VPN driver, but I do not use VPN and never have and there is no problem with boinc on that system. I had to uninstall intel pro networking client to remove the driver and allow core isolation to be enabled. Possibly a connection to WCG goes through a problem driver on SoCrunchy's system. A good check is to enabled core isolation and see if any network driver has a problem I never got that app to work on my Dell system in 22h2. Dell let the certificate expire and was not interested in updating it. |
Send message Joined: 29 Aug 05 Posts: 15566 |
However, it would be nice if BOINC updated ALL_PROJECTS_LIST.XML to have the correct attachment url.David normally does this, but it requires that someone, project admin, trusted users etc., tell him about it. It can't do it on its own. Unless we add AutoGPT to BOINC and make BOINC sentient. 😂 |
Send message Joined: 27 Jun 08 Posts: 641 |
However, it would be nice if BOINC updated ALL_PROJECTS_LIST.XML to have the correct attachment url.David normally does this, but it requires that someone, project admin, trusted users etc., tell him about it. It can't do it on its own. Unless we add AutoGPT to BOINC and make BOINC sentient. 😂 I recall this was discussed some time ago. WUProp@home is not in the list because they did not bother to ask to have it put in. As to why 7.16 is working I am guessing it does not rely on windows to handle the certificate whereas 7.20 does and an expired cert somewhere triggers an error in 22h2 |
Copyright © 2024 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.