• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Wrong IP address in Apache logfile - not fixed by MU24 patch

Baxil

New Pleskian
Hi there,

We're running Plesk 12.0.18 on Ubuntu 14.04 LTS and are troubleshooting a site problem that made us realize that the only IP address showing up in the apache logs is the server address. Searching the KB, this appears to be the nginx problem described in http://kb.odin.com/en/123537 . However, that article says that it was fixed with microupdate #24. Our system has update #67. This doesn't appear to specifically be a MU67 problem as the IP issue appears to date at least as far back as July.

Per http://kb.odin.com/en/9294 , I tried using the following to reapply all patches:
/usr/local/psa/admin/sbin/autoinstaller --select-product-id plesk --select-release-current --reinstall-patch --install-component base

That completed successfully. No change after restarting both affected services, or rebooting the server.

Is anyone else having problems with the MU#24 nginx patch not applying? We haven't touched nginx's configuration, and I have very little experience with it so I'm not even sure what to look for in its config. How would I be able to manually verify in its config and/or code if the patch was properly applied? And/or, what other problems might cause this same symptom?

Log file sample:

1.2.3.4 - - [05/Oct/2015:15:09:21 -0700] "POST /wp-login.php HTTP/1.0" 200 4131 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.125 Safari/537.36"
1.2.3.4 - - [05/Oct/2015:15:09:56 -0700] "POST /wp-login.php HTTP/1.0" 200 1921 "http://www.oneofourdomains.com/wp-login.php" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:40.0) Gecko/20100101 Firefox/40.0"
1.2.3.4 - - [05/Oct/2015:15:19:53 -0700] "GET / HTTP/1.0" 200 5250 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/600.8.9 (KHTML, like Gecko) Version/8.0.8 Safari/600.8.9"
1.2.3.4 - - [05/Oct/2015:15:19:53 -0700] "GET /wp-content/themes/theme992/style.css HTTP/1.0" 200 5609 "http://oneofourdomains.com/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/600.8.9 (KHTML, like Gecko) Version/8.0.8 Safari/600.8.9"​

[All of the "1.2.3.4" entries above are our server's IP address, and the requests came from other sources.]
 
As a self-followup to this, I've now tried some further research and am no closer to resolving the problem.

http://talk.plesk.com/threads/plesk-12-over-nginx-problem-with-ip-address.306061/#post-763787 suggests changing the Apache configuration for the mod_remoteip module to add "RemoteIPHeader X-Real-IP". /etc/apache2/plesk.conf.d/server.conf looked like this:
<IfModule mod_remoteip.c>
RemoteIPInternalProxy (our public ipv4 address) (our ipv6 address) (the machine's other IPs)
RemoteIPHeader X-Forwarded-For
</IfModule>​

I changed it to the following and reloaded Apache:
<IfModule mod_remoteip.c>
RemoteIPInternalProxy (our public ipv4 address) (our ipv6 address) (the machine's other IPs)
# changing per http://talk.plesk.com/threads/plesk-12-over-nginx-problem-with-ip-address.306061/#post-763787 to fix logging problem
# RemoteIPHeader X-Forwarded-For
RemoteIPHeader X-Real-IP
</IfModule>​

No difference; the logs still come in with our server's IP address as the requesting host.
 
Igor, thank you for the link.

You were correct, the RPAF module was not listed in the output of apachectl -M. I attempted to activate it with mizar's instructions in the thread http://talk.plesk.com/threads/remote_addr-wrong-ip.335028/, and it failed with this error message:

Output of config test was:
apache2: Syntax error on line 140 of /etc/apache2/apache2.conf: Syntax error on line 1 of /etc/apache2/mods-enabled/rpaf.load: API module structure 'rpaf_module' in file /usr/lib/apache2/modules/mod_rpaf.so is garbled - expected signature 41503234 but saw 41503232 - perhaps this is not an Apache module DSO, or was compiled for a different Apache version?

So that's at least a starting point!
 
Back
Top