• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Recent content by dairuru

  1. D

    Issue Incorrect logging of IP from Plesk Windows under Reverse Proxy

    Thank you for the reply scsa20, there was a progress but I'm still having issues. X-Forwarded-For IP is showing correctly when on HTTP, but not on HTTPS. HTTPS connections still shows the internal IP only. Contacted FortiWeb support and waiting for they reply, might be an issue on their end I...
  2. D

    Issue Incorrect logging of IP from Plesk Windows under Reverse Proxy

    Noticed that I had a typo error from my previous comment, it should be "*reverse proxy server", not "proxy server". Our firewall is FortiGate, then connected to FortiWeb as the reverse proxy server. And we have configure the reverse proxy server to forward X-Forwarder-For. As mentioned, we have...
  3. D

    Issue Incorrect logging of IP from Plesk Windows under Reverse Proxy

    Settings are already configure from the reverse proxy server, but not logging properly from Plesk Web server. We are using Fortiweb behind another firewall. That was my first hunch, to check the reverse proxy server. But that's the thing, already consulted with their technical engineer and...
  4. D

    Issue Incorrect logging of IP from Plesk Windows under Reverse Proxy

    We have a Plesk under Window Server and is running behind Reverse Proxy server. We would like to log the real public IP of web visitors, but all we can see is the Internal IP of Reverse Proxy Server. I'm thinking that x-forwarded-for or other x-headers could resolve it. Tried to lookup some...
Back
Top