Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
I ran this command: /usr/bin/letsencrypt renew >> /var/log/le-renew.log and /bin/systemctl reload nginx
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator webroot, Installer None
Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for ifghtyn.ddns.net
Waiting for verification…
Cleaning up challenges
Attempting to renew cert (ifghtyn.ddns.net) from /etc/letsencrypt/renewal/ifghtyn.ddns.net.conf produced an unexpected error: Failed authorization procedure. ifghtyn.ddns.net (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://ifghtyn.ddns.net/b [116.202.15.252]: "\n\n\n \n\n BigBlueButton\n <meta property=“og:title” content=“BigBlueButton” />\n ". Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/ifghtyn.ddns.net/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
My web server is (include version): Nginx V1.10.3
The operating system my web server runs on is (include version): Ubuntu 16.046 LTS
My hosting provider, if applicable, is: Hetzner
I can login to a root shell on my machine (yes or no, or I don’t know): Yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): No
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): 0.27.0
Hi,
I have searched everywhere but have not found a specific solution to this problem…
Somehow, there’s a redirect from every location to /b, which results in the challenge to fail. This redirect is possibly put in place by BigBlueButton. You should modify this redirect to ignore requests for /.well-known/acme-challenge/ .
\r\n”. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/ifghtyn.ddns.net/fullchain.pem (failure)
I looked for the /.well-known/acme-challenge/ but I did not find it …
certbot renew -a webroot --webroot-path=/usr/share/nginx/html -d ifghtyn.ddns.net -w /var/www
Always 404 error, I saw that certbot does not create the .well-known/acme-challenge folder in /usr/share/nginx/html
I tried several times and now I get the error:
Attempting to renew cert (ifghtyn.ddns.net) from /etc/letsencrypt/renewal/ifghtyn.ddns.net.conf produced an unexpected error: urn: ietf: params: acme: error: rateLimited :: There were too many re quests of a given type :: Error creating new order :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/. Skipping.
All renewal attempts failed. The following certs could not be renewed: