I ran this command: certbot --authenticator webroot --webroot-path=/var/www/letsencrypt --installer nginx --email xxxxx@yyyyyy.zzz --non-interactive --domain wedpics.mooo.com --agree-tos
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer nginx
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for wedpics.mooo.com
Using the webroot path /var/www/letsencrypt for all unmatched domains.
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. wedpics.mooo.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://wedpics.mooo.com/.well-known/acme-challenge/5CC5HIR22xzyRqZzUnqKJodDNFsy6R9x9VssVoew3Pk: Timeout during connect (likely firewall problem)
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: wedpics.mooo.com
Type: connection
Detail: Fetching
http://wedpics.mooo.com/.well-known/acme-challenge/5CC5HIR22xzyRqZzUnqKJodDNFsy6R9x9VssVoew3Pk:
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.14.0
The operating system my web server runs on is (include version):
debian stretch (9)
My hosting provider, if applicable, is:
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
I am starting to consider networking a form of voodoo.
I ran:
$ nmap wedpics.mooo.com
Starting Nmap 7.40 ( https://nmap.org ) at 2018-05-17 21:53 CEST
Nmap scan report for wedpics.mooo.com (80.219.237.67)
Host is up (0.0051s latency).
rDNS record for 80.219.237.67: 80-219-237-67.dclient.hispeed.ch
Not shown: 997 filtered ports
PORT STATE SERVICE
22/tcp open ssh
80/tcp open http
443/tcp open https
And then logged in via ssh. When visiting the webpage, I am forced to use https and there is a tls handshake failure (of course). I seem to be running in circles. Any help would be greatly appreciated.
I can’t access your site at all in HTTP or HTTPS, which makes me think that the error message is probably right—there may be a firewall preventing the general public from reaching your site. Have you tried accessing it from somewhere other than the local network?
I am pretty sure that’s not the case. The broadband mobile is provided by a different company, I think. Why do you ask? You are wondering why you see a different internet that I do?
Yes, exactly. I imagine that the Let's Encrypt CA is ending up with effectively the same view of your server that I have (in which these ports appear as filtered and don't respond to the TCP connection), so I wonder why that's true for some Internet users but not from your perspective on the Internet.