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:
ttrss.shiromar.com
I ran this command:
sudo certbot --nginx -d ttrss.shiromar.com
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator nginx, Installer nginx
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for ttrss.shiromar.com
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. ttrss.shiromar.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://ttrss.shiromar.com/.well-known/acme-challenge/Gl2IdRzwnxLVSH9HQ-IXVjoXC7856IewMSBDvcyXMuU: Timeout during connect (likely firewall problem)
IMPORTANT NOTES:
-
The following errors were reported by the server:
Domain: ttrss.shiromar.com
Type: connection
Detail: Fetching
http://ttrss.shiromar.com/.well-known/acme-challenge/Gl2IdRzwnxLVSH9HQ-IXVjoXC7856IewMSBDvcyXMuU:
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 version: nginx/1.14.0 (Ubuntu)
The operating system my web server runs on is (include version):
Ubuntu 18.04
My hosting provider, if applicable, is:
SELF
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.31.0
nginx server block:
server {server {
listen 80;
listen [::]:80;
server_name ttrss.shiromar.com;
return 301 https://$server_name$request_uri;
}
server {
listen 443 ssl http2;
listen [::]:443 ssl http2;
server_name ttrss.shiromar.com;
root /var/www/ttrss;
index index.php;
access_log /var/log/nginx/ttrss_access.log;
error_log /var/log/nginx/ttrss_error.log info;
location = /robots.txt {
add_header Content-Type text/plain;
return 200 “User-agent: *\nDisallow: /\n”;
}
ufw status
Status: active
To Action From
OpenSSH ALLOW Anywhere
8181/tcp ALLOW Anywhere
Nginx Full ALLOW Anywhere
443/tcp ALLOW Anywhere
80/tcp ALLOW Anywhere
3000 ALLOW Anywhere
OpenSSH (v6) ALLOW Anywhere (v6)
8181/tcp (v6) ALLOW Anywhere (v6)
Nginx Full (v6) ALLOW Anywhere (v6)
443/tcp (v6) ALLOW Anywhere (v6)
80/tcp (v6) ALLOW Anywhere (v6)
3000 (v6) ALLOW Anywhere (v6)
This was working at one point but I was using --standalone -d ttrss.shiromar.com, this would not auto renew for me.
I deleted all the keys using certbot delete --cert-name ttrss.shiromar.com.I can confirm the directory /letsencrypt/live only has the “README” file.
When I tried to create a new certificate I received the above error.
As I said this was working just yesterday but the certificate expired. I did check the IP on the server and has not changed and all the forwarding rules are still correct.
Any clues on where I went wrong?
–Thanks
