I have a long running version of UTM which I have updated to the latest code level (u2d-sys-9.709003-710001.tgz.gpg).
I also created a new VM using the latest ISO which I did update to u2d-sys-9.709003-710001.tgz.gpg
Let's Encrypt started failing to renew on my old setup and I have tried all the steps found in these forums with no success.
Removing and uploading certs made no difference.
On my old setup I have toggled off the Let's Encrypt support and tried to enable again.
Both the new install and the old install fail with this same exact message:
2022:03:23-10:37:48 ##### letsencrypt[6335]: I Create account: creating new Let's Encrypt acccount
2022:03:23-10:37:48 ##### letsencrypt[6335]: E Create account: Incorrect response code from ACME server: 500
2022:03:23-10:37:48 ##### letsencrypt[6335]: E Create account: URL was: acme-v02.api.letsencrypt.org/directory
2022:03:23-10:37:48 ##### letsencrypt[6335]: E Create account: TOS_UNAVAILABLE: Failed to retrieve the current Terms of Service URL
2022:03:23-10:37:48 ##### letsencrypt[6335]: E Create account: failed to create account
It appears even the new code is having issues with the new ACME V2 at Let's Encrypt service. Given everyone is telling us the SSL certs are the issue a fresh setup does not have these certs and fails the same way as the old install.
This makes me think this has nothing to do with the CA in the certificate store, but some underlying code issue or hidden certificates in the UTM operating system.
Does anyone have any solutions (root command line, etc.) to fix this issue?
This thread was automatically locked due to age.
