• 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.

Issue Let's encrypt renewal fails since update to Plesk 18.0.27 Update #1

peterbo

New Pleskian
Since the update, I get the error message below, when the SSL extension tries to auto-renew a certificate:

Code:
Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/12345.
Details:
Type: urn:ietf:params:acme:error:connection
Status: 400
Detail: Fetching https://example.com/.well-known/acme-challenge/xxx: Timeout during connect (likely firewall problem)

I read about that it's problematic to have the automatic 301 redirection to https active. Disabling it and renewing manually works, but I can't do that for hundreds of domains. What is a practicable workaround for that?
 
Please make sure that either all your DNS settings off the domain point to the correct host where you try to use SSL on. For example, if you have IPv4 and IPv6 configured, both must correctly point to the target domain on the server, else you'll see the 400 error in let's Encrypt, because their systems might not be able to reach the domain through the configured routes.
 
Hi Peter,
thanks for your suggestions, everything is setup correctly. Connections via ipv4 / ip6 are successful (accessible from remote / different networks, the .well-known folder and its contents are callable). The reason is the mentioned redirection. Disabling it solves the problem. This problem arose with the Update to 18.0.27, no other changes made to the domains. But I can't disable / re-enable this redirection for hundreds of domains.
 
Back
Top