• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

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