My domain is: staging-api-batiment.wamland.com
I ran this command:
certbot certonly --webroot --webroot-path=/home/rails/rails_project/public -d staging-api-batiment.wamland.com
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for staging-api-batiment.wamland.com
Using the webroot path /home/rails/rails_project/public for all unmatched domains.
Waiting for verification...
Cleaning up challenges
Unable to clean up challenge directory /home/rails/rails_project/public/.well-known/acme-challenge
Failed authorization procedure. staging-api-batiment.wamland.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://staging-api-batiment.wamland.com/.well-known/acme-challenge/iUyK682qcwpQSr6UUMZpA9YV2UwEZhR50cSALbPMMg4: Timeout
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: staging-api-batiment.wamland.com
Type: connection
Detail: Fetching
http://staging-api-batiment.wamland.com/.well-known/acme-challenge/iUyK682qcwpQSr6UUMZpA9YV2UwEZhR50cSALbPMMg4:
Timeout
The web server runs on: nginx version: nginx/1.4.6 (Ubuntu)
The operating system my web server runs on is (include version): Ubuntu server 14.04
My hosting provider, if applicable, is: Digitalocean
I can login to a root shell on my machine (yes or no, or I don’t know): Yes. However, I’m using a user account with sudo grant.
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): No
Few months ago, I didn’t have any problem set up Let’s encrypt on my Digitalocean servers. In fact, several servers already have SSL protocol in place. However, recently I’m not able at all to make it work. I’ve checked that I can have access from the browser to http://staging-api-batiment.wamland.com/.well-known/acme-challenge/test.html
and it does works.
Also, I’ve been investingating about the IPv6 problem and my domain does not appear to have any AAAA
record:
dig staging-api-batiment.wamland.com A +short
==> Output: 128.199.22x.xxx
dig staging-api-batiment.wamland.com AAAA +short
==> Output: Nothing
Is there someone having a similar issue and knows how to fix it?