• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

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