• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved Let's Encrypt Timeout During Renewal

Epic Voyage

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.
 
You must log in or register to reply here.

Similar threads

R
Issue Problems Issuing a Let's Encrypt Certificate
Replies
6
Views
718
Robin McDermott
R
L
Issue ( authorization token is unavailable ) Could not issue/renew Let`s Encrypt certificates
Replies
7
Views
2K
Leta
L
Bitpalast
Resolved SSL create and renew errors on random domains / possibly a Let's Encrypt issue, but maybe only in combination with Plesk
Replies
11
Views
2K
Change Maker
C
D
Issue Lets Encrypt Not Successful over port 80
Replies
8
Views
3K
Daiv
D
K
Question Renewing Let's Encrypt with external DNS servers
Replies
5
Views
2K
klowet
K
Back
Top