Some challenges have failed

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: realsoftware.pro

I ran this command:
sudo certbot --apache -d test.realsoftware.com

It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for test.realsoftware.com

Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
Domain: test.realsoftware.com
Type: dns
Detail: DNS problem: NXDOMAIN looking up A for test.realsoftware.com - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for test.realsoftware.com - check that a DNS record exists for this domain

Hint: The Certificate Authority failed to verify the temporary Apache configuration changes made by Certbot. Ensure that the listed domains point to this Apache 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):
Apache/2.4.52 (Ubuntu)

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

My hosting provider, if applicable, is:

My domain provider
hostinger

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, i am not using cpanel

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 @zubair999

The --apache option uses an HTTP Challenge. This challenge requires an A and/or AAAA address in the public DNS to name the public IP. The Let's Encrypt servers uses that public IP to send the challenge.

You don't have the required record(s) in your DNS for the test subdomain. You do for your registered domain but not the test subdomain.

3 Likes

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