Failed to get SSL certificate when though I have already added the A Record

Hi all, kindly need your help and guidance for the issue I am currently facing

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: heraurra.com

I ran this command: sudo certbot --nginx -d admin.heraurra.com -d www.admin.heraurra.com

It produced this output:
Requesting a certificate for admin.heraurra.com and www.admin.heraurra.com
Performing the following challenges:
http-01 challenge for www.admin.heraurra.com
Waiting for verification...
Challenge failed for domain www.admin.heraurra.com
http-01 challenge for www.admin.heraurra.com

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

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.

My web server is (include version): nginx/1.18.0

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

My hosting provider, if applicable, is: Domainesia.com

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 3.1.0

Hi @anthonylauly,

Seems like it is likely there is no A record (or CNAME) for the www subdomain.

Hi @Bruce5051 ,

Thank you for the feedback. But if I refer to DNS Propagation Checker - Global DNS Testing Tool for the DNS checker, both admin.heraurra.com and www.admin.heraurra.com is successfully traced.

Does that problem still occur?

Because I cannot reproduce it using various tools right now. One of which is Let's Debug: Let's Debug

I see some errors on DNSViz from some of your name servers. I couldn't reproduce the NXDOMAIN using unboundtest but if the same error is continuing it might be worth asking your DNS provider about the DNSViz report

https://dnsviz.net/d/www.admin.heraurra.com/dnssec/

https://unboundtest.com/

1 Like

Here admin.heraurra.com - Make your website better - DNS, redirects, mixed content, certificates is reporting "DNS-problem - authoritative Nameserver refused, not defined or timeout".

And here EDNS Compliance Tester is showing issues with the name servers for the domain name heraurra.com

1 Like

Okay, I will try to ask my DNS Provider. But, if I am able to access http://admin.heraurra.com successfully. Does this prove something ? Can I still jump to the conclusion that the problem is on the Domain and not the Computing Server I am using ?

Problem Solved. Thank you @Bruce5051

2 Likes

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