• 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 Plesk panel action log behind proxy

Martin_Sauer

Regular Pleskian
Plesk Onyx on CentOS

An nginx proxy is in front of the plesk login:
https://login.mydomain.tld <=> https://localhost:8443 via proxy_pass

Code:
        location / {
                proxy_pass https://myIP-address:8443;
                proxy_set_header Host             $host;
                proxy_set_header X-Real-IP        $remote_addr;
                proxy_set_header X-Forwarded-For  $proxy_add_x_forwarded_for;
        }

It works smooth and nice, except the panel-log /var/log/plesk/panel.log only shows the proxy-IP, not the requesting client IP. As a result Fail2Ban is unable to examine attacks.

Any solution?

Question 2: Plesk is sending E-Mails to new accounts (customer, Reseller,...) - How can I change the E-Mail cotnent to match different login details?
 
Back
Top