• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • 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.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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