• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

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