Certbot failed to authenticate some domains (authenticator: 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. 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:panel.yyyrfftf.pp.ua

I ran this command:bash <(curl -s https://pterodactyl-installer.se) (pterodactyl installer)

It produced this output:Requesting a certificate for panel.yyyrfftf.pp.ua

Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: panel.yyyrfftf.pp.ua
Type: connection
Detail: 51.20.35.206: Fetching http://panel.yyyrfftf.pp.ua/.well-known/acme-challenge/9Pnh9qOgdFrWMc_DU2evOxQDaqXLdZbcR4cdXFnz3ms: Timeout during connect (likely firewall problem)

Hint: The Certificate Authority failed to verify the temporary nginx configuration changes made by Certbot. Ensure the listed domains point to this nginx server and that it is accessible from the internet.

Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

  • WARNING: The process of obtaining a Let's Encrypt certificate failed!

My web server is (include version):~~~

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

My hosting provider, if applicable, is:Ubuntu 22.04.3 LTS

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

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

Welcome to the Let's Encrypt Community. :wave:

Your host needs to be reachable on port 80 from the internet. As you can see at the link below, it currently is not.

4 Likes

it is so how can i do that?

i should adjust DNS-records?

Inspect the configuration of all relevant network devices under your control on the ingress path to your host. Think along the lines of port forwarding and firewall rules.

5 Likes

Seems to be open now:

PORT    STATE    SERVICE
22/tcp  filtered ssh
80/tcp  open     http
443/tcp open     https
4 Likes

404 Not Found


nginx/1.18.0 (Ubuntu) - if I connect directly through the server ip. If you enter through the domain, it does not load.

Oops, sorry))) Restarting the server helped!

2 Likes