I tried to manually generate Let’s Encrypt Certificates, and that’s what I got out:
pi@raspberrypi:~ $ wget https://dl.eff.org/certbot-auto
--2018-02-10 21:09:50-- https://dl.eff.org/certbot-auto
Resolving dl.eff.org (dl.eff.org)... 2a04:4e42:1b::201, 22.214.171.124
Connecting to dl.eff.org (dl.eff.org)|2a04:4e42:1b::201|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 61939 (60K) [application/octet-stream]
Saving to: ‘certbot-auto.2’
certbot-auto.2 100%[===================>] 60.49K --.-KB/s in 0.05s
2018-02-10 21:09:51 (1.26 MB/s) - ‘certbot-auto.2’ saved [61939/61939]
pi@raspberrypi:~ $ chmod a+x certbot-auto
pi@raspberrypi:~ $ ./certbot-auto certonly --agree-tos --email email@example.com --standalone -d
Requesting to rerun ./certbot-auto with root privileges...
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for xx.xxx.com
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. xx.xxx.com (http-01): urn:acme:error:connection :: The server could not connect
to the client to verify the domain :: Fetching http://xx.xxx.com/.well-known/acme-
- The following errors were reported by the server:
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.
Here on forums, I replaced email and domain name with “x”-es, but I entered the right informations when creating the SSL certificates. If you want to check the domain, feel free to PM me.