I first noticed this after upgrading to Lunar. When attempting to update CPDN I am getting

Fri 12 May 2023 11:15:48 BST | climateprediction.net | [http] [ID#1] Info:  Connected to climateprediction.net (129.67.241.50) port 443 (#50)
Fri 12 May 2023 11:15:48 BST | climateprediction.net | [http] [ID#1] Info:  ALPN: offers h2,http/1.1
Fri 12 May 2023 11:15:48 BST | climateprediction.net | [http] [ID#1] Info:  TLSv1.3 (OUT), TLS handshake, Client hello (1):
Fri 12 May 2023 11:15:48 BST | climateprediction.net | [http] [ID#1] Info:   CAfile: /etc/ssl/certs/ca-certificates.crt
Fri 12 May 2023 11:15:48 BST | climateprediction.net | [http] [ID#1] Info:   CApath: /etc/ssl/certs
Fri 12 May 2023 11:15:48 BST | climateprediction.net | [http] [ID#1] Info:  TLSv1.3 (IN), TLS handshake, Server hello (2):
Fri 12 May 2023 11:15:48 BST | climateprediction.net | [http] [ID#1] Info:  TLSv1.2 (IN), TLS handshake, Certificate (11):
Fri 12 May 2023 11:15:48 BST | climateprediction.net | [http] [ID#1] Info:  TLSv1.2 (OUT), TLS alert, unknown CA (560):
Fri 12 May 2023 11:15:48 BST | climateprediction.net | [http] [ID#1] Info:  SSL certificate problem: unable to get local issuer certificate
Fri 12 May 2023 11:15:48 BST | climateprediction.net | [http] [ID#1] Info:  Closing connection 50
Fri 12 May 2023 11:15:48 BST | climateprediction.net | [http] HTTP error: SSL peer certificate or SSH remote key was not OK
Fri 12 May 2023 11:15:48 BST |  | Project communication failed: attempting access to reference site

From a Windows client installed under WINE updates happen normally. Other projects I can update fine including DPDN dev site, WCG and Amicable Numbers. I have tried with a selection of iterations of the Linux client all to no avail. I know this is happening for at least a few others using Linux so it isn't just me but, What is different about the way Linux asks to connect that might cause this? Any ideas of what I might try my end. I have also posted on the CPDN forums and the moderators email list so Andy is aware of the issue.

That's what I got on Friday night too, and emailed to you both. The section that worries me is

TLSv1.2 (OUT), TLS alert, unknown CA (560)

That feels to me like a server certificate problem on climateprediction.net (only) - either a mixed-up installation, or a damaged file. As Jean-David Beyer pointed out on the CPDN site, these certificate files are actually incredibly simple: just chunks of plain ASCII, concatenated one after the other. If you break then up into single certificate files, even a home version of Windows (sorry!) will decode and display the details - provider, period of validity, and so on.

Thanks Richard,

I agree with your diagnosis.

What I am struggling to understand is why it behaves normally for my windows version of BOINC and given that it does, I think there should be a client side workaround for my Linux client?

As Jean-David Beyer pointed out on the CPDN site, these certificate files are actually incredibly simple: just chunks of plain ASCII, concatenated one after the other. If you break the[m] up into single certificate files, even a home version of Windows (sorry!) will decode and display the details - provider, period of validity, and so on.

Some months ago, the Rosetta project could not download anything to my Red Hat Enterprise Linux release 8.7 (Ootpa) machine (it may have been a slightly earlier release at the time). I updated all the certificate stuff on my machine, but nothing actually changed other than the dates of some of the files were made the current date. But the content was unchanged and it did not cure the problem.

I then did a Reset Project on Rosetta on the theory that something was wrong on my machine, but that did not work either. Doing that, Rosetta created the files that were needed, but they were all empty.

I posted on the Rosetta board where complaints should go, but nothing came of it. I wondered if any human was running Rosetta at all. They sure did not read their Crunching board. Then several months later, Rosetta started working again with no action on my part. I hope it does not take months to solve this here. My guess is that Rosetta did not update their certificate when the existing one expired.

It all works just fine on my Windows 10 machine (other than lack of work units, which is no big deal).

I raised my RAM to 128 GBytes so I would have enough room to do the larger Oifs work units, and now I am not getting any, Sigh!

CPU type  Intel(R) Xeon(R) W-2245 CPU @ 3.90GHz [Family 6 Model 85 Stepping 7]
Number of processors 	16
Operating System 	Linux Red Hat Enterprise Linux
Red Hat Enterprise Linux 8.7 (Ootpa) [4.18.0-425.13.1.el8_7.x86_64|libc 2.28]
BOINC version 	7.20.2
Memory 	125.34 GB
Cache 	 16896 KB
Total disk space 	488.04 GB
Free Disk Space 	475.73 GB
Measured floating point speed 6.05 billion ops/sec
Measured integer speed 	     25.61 billion ops/sec

---

I raised my RAM to 128 GBytes so I would have enough room to do the larger Oifs work units, and now I am not getting any, Sigh!

There aren't any to be had even if the CPDN servers were working.

I raised my RAM to 128 GBytes so I would have enough room to do the larger Oifs work units, and now I am not getting any, Sigh!

There aren't any to be had even if the CPDN servers were working.

I know. I am sorry I did not make that clear.

But I cannot even get the Projects tab of the Boinc manager to display the current up-to-date results for climateprediction.net on my Linux machine. My Windows machine has that right.

---

The update process now seems to work normally on Lunar with 7.23.0. Also at least one other user has reported it working on the CPDN fora with Arch Linux.

One is still curious as to the cause. Nothing from Andy on that yet.

And here on Mint 21.1

The update process now seems to work normally on Lunar with 7.23.0. Also at least one other user has reported it working on the CPDN fora with Arch Linux.

And here on Red Hat Enterprise Linux release 8.7 (Ootpa) with 7.20.2.

---

Andy has said, "Thank you for confirming it is now fixed." The curiosity remains.

How much credit do you have?

Total credit 	      16,166,961
Recent average credit 30,619.600

Niotice that these numbers do not agree with the stuff in my signature box. The box is many weeks (months?) behind, and I do not know why.

---

CPDN has both an internal credit issue that they are looking at .... (Amounts of Credit)

AND a Stat's export issue that they are holding on until the credit problem above is resolved. Stat's have not exported in about 55 days.

---

In October 1969 I took an oath to support and defend the Constitution of the United States against all enemies, foreign and domestic;
There was no expiration date.