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

Issue Bug in mod_rpaf with IPv6?

HostaHost

Regular Pleskian
Hi all, curious if anyone knows of a bug in the mod_rpaf with IPv6 addresses? I've got a CentOS 6 server, Plesk 12.5, nginx+apache. Inbound requests from IPv4 addresses are properly logged to the apache logs with their real IP address, IPv6 requests end up logged with the site IP rather than the real remote IP.
 
I haven't seen it in a while; at some point Plesk switched to using mod_remoteip instead and the problem went away. We're running it with nginx+apache and ipv6 on the sites. I just tested and my real IPv6 is being logged when I browse sites.
 
Back
Top