Lets encrypt ssl certificat install failes

[Henningm]

Hi

When I try to download and install the "let's encrypt" certificate, it continues to end up with the answer "please try again later".
I've booted the box, but still when trying to install it results in this error

Any ideas on what could be wrong?

The box is running 4.3.3 2017.07.27 firmware

[Marcel Veldhuizen]

I got a different message while trying to renew or install a Let's Encrypt certificate ("Please check the DNS server or if the port 80 is working."), but I followed some of the instructions in viewtopic.php?f=313&t=129872 which eventually led me to check the log file /mnt/ext/opt/QcloudSSLCertificate/log/acme_error_log_http.

In there I found this message:

Code: Select all

09/05/17 23:04:14 - args: Namespace(account_key='/mnt/ext/opt/QcloudSSLCertificate/cert/account/key', acme_dir='/mnt/ext/opt/QcloudSSLCertificate/cert/.well-known/acme-challenge', ca='https://acme-v01.api.letsencrypt.org', cert_file='/mnt/ext/opt/QcloudSSLCertificate/cert/cert_tmp', chain_file='/mnt/ext/opt/QcloudSSLCertificate/cert/chain_tmp', csr='/mnt/ext/opt/QcloudSSLCertificate/cert/csr', email='marcel@redacteddomain.com', qpkg_dir='/mnt/ext/opt/QcloudSSLCertificate', quiet=40, verify_type='http', well_known_dir='/mnt/ext/opt/QcloudSSLCertificate/cert/.well-known')

Traceback (most recent call last):
  File "/mnt/ext/opt/QcloudSSLCertificate/bin/acme-tiny/acme_tiny.py", line 875, in main
    challenge_type=challenge_type, ca_certs=ca_certs)
  File "/mnt/ext/opt/QcloudSSLCertificate/bin/acme-tiny/acme_tiny.py", line 640, in get_crt
    raise ValueError("Error requesting challenges: {0} {1}".format(code, result))
ValueError: Error requesting challenges: 429 <bound method _fileobject.read of <socket._fileobject object at 0x18b8ad0>>

I think the 429 refers to HTTP status code 429, which basically means that the Let's Encrypt server is simply getting more requests than it can handle.
Your error message seems to imply something similar. Unfortunately, the only thing you can do on your side would be to "try again later"

Indeed, when I tried it this morning (the error message is from last night), I got a new certificate just fine on the first go.