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. https://crt.sh/?q=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: www.apostolosandreaswindsor.com

I ran this command:sudo certbot

It produced this output:
Performing the following challenges:
http-01 challenge for apostolosandreaswindsor.com
http-01 challenge for www.apostolosandreaswindsor.com
Waiting for verification...
Challenge failed for domain apostolosandreaswindsor.com
Challenge failed for domain www.apostolosandreaswindsor.com
http-01 challenge for apostolosandreaswindsor.com
http-01 challenge for www.apostolosandreaswindsor.com
Cleaning up challenges
Some challenges have failed.

IMPORTANT NOTES:

My web server is (include version): apache

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

My hosting provider, if applicable, is: amazon aws

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

2 Likes
#2

Welcome to the Let's Encrypt Community, Marios :slightly_smiling_face:

You say that you are using Apache as your webserver, but for some reason I'm getting a 200 OK response from Nginx for ANYTHING I request (even things that don't exist).

>>> http://apostolosandreaswindsor.com/.well-known/acme-challenge/test

> --------------------------------------------
> 200 OK
> --------------------------------------------

Status: 200 OK
Code: 200
Server: nginx/1.16.1
Date: Tue, 01 Dec 2020 17:59:32 GMT
Content-Type: text/html; charset=utf-8
Connection: close

>>> http://www.apostolosandreaswindsor.com/.well-known/acme-challenge/test

> --------------------------------------------
> 200 OK
> --------------------------------------------

Status: 200 OK
Code: 200
Server: nginx/1.16.1
Date: Tue, 01 Dec 2020 17:59:19 GMT
Content-Type: text/html; charset=utf-8
Connection: close

It looks like you have GoDaddy site redirection active, which will definitely interfere with acquiring a certificate via http-01 validation. I'm guessing there's an opaque (masking) redirection?

3 Likes
#3

Indeed I use it. I changed the redirect to my webserver.

As I am noob on this, how can I make it work as expected in go daddy? It seems that I cannot change the A name.

2 Likes
#4

Not a problem. :slightly_smiling_face:

Fortunately for you, I'm one of the few regulars (maybe the only regular) around here that has used GoDaddy for years.

  1. Turn off the redirect and wait for it to clear.
  2. Your A record should be "Parked".
  3. Change the A record of your DNS to point to your actual webserver.

Can you take a screenshot of all of your DNS records in your GoDaddy account?

3 Likes
#5

@griffin thanks for your help. I followed your instructions and I managed to get the certificate. However when I try to go to my website I got this:

Destination

Unknown

Everything's working on our side, so the link you clicked is either wrong or has been retired.

except from the A should I change something else? My A now is the IP of my webserver. When I call it directly I can see my website. When I use the www.apostolosandreaswindsor.com I get an error.

3 Likes
#6

No errors from my perspective.
Screenshot_1 Screenshot_2

4 Likes
#7

:partying_face:

Looking great here too!

If you're experiencing errors, try clearing your cache.

Screenshot_20201201-130755_Samsung Internet
Screenshot_20201201-130755_Samsung Internet1439×2724 306 KB

4 Likes
#8

I have never used them to host my sites, but I have a decade working with them as one of my registrars..

2 Likes
#9

You've only had half the fun!?

:grin:

Really though, the registrar portion is where most of the weirdness occurs. Glad to have a fellow GoDaddy victi... user.

2 Likes
#10

Just don't make the mistake of covering a mail subdomain with a certificate and then try using it for outbound (SMTP) connections. You'll have to accept "all certificates". Best to use the GoDaddy hosting instance name in your email software.

2 Likes
#11

hi all, thanks for your help and specially @griffin!!

It works as expected now :slight_smile:

4 Likes
#12

You are quite welcome. Happy to see things resolved so expediently! :slightly_smiling_face:

3 Likes
#13

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