Setting up SSL certification for test domain with private IP

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:
adnetpub1.duckdns.org

I ran this command:
# certbot -v --nginx --test-cert
It produced this output:

We recommend selecting either all domains, or all domains in a VirtualHost/server block.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: adnetpub1.duckdns.org
2: www.adnetpub1.duckdns.org
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter 'c' to cancel):
Requesting a certificate for adnetpub1.duckdns.org and www.adnetpub1.duckdns.org
Performing the following challenges:
http-01 challenge for adnetpub1.duckdns.org
http-01 challenge for www.adnetpub1.duckdns.org
Waiting for verification...
Challenge failed for domain adnetpub1.duckdns.org
Challenge failed for domain www.adnetpub1.duckdns.org
http-01 challenge for adnetpub1.duckdns.org
http-01 challenge for www.adnetpub1.duckdns.org

Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
  Domain: adnetpub1.duckdns.org
  Type:   dns
  Detail: no valid A records found for adnetpub1.duckdns.org; no valid AAAA records found for adnetpub1.duckdns.org

  Domain: www.adnetpub1.duckdns.org
  Type:   dns
  Detail: no valid A records found for www.adnetpub1.duckdns.org; no valid AAAA records found for www.adnetpub1.duckdns.org

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.

Cleaning up challenges
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):
NGINX version 1.22.1

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

My hosting provider, if applicable, is:

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 2.6.0

I'm trying to create a test Letsencrypt SSL for a web server that would host "adnetpub1.duckdns.org" in an internal private network using a private IP (as opposed to a public IP). I'm getting the error above"

Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
  Domain: adnetpub1.duckdns.org
  Type:   dns
  Detail: no valid A records found for adnetpub1.duckdns.org; no valid AAAA records found for adnetpub1.duckdns.org
2

That isn't going to work. In order to validate your control of the domain, Let's Encrypt needs to be able to connect to your server--which means they need a public IP address that will reach your server.

5 Likes
3

Have a look here: Certificates for localhost - Let's Encrypt
You could also consider the DNS-01 challenge of the Challenge Types - Let's Encrypt

4 Likes
4

That error is to be expected.

Please read

to learn why your method using the http-01 challenge doesn't work with local IP addresses.

There is a third party DNS plugin for DuckDNS available at GitHub - infinityofspace/certbot_dns_duckdns: Plugin for certbot for a DNS-01 challenge with a DuckDNS domain.. That plugin is also available on snap apparently.

3 Likes
5

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