Guest User!

You are not Sophos Staff.

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.
  • For me it worked by forcing IPv4

    wget -4  https://acme-v02.api.letsencrypt.org/directory --no-check-certificate

  • I just ran into this again, today. Months ago, I replaced the 93:­3C:­6D... cert with the CA:­BD:­2A... cert and it worked for a while.

    Today, I got these errors:

    2022:05:30-07:14:02 gateway letsencrypt[21106]: I Renew certificate: sending notification WARN-603
    2022:05:30-07:14:02 gateway letsencrypt[21106]: [WARN-603] Let's Encrypt certificate renewal failed accessing Let's Encrypt service
    2022:05:30-07:14:02 gateway letsencrypt[21106]: I Renew certificate: execution failed
    2022:05:30-07:27:02 gateway letsencrypt[23352]: E Renew certificate: Incorrect response code from ACME server: 500
    2022:05:30-07:27:02 gateway letsencrypt[23352]: E Renew certificate: URL was: acme-v02.api.letsencrypt.org/directory
    2022:05:30-07:27:02 gateway letsencrypt[23352]: I Renew certificate: handling CSR REF_CaCsrBwservutec for domain set [sub.domain.tld]
    2022:05:30-07:27:02 gateway letsencrypt[23352]: E Renew certificate: TOS_UNAVAILABLE: Could not obtain the current version of the Let's Encrypt Terms of Service

    Once again, I tried deleting/re-uping the correct X1 cert and restarting httpproxy but that did not help. I then tried unticking/ticking the Allow Let’s Encrypt certificates checkbox on the advanced page but then I got "Failed to create account" errors.

    What ended up working was removing ALL Let's Encrypt certs on the CA tab, rebooting the UTM and manually uploading only the R3 cert (https://letsencrypt.org/certs/lets-encrypt-r3.pem). I was then able to re-tick the Allow Let’s Encrypt certificates checkbox and the account was created. Subsequently, all LE certs were updated.

    Hope this is not a normal reoccuring event that needs to be handled every couple of months.

    --------------------------------------------------------------------
    Sophos UTM 9.714-4 - Home User
    Currently testing VM on i3-9100 @ 3.60 GHz
    16 GB RAM
    Dell Optiplex XE
    Intel Core 2 Duo CPU E8600 @ 3.33GHz
    8GB RAM
    --------------------------------------------------------------------



    Clearify
    [edited by: jeffshead at 1:52 PM (GMT -7) on 30 May 2022]
  • My ticket regarding this issue has reached Global Escalation Support and is now @DevOps

    Dear Sophos Customer,
    
    our Development team has informed us that the processing of the bug ID is unfortunately still delayed.
    
    GES expects a status update now in calendar week 23.
    
    We apologize for the delay.
    

  • Hello,
    
    Development has confirmed this as a Bug. Fix will be available in the next release.
    
    Regards, 
    
    Sophos Global Escalation Support 
    

  • Thanks for the answer. Looked for the same today because of expired LE certificate. Do you know an estimated time frame for release?

  • Development reference number: 
    NUTM-13504
    
    Current Status:
    Assigned to release
    
    Issue type:
    Defect
    
    Your issue with the above reference number has been assigned to a release.
    
    Current plans are to include this fix as part of 9.7MR12 and release the fix by Q3 2022.  Should it be delayed, we will inform you accordingly.
    

  • thanks for the fast answer.

  • As we know the basic problem will be fixed in a MR. But after solving this one manually we have another problem. Maybe someone knows what to do here as I didn't get an answer to my ticket in the last hours:

    2022-06-22 13:04:50 TLS error on connection from prt-xyz.test.local [192.168.101.174]:52532 (SSL_accept): error:14094415:SSL routines:ssl3_read_bytes:sslv3 alert certificate expired

    At first I thought ok only certificate is expired. So I came to this thread. Fixed the LE problem but after that (and a reboot) this problem still persists. Internal devices which check the certificate (and chain) have a problem with the new certificate. If I take a self signed one from my own CA it is working without any harm. And before it did with the LE, too. Someone knows the problem?

  • Is solved now without doing anything. Curious...