Challenge failed for domain

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

I ran this command: Digital Ocean console setup

It produced this output: No SSL

My web server is (include version): Not sure

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

My hosting provider, if applicable, is: Digital Ocean

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

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): Not sure

I'm getting the following error when trying to set up Lets Encrypt, this has never happened before.

Challenge failed for domain www.www.yourwhispark.com
Challenge failed for domain www.yourwhispark.com

2

I know I messed up typing www.www.

The second one in which I didn't type www. prior the error said this:

Domain: www.yourwhispark.com
Type: connection
Detail: Fetching
http://www.yourwhispark.com/.well-known/acme-challenge/aWbXfCXPgOKHcBjJkyCjk0BR2qElabTGc2RreG8qR3Q:
Timeout during connect (likely firewall problem)

3

Got this error as well An unexpected error occurred:
The server will not issue certificates for the identifier :: Error creating new order :: Cannot issue for "www.your_domain": Domain name contains an invalid character (and 1 more problems. Refer to sub-problems for more information.)

4

I bought a new domain to test set up with Digital Ocean and it failed on that to.

Challenge failed for domain thewhispark.com
Challenge failed for domain www.thewhispark.com

5

You need a functional HTTP site before you can secure it (via HTTP authentication).
*** 8.8.8.8 can't find yourwhispark.com: Server failed
*** 8.8.8.8 can't find www.yourwhispark.com: Server failed

1 Like
6 
nslookup -q=ns yourwhispark.com. a.gtld-servers.net.
yourwhispark.com        nameserver = ns1.digitalocean.com.
yourwhispark.com        nameserver = ns2.digitalocean.com.
yourwhispark.com        nameserver = ns3.digitalocean.com.

nslookup -q=ns yourwhispark.com. ns1.digitalocean.com.
Server:         ns1.digitalocean.com.
Address:        173.245.58.51#53
** server can't find yourwhispark.com: REFUSED
1 Like
7

Looks like you got this working on these new domain names. Do you still need help?

I see the same as @rg305 for your old domain names. It seems your DNS records for it are missing.

2 Likes
8

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