• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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