After problems with upgrade to v5.0.0 I got finally again this LetsEncrypt Error. But I remembered this thread - and could solve the problem again. That’s why: Again many thanks.
I am also still stuck at
notAfter=Mar 17 16:40:46 2021 GMT
tried the suggestions in this thread already, including
update-ca-certificates --fresh
After fresh installation of UCS 5.0.2 with Let’s Encrypt i got the same error in system diagnostic again. But the the solution of tpfann in #87 was the right tip.
Many thanks
Same for me.
A fresh installation, system diagnostic error about invalid certificate and the solution of tpfann (step 1, 2 and 3) worked for me.
Same here on a fresh 5.0.4.
Step 1, 2 and 3 and everything ist OK
Same here before going from 5.0-4 to 5.0-6
-
wget -O /etc/univention/letsencrypt/lets-encrypt-r3.pem https://letsencrypt.org/certs/lets-encrypt-r3.pem
-
ln -s /etc/univention/letsencrypt/lets-encrypt-r3.pem /usr/local/share/ca-certificates/lets-encrypt-r3.crt
-
update-ca-certificates
And the problem was solved.
Just in case the System Diagnostic Error hits you again after the changes last night on LetsEncrypt-side here are the updated instructions in order to solve the issue:
- wget -O /etc/univention/letsencrypt/r11.pem https://letsencrypt.org/certs/2024/r11.pem
- ln -s /etc/univention/letsencrypt/r11.pem /usr/local/share/ca-certificates/r11.crt
- update-ca-certificates --fresh
1 Like
This did not work for me.
But the commands at the end of the posting here:
did it.
1 Like
After checking my current LetsEncrypt-Certificate that was created on 01.07.2024, I found out that the R11- Intermediate-Certificate seems the one to be relevant (see screenshot):
But good to know if you want to be on the save side, you better install the R10- Intermediate-Certificate as well.