• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Let's Encrypt Timeout During Renewal

Epic Voyage

New Pleskian
I'm just going to put this here so that other people can find it. I had a server fail to renew its SSL Certficates from Let's Encrypt, and it gave us the following error when we tried to renew from the command line or web interface:

[2017-06-17 07:58:09] ERR [extension/letsencrypt] Cannot renew certificate on domain example.com with error: Challenge marked as invalid. Details: Fetching http://example.com/.well-known/acme-challenge/[random-random-random-random-random]: Timeout

It seems that the IPv6 configuration had been messed up and nobody noticed. Let's Encrypt attempted to contact us through the IPv6 address, which caused the timeout. Once the network issue was resolved, the Let's Encrypt extension went back to working correctly.
 
Thanks,

I for now deactivated IPV6 for the given domain which seam to work.

How did you fix this?
 
The answer will depend on your operating system, and is not something you can fix inside of Plesk. For us, on CentOS, we had to get the configuration resolved in /etc/sysconfig/network-scripts/ifcfg-eth0.
 
Back
Top