• 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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