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

Logformat

Frater

Regular Pleskian
I am considering to use a reverse-proxy for http on the system where Plesk is installed.

When I do I will need to use a different 'LogFormat=' in Apache because all traffic will otherwise be logged as coming from the proxy (the same IP as the server)

This is working on a normal Apache config...

/etc/apache2/conf.d/proxy:

SetEnvIf X-Forwarded-For "^.*\..*\..*\..*" is-forwarder

LogFormat "%h %v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_non_proxy
LogFormat "%{X-Forwarded-For}i %v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_proxy

/etc/apache2/sites-available/default:
CustomLog /var/log/apache2/access.log vhost_proxy env=is-forwarder
CustomLog /var/log/apache2/access.log vhost_non_proxy env=!is-forwarder

It now seems each site has their own customlog....
What's the most elegant solution to make Plesk reverse-proxy aware?

I wouldn't mind a solution where both IP's are logged (otherwise I wouldn't get the IP of a foreign proxy in case the reverse proxy on the local machine is turned off). But I think this will confuse some statistics scripts....
 
Back
Top