• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Apache server status page showing server IP's only

Chris1

Regular Pleskian
Hello,

I know this isn't directly related to Plesk but hopefully someone can help me.

I've got a few Plesk servers and in the past activating the server status page on CentOS6 was easy, I just added the following to the /etc/httpd/conf/httpd.conf file:

Code:
ExtendedStatus On
<Location /server-status>
    SetHandler server-status
    Order deny,allow
    Deny from all
    Allow from <my_ip>
</Location>

When I do this on a CentOS7 server, the server status page comes up but it seems to be giving different information. The heading is "Apache Server Status for hostname (via 111.111.111.11)" and all the domains in the vhost column have the port 7080 attached to them and in the client column, all the IP's are that of the server (111.111.111.111). Is this showing the nginx stuff instead of Apache?

The server-status page on my CentOS6 server has the title "Apache Server Status for 222.222.222.222", it doesn't have that "via 222.222.222.222" part, it shows the real IP of the visitor and it doesn't have this port of 7080 attached to the vhost.

Why are these different, how can I get the server status output on the CentOS 7 server similar to that of the CentOS 6 server?
 
I reproduce this problem on CentOS 7 - it seems the problem in Apache 2.4 mod_remoteip doesn't affect mod_status
 
Hi @vlikhtanskiy here is the output of that command
Code:
[root@server ~]# apachectl -M | grep remoteip
[Wed Oct 21 09:53:51.972555 2015] [so:warn] [pid 543132] AH01574: module actions_module is already loaded, skipping
[Wed Oct 21 09:53:52.076720 2015] [so:warn] [pid 543132] AH01574: module headers_module is already loaded, skipping
[Wed Oct 21 09:53:52.096697 2015] [so:warn] [pid 543132] AH01574: module logio_module is already loaded, skipping
[Wed Oct 21 09:53:52.147407 2015] [so:warn] [pid 543132] AH01574: module suexec_module is already loaded, skipping
[Wed Oct 21 09:53:52.767398 2015] [so:warn] [pid 543132:tid 140076835534912] AH01574: module fcgid_module is already loaded, skipping
remoteip_module (shared)

Hi @mizar , thanks for looking into that, at least I know it's not just isolated to my server. Would you happen to know of any workarounds?
 
Back
Top