Error: Let's Encrypt SSL certificate installation failed: Challenge marked as invalid. Details: Fetching http://bc.guide/.well-known/acme-challenge/tqzVGiWsXQurmn9DL-DFcrmT-SmaaGrA915QRsoY_Ik: Timeout

Help
1

Please fill out the fields below so we can help you better.

My domain is:bc.guide

I ran this command:renew cert in plesk 17.5.3#10

It produced this output: Error: Let’s Encrypt SSL certificate installation failed: Challenge marked as invalid. Details: Fetching http://bc.guide/.well-known/acme-challenge/tqzVGiWsXQurmn9DL-DFcrmT-SmaaGrA915QRsoY_Ik: Timeout

My web server is (include version): basic is server deb min, with proxmox, some ip`s, all VM with plesk

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

My hosting provider, if applicable, is: 1and1

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

THANKs 4 Helping me …

2

From [where i am], connecting to http://bc.guide/ over IPv4 returns “Connection refused”, and IPv6 times out. Are you sure the DNS records, firewall settings and network configuration are correct?

Also, for https://bc.guide/, IPv4 uses a self-signed certificate (probably not surprising), but IPv6 also times out.

1 Like
3

Hi, it worked fine, till last week…
and sure… i never touched a running system…
BUT, yes perhaps, DNS is confused, so domains is hosted by godaddy, server by 1and1,
and a complex ip routing voodoo…

4

All is checked, domains running without ssl… cms on bc.guide , chat on bc.guide:666
BUT CertBot still deliver same errror …timeout… :cry:

5

The problem is clearly that the site is timing out when accessed over IPv6.

The best thing to do would be to get whoever is responsible (maybe you?) to fix the IPv6 connectivity so that the site can be reached correctly in IPv6. Alternatively, you can remove the AAAA record in DNS.

6

i try, but AAAA is by godaddy dns settings a required field :frowning:

7

OK,
we will try to make for server/VM`s a ipv6NAT too…
thanks for help :wink:

8

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