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

Question Let´s Encrypt and reverse proxy

KristallCarlo

New Pleskian
We want to install a second plesk server. We also want to use 1 public ip-address. Therefore we have to install a reverse proxy (haproxy) which will redirect the incoming requests.
The domains in plesk are using Let's Encrypt and this can be an issue. When haproxy is active the let's encrypt server can't communicate anymore with the plesk server. Is there a workaround for this ?

Or is there a better methode to use 2 plesk servers with one 1 public address and Let´s Encrypt.
 
Back
Top