Challenge Failed

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., 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:

It produced this output:

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

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

Hi @piyush1973

your ip numbers ( ):

Host T IP-Address is auth. ∑ Queries ∑ Timeout A yes 2 0
AAAA yes C yes 1 0
A yes

First look, the answers are ok - port 80 is open.

Domainname Http-Status redirect Sec. G 200 3.360 H 200 0.350 H 200 1.900 N
Certificate error: RemoteCertificateNameMismatch 200 1.593 N
Certificate error: RemoteCertificateNameMismatch 200 0.374
Visible Content: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" ""> Curae 200 0.357
Visible Content: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" ""> Curae

But there is a http status 200, checking the not existing file /.well-known/acme-challenge.

And there

is a frame included.

<frame src="" frameborder="0" />

If you want a certificate with http-01 validation, your dns entry must use the and you must have an open port 80, not port 8080.

Or use dns-01 validation, then you don't need a running webserver.

I am still getting the same error.
Piyush Agarwal

I also get a “Connection reset by peer” error if I try to access it using curl.

It looks like the website blocks some clients based on the User-Agent header. A browser works – producing the iframe page – but other clients get the connection reset.

Rechecked your domain ( ):

Host T IP-Address is auth. ∑ Queries ∑ Timeout A yes 2 0
AAAA yes C yes 1 0
A yes

You didn't change your ip address.

There must be your 18.* address visible.

http + www now has a server error (bad gateway), the rest is the same.

Actually I am redirecting it from to 18.*
I am doing the same for two other websites and it is working

On which ip address runs your certbot?

184.* or 18.*

certbot is running on 18.*

And that can’t work, Letsencrypt sees:

your domain -> 184.* -> Letsencrypt checks the 184.*

I have updated the A entry . Now there are two ip addresses

If your certbot runs on the 18.*, certbot can't update the 184.* ip addresses.

So remove these entries complete, only

A -> 18.*

1 Like

Thank you. It s working now

1 Like

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