A
A
Alexander Semenenko2017-11-19 14:37:10
Nginx
Alexander Semenenko, 2017-11-19 14:37:10

How to install ssl let's encrypt certificate?

I did the following:
- I configured ddns on Mikrotik, now I have a level 4 domain that refers to the ip address of my router.
- On the router forwarded port 8085 to the local web server, port 80.
- In the browser behind nat I write my domain, port 8085, I get to nginx
I try to get a certificate with this command:
sudo certbot certonly -a webroot --webroot-path=/var/www/html -d xxxxxxxx.xx.xxxxxxxxx.net
Here is the output :
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for xxxxxxxx.xx.xxxxxxxxxx.net
Using the webroot path /var/www/html for all unmatched domains.
Waiting for verification...
Cleaning up challenges
Unable to clean up challenge directory /var/www/html/.well-known/acme-challenge
Failed authorization procedure. xxxxxxxx.xx.xxxxxxxxx.net (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching xxxxxxxxx.xx.xxxxxxxxxxx.net/.well-known/ acme-chal... Timeout
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: xxxxxxxx.xx.xxxxxxxxxx.net
Type: connection
Detail: Fetching
xxxxxxxxxxxx.xx.xxxxxxxx.net/.well-known/acme-chal...
Timeout
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.
Did you do something wrong in the nginx settings? Or somewhere I need to specify that my port is 8085? Or maybe due to the fact that port 443 is still closed for the web server? If you need additional infa, I will provide.

Answer the question

In order to leave comments, you need to log in

1 answer(s)
W
Wexter, 2017-11-19
@semenenko88

Domain validation goes on port 80, forward port 80 to the server and then everything will work.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question