Let's Encrypt Root Zertifikat gültig bis 30.09.2021 (alte R3 / X3 Zertifikatskette)

Hey Volker, Thanks for reaching out. 

I have tested and the results are the same. New certificates are also signed by the old chain. 

We're following up with our internal team for this. I will update this post once we receive the update :) 

Hello Volker,

This is the update from our PM

The Let’s Encrypt chain currently includes both the ISRG Root, which is itself signed by the expiring DST Root.

Certificate chain

 0 s:CN = floater.xxxxxxxx.ca

   i:C = US, O = Let's Encrypt, CN = R3

 1 s:C = US, O = Let's Encrypt, CN = R3

   i:C = US, O = Internet Security Research Group, CN = ISRG Root X1

 2 s:C = US, O = Internet Security Research Group, CN = ISRG Root X1

   i:O = Digital Signature Trust Co., CN = DST Root CA X3

 3 s:O = Digital Signature Trust Co., CN = DST Root CA X3

   i:O = Digital Signature Trust Co., CN = DST Root CA X3

You can see that the chain terminates with the DST cert but includes the ISRG Root.

For any client that includes the ISRG cert in its built-in trusted root list, the fact that it is signed by an out-of-date cert should be irrelevant. The trust is rooted in the ISRG cert. When the client traces the certificate chain, it stops when it hits a cert that is included in its root trust list.

It’s also included in the UTM’s own HTTPS root CA list:

Regards,

You just delete those CN R3 - and no, you don't need to renew LE certs.

Fix is working (delete old R3 CA on UTM)

It would have been nice if SOPHOS had told that fact after their verification process here - but don´t expect too much...

regards

To get SSL Decrypt and Scan working.  I had to disable the "Digital Signature Trust Co. DST Root CA X3" cert under Web Protection > Filtering Options > HTTPS CAs.  Then download the two certs "ISRG Root X1" and "Let’s Encrypt R3" from Chain of Trust - Let's Encrypt (letsencrypt.org) in PEM format.  Upload them to Web Protection > Filtering Options > HTTPS CAs.  Once I did this sites started working again.

Hmm bei mir funktioniert genau das nicht. Er sagt immer noch Zertifikats Error. Noch eine Idee?

Thanks, nfawcett.  But, like Lesmona2020 stated,that didn't work for us.  Still getting sites with certificate errors.  example:  typetastic.com

ZertifikatsError auf dem Proxy (WebProtection) oder dem Reverse Proxy (WebServer Protection) ?

On the proxy (web protection).  DO we need to restart the httpproxy service?

So what is the error shown?

"certificate has expired"  

an example:

I have the same issue, even after following what nfawcett said.

I have the same issue, even after following what nfawcett said.

check intermediate certificate. By whom it has been issued?

Disabling Digital Signature Trust Co. DST Root CA X3 and then turning the web filter off and then back on fixed the issue for me.