Hello, unable to connect and get WU :
01/10/2021 15:52:34 | QuChemPedIA@home | work fetch resumed by user
01/10/2021 15:52:38 | QuChemPedIA@home | Sending scheduler request: To fetch work.
01/10/2021 15:52:38 | QuChemPedIA@home | Requesting new tasks for CPU
01/10/2021 15:52:39 | | Project communication failed: attempting access to reference site
01/10/2021 15:52:39 | QuChemPedIA@home | Scheduler request failed: Peer certificate cannot be authenticated with given CA certificates
01/10/2021 15:52:41 | | Internet access OK - project servers may be temporarily down.

I have 20 tasks waiting an upload. The Event logs mention a problem with certificates.
Tullio

---

They are working fine on Linux. It is a Windows certificate problem.

https://www.sidock.si/sidock/forum_thread.php?id=153&postid=1247#1247
http://wuprop.boinc-af.org/forum_thread.php?id=575&postid=8360#8360
https://boinc.berkeley.edu/forum_thread.php?id=14413

True. I downloaded 2 Linux tasks without problem.
Tullio

---

Is the problem solved or not ?

No. I have received from the LHC@home administrator a workaround, but I am afraid of spoiling my BOINC client so I am now running only Linux tasks.
Tullio

---

From boinc forums
https://boinc.berkeley.edu/forum_thread.php?id=14413

My certificate ca-bundle in C:/Programs/BOINC claims its is valid until January 28 2028. BOINC 7.16.11.
Tullio

---

So, it comes from the let's encrypt certificate, i.e. your OS or your boinc client certificate. Old system are not maintained (Windows 8 and before) and let's encrypt change the certificate.
First solution : use a recent and up-to-date OS or fixed boinc client
second solution : install new certificate by hand / by-pass the certificate check

EDIT: the link to boinc forum explain that the windows boinc client have its own certificates file.

I am running Einstein@home and LHC@home on this same Windows 10 PC and they have no problem. What is the difference?
Tullio

---

Also GPUGRID and climateprediction.net refuse connection. It seems that some BOINC projects accept connection and others do not. Dave Anderson?
Tullio

---

G'Day Tullio,

I know that you run Linux and are doing some Linux work units on this project. Your problem is with Windows.

So the simplest way to get Windows working is to copy the "ca-bundle.crt" certificate file from your Linux machine to your Windows BOINC directory (or where ever your ca-bundle file is kept). Restart the manager and all should work.

I did this (I could of used the ca-bundle on my own Linux machine but den777 over at WUProp gave a link to download the one from his Ubuntu machine, so I used that for my Windows machines), and it all worked.

However there were still about 5 projects that I run (ODLK, LatinSquares, Milkyway, yoyo and TN-Grid) that I had to detach and re-attach to get all things working on my Windows XP machine and iThena had to detach and re-attach on my Windows 7 machine.

If unsure then you can read the postings over at WUProp, under the 'peer certificate' hrading and find the den777 posting.

This may also help others.

The issue is a certificate relating to HTTPS access to the web and it expired on the 30/9/2021, it was called IdentTrust DST Root CA X3, and was replaced by ISRG Root X1.

In the case of my Win XP machine I had to download the ISRG Root X1 file as a .pem file and install just that file into my Windows machine (I had to google how to do it) as a few web sites not related to Boinc would not allow access anymore (in my case the Australian government health site for Covid information).

You asked why some affected and others not, this replacement certificate has been in existence since 2015 but not everyone updated to use it as the other was still working, particularly on custom installs which take a bit of updating.

Hope this may help a few people

Conan

Thanks Conan. The ca-bundle file in my Windows 10 PC with BOINC 7.16.11 claims to be valid until January 28 2028. I have downloaded a ca-bundle file as suggested by the BOINC home page and it claims the same thing. I really do not understand, thanks anyway.
Tullio

---

From 09/30/2021 I have 1 WU in the following status

100% uploading
Received
9/27/2021 5:17:56 PM
Data limit to report
10/11/2021 17:17:55
Computation estimate calculation
20,000 GFLOPs
CPU time
01:40:45
Time elapsed
02:15:47
Executable
vboxwrapper_26200_windows_x86_64.exe

and it is still in the same position. There is any problem with the trickle_credit_vm?

There are 829978 tasks ready to send but in 10 days I have not received any WU yet.

On September 30 I had 21 Windows tasks waiting to be uploaded. Deadline is October 16. Goodby.
Tullio

---

I have no problem with my Linux machines. The problem is with the BOINC clients on Windows. The project receives about 8000 valid tasks per 24 hours according to my dashboard and no problems are reported.

Hello,

Same issue from my side, 72 tasks are waiting to be uploaded for several days now, and it seems that anybody really cares about that.
Even if the issue is coming from the boinc client on windows only; it impacts directly some projects (including QuChemPedIA@home), and I don't really see any of these project admins taking this problem seriously.

Frustrating...

Regards,

Other projects are also affected. I have a huge number of Einstein@home tasks waiting for validation, so many wingmen seem to be missing. On the BOINC home page Dave Anderson writes that also Science United is affected and I saw it declining in the users ranking list. I went from rank 30 to rank 50, since I have now only an old Linux laptop crunching its tasks.
Tullio

---

Same issue from my side, 72 tasks are waiting to be uploaded for several days now, and it seems that anybody really cares about that.
Even if the issue is coming from the boinc client on windows only; it impacts directly some projects (including QuChemPedIA@home), and I don't really see any of these project admins taking this problem seriously.

It's frustrating for me too. The certificate problem is a problem that I understand very well but I can't do anything directly!

The solution is always the same: install a Linux VM with Virtualbox for example, then install Boinc in it and join the project from the VM.

I have tried to connect to all BOINC projects. About 50% of them accept my connection, 50% do not. Since my client is always the same BOINC 7.16.11, the problem is not in the client but on the servers. On a Linux Virtual Machine with SuSE Tumbleweed I have a BOINC 7.18.0 which is a development version. But since it is a Linux host, the problem does not affect it.
Tullio

---