• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Let's Encrypt renewal cause 502 Bad Gataway

J

jarred_cz

New Pleskian
Hallo there.
Each SSL renewal attempt cause temporary "502 Bad Gateway". I understand it's need to refresh server config, but with almost 150 domains on the server (each with approx 3 subdomains), our server is down few times a day because there still some renewal attempts.
Is there any chance to merge those attempts to dedicated time?
Thanks for any tips!
 

Attachments

  • ssl-attempts.png
    ssl-attempts.png
    16.4 KB · Views: 10
You must log in or register to reply here.

Similar threads

I
Resolved Preventing bot brute force probes against Postfix/SMTP
Replies
5
Views
1K
iainh
I
H
Resolved Laravel app "502 Bad Gateway" on page reload only
Replies
2
Views
4K
halnex
H
S
Question How To Renew Let's Encrypt SSL On Sites Without Plesk Panel Access (SSH)
Replies
3
Views
4K
xdjxdaveyx
xdjxdaveyx
Epic Voyage
Resolved Could not issue/renew Let's Encrypt certificates for <customer>
Replies
4
Views
4K
Kaspar@Plesk
Kaspar@Plesk
P
Question Plesk login 8443 cannot be called up
Replies
8
Views
6K
Kaspar@Plesk
Kaspar@Plesk
Back
Top