/.well-known/acme-challenge/ timeout

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:
carlosmedina.tk
I ran this command:
sudo certbot --apache -d carlosmedina.tk
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for carlosmedina.tk
Enabled Apache rewrite module
Waiting for verification…
Cleaning up challenges
Cleaning up challenges
Failed authorization procedure. carlosmedina.tk (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://carlosmedina.tk/.well-known/acme-challenge/CmFfD28Y8F5lXxDjxn9jku7p7w6yCC69oPybd7xAWDk: Timeout after connect (your server may be slow or overloaded)

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: carlosmedina.tk
    Type: connection
    Detail: Fetching
    http://carlosmedina.tk/.well-known/acme-challenge/CmFfD28Y8F5lXxDjxn9jku7p7w6yCC69oPybd7xAWDk:
    Timeout after connect (your server may be slow or overloaded)

    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. Additionally, please check that
    your computer has a publicly routable IP address and that no
    firewalls are preventing the server from communicating with the
    client. If you’re using the webroot plugin, you should also verify
    that you are serving files from the webroot path you provided.
    My web server is (include version):

The operating system my web server runs on is (include version):
debian 10 (buster)
My hosting provider, if applicable, is:
Me :slight_smile:
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):
certbot 0.31.0

I’ve been trying many different commands to install a cert but i get this error every single time. Looking for guidance on where to go. Do i need to make a new folder in my /var/www/html/ dir?

1 Like

Your current setup won’t work.

carlosmedina.tk seems to be a web server run by .tk. http://carlosmedina.tk/ has a frame with your IP address; meanwhile they drop requests to the Let’s Encrypt validation URLs.

Also, the IP address – 192.168.0.80 – is not public. It’s a private address that only works on your LAN.

The current forwarding setup makes HTTP validation impossible, and it may also make setting up HTTPS difficult (since certificates would have to be installed on .tk’s web server and on your web server).

If possible, you should put your public IP address in your DNS records. Not Freenom’s “forwarding” or whatever it’s called.

1 Like

So a 172 address is in my cloudflare DNS yet on freenom I have the url fowarding to the 192, should i change the freenom fowarding to the cloudflare dns ip?

Your domain isn’t using Cloudflare’s DNS. It’s using the .tk or Freenom DNS.

Nope, it wasn’t and did not have any name server. It’s fixed now and I have the certs installed. Only thing now is I keep getting a redirect error which ill post about, thanks.

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