Hi Guys, I got a server running nginx as a webserver and using let's encrypt to provide the SSL certificate. I just noticed that my site is no longer getting a valid certificate so I started to investigate. Could not find the error so i decided to ask the help of this community.
My domain is: samartis.de
I ran this command: certbot renew
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Processing /etc/letsencrypt/renewal/samartis.de.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Cert is due for renewal, auto-renewing...
Plugins selected: Authenticator nginx, Installer nginx
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for samartis.de
http-01 challenge for www.samartis.de
nginx: [warn] conflicting server name "www.samartis.de" on 0.0.0.0:443, ignored
nginx: [warn] conflicting server name "samartis.de" on 0.0.0.0:443, ignored
nginx: [warn] conflicting server name "www.samartis.de" on [::]:443, ignored
nginx: [warn] conflicting server name "samartis.de" on [::]:443, ignored
nginx: [warn] conflicting server name "samartis.de" on 0.0.0.0:80, ignored
nginx: [warn] conflicting server name "www.samartis.de" on 0.0.0.0:80, ignored
nginx: [warn] conflicting server name "samartis.de" on [::]:80, ignored
nginx: [warn] conflicting server name "www.samartis.de" on [::]:80, ignored
Waiting for verification...
Challenge failed for domain samartis.de
Challenge failed for domain www.samartis.de
http-01 challenge for samartis.de
http-01 challenge for www.samartis.de
Cleaning up challenges
nginx: [warn] conflicting server name "www.samartis.de" on 0.0.0.0:443, ignored
nginx: [warn] conflicting server name "samartis.de" on 0.0.0.0:443, ignored
nginx: [warn] conflicting server name "www.samartis.de" on [::]:443, ignored
nginx: [warn] conflicting server name "samartis.de" on [::]:443, ignored
nginx: [warn] conflicting server name "samartis.de" on 0.0.0.0:80, ignored
nginx: [warn] conflicting server name "www.samartis.de" on 0.0.0.0:80, ignored
nginx: [warn] conflicting server name "samartis.de" on [::]:80, ignored
nginx: [warn] conflicting server name "www.samartis.de" on [::]:80, ignored
Attempting to renew cert (samartis.de) from /etc/letsencrypt/renewal/samartis.de .conf produced an unexpected error: Some challenges have failed.. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/samartis.de/fullchain.pem (failure)
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/samartis.de/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
IMPORTANT NOTES:
-
The following errors were reported by the server:
Domain: samartis.de
Type: connection
Detail: 89.58.37.59: Fetching
https://www.samartis.de/.well-known/acme-challenge/47nLhmvO_DXaZAdaFskqkerlCW sIfWQGgXlZYd8O8dw:
Timeout during connect (likely firewall problem)Domain: www.samartis.de
Type: connection
Detail: 89.58.37.59: Fetching
https://www.samartis.de/.well-known/acme-challenge/Yr-4r5515mdCDEq08GbGHr3k5c LqQsfjyqeoH12h81Y:
Timeout during connect (likely firewall problem)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. 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.
My web server is (include version): nginx 1.18.0
The operating system my web server runs on is (include version): ubuntu 20.04.4 LTS
My hosting provider, if applicable, is: netcup GmbH (Germany)
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): certbot 0.40.0
UFW Firewall status: Status: active
To Action From
-- ------ ----
Nginx Full ALLOW Anywhere
22/tcp LIMIT Anywhere
OpenSSH ALLOW Anywhere
80 ALLOW Anywhere
443 ALLOW Anywhere
Nginx Full (v6) ALLOW Anywhere (v6)
22/tcp (v6) LIMIT Anywhere (v6)
OpenSSH (v6) ALLOW Anywhere (v6)
80 (v6) ALLOW Anywhere (v6)
443 (v6) ALLOW Anywhere (v6)
I am redirecting http traffic to https via the following nginx config line:
server {
listen 80;
listen [::]:80;
server_name samartis.de www.samartis.de;
return 301 https://www.samartis.de$request_uri;
}
Could that be the root cause for my problem?