Hi,
I run UCS 4 for our server quite a while with a properly working Let’s Encrypt certificate. It was monthly renewed without any issues. We regularly update the UCS server and now run UCS 4.4-2 errata-291. However, we realized that the certificate renewal that should have been performed on September 29, 2019 did not work.
The logfile /var/log/univention/letsencrypt.log reads:
So 29. Sep 16:45:23 CEST 2019
Refreshing certificate for following domains:
<hostname>
Parsing account key...
Parsing CSR...
Found domains: <hostname>
Getting directory...
Directory found!
Registering account...
Already registered!
Creating new order...
Order created!
Verifying <hostname>...
Traceback (most recent call last):
File "/usr/share/univention-letsencrypt/acme_tiny.py", line 197, in <module>
main(sys.argv[1:])
File "/usr/share/univention-letsencrypt/acme_tiny.py", line 193, in main
signed_crt = get_crt(args.account_key, args.csr, args.acme_dir, log=LOGGER, CA=args.ca, disable_check=args.disable_check, directory_url=args.directory_url, contact=args.contact)
File "/usr/share/univention-letsencrypt/acme_tiny.py", line 147, in get_crt
authorization = _poll_until_not(auth_url, ["pending"], "Error checking challenge status for {0}".format(domain))
File "/usr/share/univention-letsencrypt/acme_tiny.py", line 66, in _poll_until_not
result, _, _ = _do_request(url, err_msg=err_msg)
File "/usr/share/univention-letsencrypt/acme_tiny.py", line 45, in _do_request
raise ValueError("{0}:\nUrl: {1}\nData: {2}\nResponse Code: {3}\nResponse: {4}".format(err_msg, url, data, code, resp_data))
ValueError: Error checking challenge status for <hostname>:
Url: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/11293440
Data: None
Response Code: None
Response: <urlopen error [Errno 104] Connection reset by peer>
Setting letsencrypt/status
Does anybody have a hint as how to cope with this error?
Best regards,
Peter