Http-01 challenge issue setting up certificates for the first time


#1

My domain is: test.travel.earth

I ran this command: sudo certbot --apache
sudo certbot --apache -d test.travel.earth

It produced this output:
sudo certbot --apache -d test.travel.earth
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache
Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for test.travel.earth
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. test.travel.earth (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://test.travel.earth/.well-known/acme-challenge/voZVf61NGAzmpq7hxfz4efHMRHePkyHY1sCK9AvS-ig: "<!doctype html>

<head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
    <meta htt"

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: test.travel.earth
    Type: unauthorized
    Detail: Invalid response from
    http://test.travel.earth/.well-known/acme-challenge/voZVf61NGAzmpq7hxfz4efHMRHePkyHY1sCK9AvS-ig:
    "<!doctype html>

    <head>
        <meta http-equiv="Content-Type" content="text/html;
    

    charset=utf-8">
    <meta htt"

    To fix these errors, please make sure that your domain name was
    entered correctly and the DNS A/AAAA record(s) for that domain
    contain(s) the right IP address.

My web server is (include version): Apache/2.4.6 (CentOS)

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

I can log in 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

Apart from that, I tried creating a directory at .well-known/acme-challenge/ and placed a test.html file and tried navigating it through the browser to check if I can reach it, and I was able to reach the page.


#2

Is test.travel.earth supposed to have two IP addresses?

test.travel.earth.  (insecure)  600  A  13.232.181.128
test.travel.earth.  (insecure)  600  A  184.168.131.241

The first IP has a /.well-known/acme-challenge/test.html page; the second IP returns a 404 Not Found error page starting with the HTML in the Let’s Encrypt error message.


#3

Hi Mnodhoff,

The First IP is the public ip of the server, while the second is the godaddy ip(we have setup the subdomain using godaddy), is there a way to resolve it.


#4

To use HTTP validation, you have to disable the GoDaddy URL forwarding thing for that subdomain.

The normal A record for 13.232.181.128 is the only one that should exist (for the sudomain).


#5

Hi mnordhoff,

Thanks for the help, removed extra A record and tried installing again, and it worked like charm.
Just one more thing, how did you get to know that it had two A name records.

Thank again.