I’ve tried to renew my certificate but it doesn’t work. On my server I execute the command:
sudo /etc/letsencrypt/certbot-auto renew
which results in:
Cert is due for renewal, auto-renewing…
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for werners.sytes.net
Waiting for verification…
Cleaning up challenges
Attempting to renew cert from /etc/letsencrypt/renewal/werners.sytes.net.conf produced an unexpected error: Failed authorization procedure. werners.sytes.net (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Could not connect to werners.sytes.net. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/werners.sytes.net/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you’re using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.
I’ve checked all configurations and they seem to work. Whats wrong here?
?
I disabled the public ssh option on purpose for security reasons. Or how exactly should I run the command that certbot will be able to access my system?
I’ve intentionally redirected all incoming traffic on port 80 to port 443 for security purposes but this seems to be a bad call when using letsencrypt.
It can work OK if you use an HTTP 301 redirect, instead of a port-forwarding redirect. That is a different notion of "redirect" (at a different protocol layer), but it will avoid confusing the CA during the validation process. In that case people who visit your domain in a browser will also successfully get "redirected" in the browser to the secure version of the site.