This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos UTM 9.707-5 - Let’s Encrypt failed: Failed to retrieve the current Terms of Service link

Hello, 

I appear to be having issues trying to renew LE Certificates. This started a few days ago (when due for renewal) and initially I did come to this forum for answers and found that one post suggested to update to the latest UTM version. I'm now up to 9.707-5 but still have the same issue. 

Patterns also up to date:

Current pattern version: 204063
Latest available pattern version: 204063

It appears to be related to being unable to find the TOS but all links it shows resolve fine. The certificates I have are used for UTM Management and WAF.

Looking at the logs I see the following after turning the service off and back on...

2021:10:10-09:15:14 utm letsencrypt[9881]: I Create account: creating new Let's Encrypt acccount
2021:10:10-09:15:15 utm letsencrypt[9881]: E Create account: Incorrect response code from ACME server: 500
2021:10:10-09:15:15 utm letsencrypt[9881]: E Create account: URL was: acme-v02.api.letsencrypt.org/directory
2021:10:10-09:15:15 utm letsencrypt[9881]: E Create account: TOS_UNAVAILABLE: Failed to retrieve the current Terms of Service URL
2021:10:10-09:15:15 utm letsencrypt[9881]: E Create account: failed to create account

Prior to that, an attempt at renewing:

2021:10:10-08:44:02 utm letsencrypt[1020]: E Renew certificate: Incorrect response code from ACME server: 500
2021:10:10-08:44:02 utm letsencrypt[1020]: E Renew certificate: URL was: acme-v02.api.letsencrypt.org/directory
2021:10:10-08:44:02 utm letsencrypt[1020]: I Renew certificate: handling CSR REF_CaCsrXXXXLetsEncry for domain set [DOMAINS]
2021:10:10-08:44:02 utm letsencrypt[1020]: E Renew certificate: TOS_UNAVAILABLE: Could not obtain the current version of the Let's Encrypt Terms of Service
2021:10:10-08:44:02 utm letsencrypt[1020]: I Renew certificate: sending notification WARN-603
2021:10:10-08:44:02 utm letsencrypt[1020]: [WARN-603] Let's Encrypt certificate renewal failed accessing Let's Encrypt service
2021:10:10-08:44:02 utm letsencrypt[1020]: I Renew certificate: execution failed

The UTM has been rebooted, no change. I've turned off Web protection, no change...

Any ideas appreciated.

Thanks!


This thread was automatically locked due to age.
Parents
  • There are 2 X1 CA certificates:

    Correct
    Fingerprint: CA:BD:2A:79:A1:07:6A:31:F2:1D:25:36:35:CB:03:9D:43:29:A5:E8

    Wrong
    Fingerprint: 93:3C:6D:DE:E9:5C:9C:41:A4:0F:9F:50:49:3D:82:BE:03:AD:87:BF

    Download correct X1: https://letsencrypt.org/certificates/ or https://letsencrypt.org/certs/isrgrootx1.pem

    Delete the 93:3C:... and add the CA:BD:.. manually under Certificate Management->Certificate Authority

    The wrong X1 will reappear after a renew of a LetsEncrypt certificate. So you might have to check again after at least 2 month.

  • > The wrong X1 will reappear after a renew of a LetsEncrypt certificate. So you might have to check again after at least 2 month.

    can you please elaborate that? Can Sophos give us official solution / patch for the issue?

    we have support case opened 04594640 

  • When i try this i got:
    fw:/root # wget acme-v02.api.letsencrypt.org/directory
    --2021-12-04 19:45:59--  acme-v02.api.letsencrypt.org/directory
    Resolving acme-v02.api.letsencrypt.org... 2606:4700:60:0:f53d:5624:85c7:3a2c, 172.65.32.248
    Connecting to acme-v02.api.letsencrypt.org|2606:4700:60:0:f53d:5624:85c7:3a2c|:443... failed: Connection timed out.
    Connecting to acme-v02.api.letsencrypt.org|172.65.32.248|:443... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 658 [application/json]
    Saving to: `directory.1'

    100%[====================================================================================================================================================================================================================>] 658         --.-K/s   in 0s

    2021-12-04 19:48:07 (96.2 MB/s) - `directory.1' saved [658/658]

    fw:/root # wget acme-v02.api.letsencrypt.org/directory --no-check-certificate
    --2021-12-04 19:42:51--  acme-v02.api.letsencrypt.org/directory
    Resolving acme-v02.api.letsencrypt.org... 2606:4700:60:0:f53d:5624:85c7:3a2c, 172.65.32.248
    Connecting to acme-v02.api.letsencrypt.org|2606:4700:60:0:f53d:5624:85c7:3a2c|:443... failed: Connection timed out.
    Connecting to acme-v02.api.letsencrypt.org|172.65.32.248|:443... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 658 [application/json]
    Saving to: `directory'

    100%[====================================================================================================================================================================================================================>] 658         --.-K/s   in 0s

    2021-12-04 19:44:59 (121 MB/s) - `directory' saved [658/658]

  • I get repeatingly connection reset by peer

    astaroutmisbest:/root/test # wget acme-v02.api.letsencrypt.org/directory
    --2021-12-05 10:33:57--  acme-v02.api.letsencrypt.org/directory
    Resolving acme-v02.api.letsencrypt.org... 172.65.32.248, 2606:4700:60:0:f53d:5624:85c7:3a2c
    Connecting to acme-v02.api.letsencrypt.org|172.65.32.248|:80... connected.
    HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.
    Retrying.

    --2021-12-05 10:33:58--  (try: 2)  acme-v02.api.letsencrypt.org/directory
    Connecting to acme-v02.api.letsencrypt.org|172.65.32.248|:80... connected.
    HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.
    Retrying.

    Using no check certificate it downloads

    astaroutmisbest:/root/test # wget acme-v02.api.letsencrypt.org/directory --no-check-certificate
    --2021-12-05 10:40:20--  acme-v02.api.letsencrypt.org/directory
    Resolving acme-v02.api.letsencrypt.org... 172.65.32.248, 2606:4700:60:0:f53d:5624:85c7:3a2c
    Connecting to acme-v02.api.letsencrypt.org|172.65.32.248|:443... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 658 [application/json]
    Saving to: `directory'
    100%[=================================================>] 658         --.-K/s   in 0s      
    2021-12-05 10:40:20 (158 MB/s) - `directory' saved [658/658]

    BTW:
    Box is on 9.708-6 also tried 9.705, 707 and 708

    I have no problems on 707 with my home use installation, but the box with the paid license causes these problems...

  • So on your site it's working, on my site it's not working without --no-check-cert.

  • Yes i have installed the update to 9.708-6 but still unable to activate let's encrypt again....

  • @PieterH and Jasmine,

    are you getting the same error if you activate let's enc.?

  • Hello Sophos Support, what is the status here? Ticket was already opened last Friday and apparently it affects other people?
    Please urgently share the status or resolution of the issue!

  • Hi all.

    I know this issue is frustrating. My advice is to delete ALL!!!!! from Certificate Authorities and then import back those that are needed.
    I've deleted all X1 several times but in the end, we found out there was third one with a completely diff name that was causing troubles. Because of that name, I didn't even look at it this third one in the first place.

  • Yes when I try to turn on let’s encrypt again I got the errors. 

  • I don’t see let’s Encrypt In certificate Authorities. 

  • I still have an issue to activate let's encrypt again.

    Got an error in the log:

    2021:12:12-16:05:32 fw letsencrypt[478]: I Create account: creating new Let's Encrypt acccount
    2021:12:12-16:06:02 fw letsencrypt[478]: E Create account: Incorrect response code from ACME server: 500
    2021:12:12-16:06:02 fw letsencrypt[478]: E Create account: URL was: acme-v02.api.letsencrypt.org/directory
    2021:12:12-16:06:02 fw letsencrypt[478]: E Create account: TOS_UNAVAILABLE: Failed to retrieve the current Terms of Service URL
    2021:12:12-16:06:02 fw letsencrypt[478]: E Create account: failed to create account
    The suggestion to delete all from the certificate Authorities sounds good but I don't see anything from let's encrypt there so I don't think this will fix the issue.
    Is there any progress on this?
Reply
  • I still have an issue to activate let's encrypt again.

    Got an error in the log:

    2021:12:12-16:05:32 fw letsencrypt[478]: I Create account: creating new Let's Encrypt acccount
    2021:12:12-16:06:02 fw letsencrypt[478]: E Create account: Incorrect response code from ACME server: 500
    2021:12:12-16:06:02 fw letsencrypt[478]: E Create account: URL was: acme-v02.api.letsencrypt.org/directory
    2021:12:12-16:06:02 fw letsencrypt[478]: E Create account: TOS_UNAVAILABLE: Failed to retrieve the current Terms of Service URL
    2021:12:12-16:06:02 fw letsencrypt[478]: E Create account: failed to create account
    The suggestion to delete all from the certificate Authorities sounds good but I don't see anything from let's encrypt there so I don't think this will fix the issue.
    Is there any progress on this?
Children