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

remote_addr

  1. P

    Question Getting X-Forwarded-For IP address from behind a nginx proxy server

    I've got a Plesk server sitting behind a Ngnix Proxy Manager. I am receiving correct HTTP_X_FORWARDED_FOR & HTTP_X_REAL_IP from the ngnix proxy on requests forwarded to domains on the Plesk server. Here's my topology: However, I can't figure out how to get the Apache log files to show the...
  2. Ehud

    Question Integrating AbuseIPDB RealTime IP Check, possibly using ModSecurity and LUA

    Hi, I would like to check IPs connecting ports as 80 and 443, on real-time, against data base of abusing IPs, as abuseupdb.com. I have an API key, which allows curl checks. A test may look like this: Where the results would look like this: I also use ModSecurirty, that enables LUA...
    • Ehud
    • Thread
    • abuseipdb csf dynamic fail2ban firewall integration script modesecurity modesecurity ban ip remote_addr
    • Replies: 12
    • Forum: Plesk Obsidian for Linux
  3. M

    Nginx with JXcore, give wrong $remote_addr (127.0.0.1)

    Hello, My server are on plesk 12, with nginx and jxcore. The website use nodejs with some npm. All my log show 127.0.0.1 for remote_addr There is a way to solved this trouble? Thanks for your help here the exctract from my jxcore log headers=>undefined headers x-real-ip=>undefined headers...
Back
Top