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. crt.sh | 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:servicios.poblado.alarmar.com.co
I ran this command:certbot
It produced this output:
root@servicios:~# certbot
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache
Which names would you like to activate HTTPS for?
1: servicios.poblado.alarmar.com.co
Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter 'c' to cancel): 1
Cert is due for renewal, auto-renewing...
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for servicios.poblado.alarmar.com.co
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. servicios.poblado.alarmar.com.co (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: 201.184.143.221: Fetching http://servicios.poblado.alarmar.com.co/.well-known/acme-challenge/n1tqKwZZSfQd1aaa7siVubzAO0i6XgVpdXOVqp3FRto: Error getting validation data
IMPORTANT NOTES:
-
The following errors were reported by the server:
Domain: servicios.poblado.alarmar.com.co
Type: connection
Detail: 201.184.143.221: Fetching
http://servicios.poblado.alarmar.com.co/.well-known/acme-challenge/n1tqKwZZSfQd1aaa7siVubzAO0i6XgVpdXOVqp3FRto:
Error getting validation dataTo 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): ubuntu 16.04
I can login to a root shell on my machine (yes or no, or I don't know): yes
I also check the firewall rules and I see that the traffic is being accepted by ports 80 and 443, but it still shows me the news
1175K 71M SYS_HTTPS tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:80
579K 94M SYS_HTTPS tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:443