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:
I ran this command:
sudo certbot --apache
It produced this output:
can't validate DNS
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you're using Certbot):
I moved several sites from multiple hosts to one server. But i can't pass DNS checks and i eventually ended up with too many requests.
Hello @stefa, welcome to the Let's Encrypt community.
See Rate Limits - Let's Encrypt , searching for request on that page will help you find which limit you are running up against and how long you will have to wait before attempting again.
Also testing and debugging are best done using the Staging Environment as the Rate Limits are much higher. Rate Limits are per week (rolling).
Hi @Bruce5051! This is my first time having these, i've used Let'sEncypt many times before. Im getting this:
Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
Detail: DNS problem: NXDOMAIN looking up A for digitnaladosada.com - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for digitnaladosada.com - check that a DNS record exists for this domain
Detail: DNS problem: NXDOMAIN looking up A for www.digitnaladosada.com - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for www.digitnaladosada.com - check that a DNS record exists for this domain
Detail: DNS problem: NXDOMAIN looking up A for www.skatech.io - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for www.skatech.io - check that a DNS record exists for this domain
Wait... I think i got it.
I'm interested in knowing what you "got".
As the domains use different DNS servers:
digitalnadosada.com nameserver = ns77.domaincontrol.com
digitalnadosada.com nameserver = ns78.domaincontrol.com
skatech.io nameserver = dns1.registrar-servers.com
skatech.io nameserver = dns2.registrar-servers.com
sudarelite.com nameserver = ns31.domaincontrol.com
sudarelite.com nameserver = ns32.domaincontrol.com
That there is no cure for typos. First problem is that i mistyped my ansible script so it actually created a
digitlnadosada.com which is totally wrong domain. When i fixed that, next issue was a missing CNAME record on www for the other domain. After adding that, everything is peaches.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.