• 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.

Access logs on 12.5 logging destination IP not remote IP

tech01

Basic Pleskian
Access logs on 12.5 logging destination IP not remote IP

xxx.xxx.xxx.xxx - - [22/Oct/2015:14:56:07 -0400] "GET / HTTP/1.0" 302 263 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" www.exampledomain.com

where xxx.xxx.xxx.xxx is equal to the ip assigned to the exampledomain on the server... This was not always this way and I'm not sure what changed.
 
Good to see you are still around IgorG :)

Ended up filling out a support request, the support agent advised the following:
"In order to fix this issue, I have edited /etc/httpd/conf.d/rpaf.conf file
The loadmodule "LoadModule rpaf_module modules/mod_rpaf.so" was commented out.
I have uncommented this statement."

We are now up and running again with our logs. This was in fact an issue with the upgrade process. Not sure what happened but we did use "plesk repair all" at one point.
 
Back
Top