Integration with Nginx: Banning NOT functional

  • Resolved John

    (@john-pingtech)


    10 years, 2 months ago

    We have used your plugin on apache sites where the apache process can dynamically read changes in the .htaccess file. This works well. But on Nginx, your plugin writes to a nginx.conf file in the virtual servers public_html folder. This requires that you do an include from the sites-available/[virtual-server].conf file. (not a big deal, but undocumented step)

    The problem/issue comes from the fact that Nginx does not parse these files dynamically. Meaning that after a change, you have to specifically reload Nginx to see the changes. For example, when banning a user for a brute force attack, your plugin writes a deny line in the /virtual-server/public_html/nginx.conf file. But this change is not picked up until you reload Nginx. So the attack continues unabated.

    Are there any plans to address this?

    https://www.ads-software.com/plugins/better-wp-security/

Viewing 2 replies - 1 through 2 (of 2 total)

  • Hey John,

    This is expected behavior and unfortunately a limitation NGINX. I can add it as a feature request but I’m not aware of any current plans to adjust it.

    Thanks,

    Gerroald

    I just buy PRO version of plugin and have same problem.. Also my nginx.conf is blank….

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Integration with Nginx: Banning NOT functional’ is closed to new replies.