• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

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