Http chllenge 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. 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: dufoo.com.mx

I ran this command: certbot --nginx

It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator nginx, Installer nginx

Which names would you like to activate HTTPS for?


1: dufoo.com.mx
2: www.dufoo.com.mx


Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter ‘c’ to cancel): 1,2
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for dufoo.com.mx
http-01 challenge for www.dufoo.com.mx
Waiting for verification…
Challenge failed for domain dufoo.com.mx
Challenge failed for domain www.dufoo.com.mx
http-01 challenge for dufoo.com.mx
http-01 challenge for www.dufoo.com.mx
Cleaning up challenges
Some challenges have failed.

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: dufoo.com.mx
    Type: dns
    Detail: DNS problem: query timed out looking up A for dufoo.com.mx

    Domain: www.dufoo.com.mx
    Type: dns
    Detail: DNS problem: query timed out looking up A for
    www.dufoo.com.mx

My web server is (include version): nginx 1.1.12.2

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

My hosting provider, if applicable, is: Oracle Cloud

I can login to a root shell on my machine (yes or no, or I don’t know):
yes with sudo su

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

Hi,

Could you please retry the operation, there might just be a glich in the system.

update: Different system yielded different result:
unboundtest and few other systems showed all clear, but Let’s Debug showed similar issue.
https://letsdebug.net/dufoo.com.mx/64791
https://unboundtest.com/m/A/dufoo.com.mx/HPDWRFW6

@_az What’s the reason for the “A record timeout”?
the DNSSEC response is signed too…

Thank you

Hi @rdufoo

looks like your name servers are a problem.

Different checks, different answers.

https://unboundtest.com/m/A/www.dufoo.com.mx/XFTZNLLX

without a result (a timeout). A few minutes earlier, a lot of “lame” results.

The non-www works - https://unboundtest.com/m/A/dufoo.com.mx/ZP6TVURI - but the www is terrible.

Ah, now the non-www has lame results:

query response was DNSSEC LAME

Hi,

I changed DNS provider to Cloudfare and got my certificates.

Thanks

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