• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • 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 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