DNS DCV: No Local Authority

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: butterflyexpressions.org

I ran this command: Run AutoSSL

It produced this output: DNS DCV: No local authority: “butterflyexpressions.org”; HTTP DCV: The system queried for a temporary file at “http://butterflyexpressions.org/.well-known/acme-challenge/F21OEP174Z7KQ21FGU9K3TB931XNWRIT”, but the web server responded with the following error: 404 (Not Found). A DNS (Domain Name System) or web server misconfiguration may exist. The domain “butterflyexpressions.org” resolved to an IP address “69.16.249.215” that does not exist on this server.

My web server is (include version):

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

My hosting provider, if applicable, is: LiquidWeb

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):

What is the Internet IP of your server?

3 Likes

69.16.249.215

it may had some wired config. can you try certsage?

2 Likes

Have you tried asking your hosting support about that? Because that error comes from a check that AutoSSL does before requesting a cert from Let's Encrypt.

You are using the standard LiquidWeb DNS setup so something unusual must be going wrong. LiquidWeb should be able to sort that out for you. They setup AutoSSL and know best how it should work with their services.

As a work-around you might try disabling the "pre-check" that AutoSSL does. But, better is to have your hosting company fix the actual problem.

6 Likes