No valid A records found for panel

Help
1

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.united-snakes.com

I ran this command: certbot certonly --nginx -d panel.united-snakes.com

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for panel.united-snakes.com

Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
** Domain: panel.united-snakes.com**
** Type: dns**
** Detail: no valid A records found for panel.united-snakes.com; no valid AAAA records found for panel.united-snakes.com**

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.

My web server is (include version): I'm not sure. Running on a machine I own.

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

My hosting provider, if applicable, is: godaddy for web address

I can login to a root shell on my machine (yes or no, or I don't know): yes, I am running my commands through root

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): I am setting up a pterodactyl panel here.

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

2

Also may be pertinent info, I do in fact own this dns address and it points to the public IP of my server

3

When you posted initially there was not an A record in the DNS for your panel subdomain.

There is now but HTTP requests to that domain on port 80 are failing. This is most often a firewall although can be other things.

The Let's Debug test site is very helpful for checking new setups. See:

You could also try using a different device on the public internet to try an HTTP connection. For example, a mobile phone with wifi disabled so using using carrier's network. Often times connections on your local network work but connections from the public internet fail if your comms are not setup right.

2 Likes
4

Thanks, simply altering my firewall parameters for port 80 worked. I should have guessed the answer would be so obvious as a firewall not allowing port 80 through on my machine. I have done networking to host my own custom servers plenty of times before and had to alter my firewall then also but for some reason it went right over my head this time. Thanks.

2 Likes