• 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 nginx + apache + plesk = wrong REMOTE_HOST value

Kitty

New Pleskian
Hi there,

Im running the latest plesk onyx (web admin) on apache2 + nginx on an Ubuntu 16.04 vps.

My issue is that after enabling HostnameLookups in apache2.conf, the REMOTE_HOST value contains the domain name of the website, not the hostname based on the user's IP.

This value is only wrong when I access the server via nginx (port 80), if I connect directly to apache via port 7080 it's correct.

Is this a plesk issue or apache?
 
Ah yes I've tried the rpaf module. It actually makes "REMOTE_HOST" correct, but it then unfortunately breaks the "REMOTE_ADDR" values (becomes the server public IP).

The remoteip module is running on the server, which supposedly superceded rpaf a few years ago. I believe this module (remoteip) is the reason why the REMOTE_ADDR contains the correct client IP address, but fails with REMOTE_HOST.
 
Back
Top