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.
My domain is: sheffieldboulder.uk / kimura.no-ip.info
I ran this command:
certbot renew --agree-tos
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
-------------------------------------------------------------------------------
Processing /etc/letsencrypt/renewal/kimura.no-ip.info.conf
-------------------------------------------------------------------------------
Cert is due for renewal, auto-renewing...
Plugins selected: Authenticator webroot, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for kimura.no-ip.info
Waiting for verification...
Cleaning up challenges
Attempting to renew cert (kimura.no-ip.info) from /etc/letsencrypt/renewal/kimura.no-ip.info.conf produced an unexpected error: Failed authorization procedure. kimura.no-ip.info (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://kimura.no-ip.info/.well-known/acme-challenge/_w_lEsEQ4Fmbt6dMGzGBu8NvTvkGW4RbkKOAOUOAmiA: " <!DOCTYPE html>
<html lang="en" id="document" dir="ltr">
<head prefix="og: http://ogp.me/ns# article: http://ogp.me/ns/article# ". Skipping.
-------------------------------------------------------------------------------
Processing /etc/letsencrypt/renewal/sheffieldboulder.uk.conf
-------------------------------------------------------------------------------
Cert is due for renewal, auto-renewing...
Plugins selected: Authenticator webroot, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for sheffieldboulder.uk
Waiting for verification...
Cleaning up challenges
Attempting to renew cert (sheffieldboulder.uk) from /etc/letsencrypt/renewal/sheffieldboulder.uk.conf produced an unexpected error: Failed authorization procedure. sheffieldboulder.uk (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://sheffieldboulder.uk/.well-known/acme-challenge/mDu4ZJ1TzDC42TDuaZt9iFueFKGCi9lvRS6QkoEK448: "<!DOCTYPE html>
<html lang="en" dir="ltr" class="no-js">
<head>
<meta charset="utf-8" />
<title>well-known_acme-challeng". Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/kimura.no-ip.info/fullchain.pem (failure)
/etc/letsencrypt/live/sheffieldboulder.uk/fullchain.pem (failure)
-------------------------------------------------------------------------------
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/kimura.no-ip.info/fullchain.pem (failure)
/etc/letsencrypt/live/sheffieldboulder.uk/fullchain.pem (failure)
-------------------------------------------------------------------------------
2 renew failure(s), 0 parse failure(s)
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: kimura.no-ip.info
Type: unauthorized
Detail: Invalid response from
http://kimura.no-ip.info/.well-known/acme-challenge/_w_lEsEQ4Fmbt6dMGzGBu8NvTvkGW4RbkKOAOUOAmiA:
"<!DOCTYPE html>
<html lang="en" id="document" dir="ltr">
<head prefix="og: http://ogp.me/ns# article:
http://ogp.me/ns/article# "
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.
- The following errors were reported by the server:
Domain: sheffieldboulder.uk
Type: unauthorized
Detail: Invalid response from
http://sheffieldboulder.uk/.well-known/acme-challenge/mDu4ZJ1TzDC42TDuaZt9iFueFKGCi9lvRS6QkoEK448:
"<!DOCTYPE html>
<html lang="en" dir="ltr" class="no-js">
<head>
<meta charset="utf-8" />
<title>well-known_acme-challeng"
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.
My web server is (include version): nginx version: nginx/1.12.2
The operating system my web server runs on is (include version): ArchLinux (no version, rolling release)
My hosting provider, if applicable, is: OVH
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
Initially I had a different error but I solved that after reading that I need to disable redirects of http/port 80 which I have in place and have done so in the /etc/nginx/nginx.conf and restarted the service to ensure redirects didn’t happen. Now hit this problem.
At some point I’ve screwed up the certificate for sheffieldboulder.uk too as I now can’t access that site due to a certificate error.
If it makes any difference when I first obtained certificates I setup nginx with root /var/lib/letsencrypt/ for both sites and then changed the root to root /usr/share/nginx/html/sheffieldboulder/ and root /usr/share/nginx/html/kimura/. Realising that the necessary ~/.well-known/acme-challenge directories were not present in either of these I created them, ensuring permissions were those for the web server user…
mkdir -p /usr/share/nginx/html/sheffieldboulder/.well-known/acme-challenge /usr/share/nginx/html/kimura/.well-known/acme-challenge
chown -R http:http /usr/share/nginx/html/sheffieldboulder/.well-known /usr/share/nginx/html/kimura/.well-known
…but that didn’t help. I noticed that certbot is reporting that its looking for http://localhost/ but am unsure why (a guess would be it recognises its on the target domain).
Wondering if I’d be better off just creating new certificates rather than refreshing (currently one is due to expire 2018-01-19 and I expect to get a renewal notice for the other in the not too distant future).
