Can't get configure ssl for nginx

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., so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: /

I ran this command:

sudo certbot --nginx -d -d

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator nginx, Installer nginx
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for
http-01 challenge for
Waiting for verification…
Challenge failed for domain
Challenge failed for domain
http-01 challenge for
http-01 challenge for
Cleaning up challenges
Some challenges have failed.


My web server is (include version):

nginx version: nginx/1.18.0 (Ubuntu)

The operating system my web server runs on is (include version):

Distributor ID: Ubuntu
Description: Ubuntu 20.04.1 LTS
Release: 20.04
Codename: focal

My hosting provider, if applicable, is:

self-hosted, but port 80 forwarded properly, - is accessible

I can login to a root shell on my machine (yes or no, or I don’t know):


I’m using a control panel to manage my site (no, or provide the name and version of the control panel):


The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):


Hi @ElderOrb

no, I can’t open your site. Same your check, ~~1,5 hours old -

Domainname Http-Status redirect Sec. G -14 10.014 T
Timeout - The operation has timed out -14 10.047 T
Timeout - The operation has timed out -14 10.014 T
Timeout - The operation has timed out
Visible Content:

Only timeouts.

A working port 80 is required, if you want to use http validation.

1 Like

Thanks for a good catch! I’ve tried using vpn and found this ‘public ip’ is public only when used from inside Belarus. :frowning: What is even more frustrating, my internet provider can do nothing about this and says its just fine on their side. Anyway, definitely not letsencrypt issue.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.