NGINX Clarification

  • Hi All

    I’ve found a few threads on using iThemes Security with NGINX, but I was wondering if I could get some clarification. Currently, I am getting this error in the logs.

    Empty file encountered when attempting to update apache config file.

    However, from what I understand, alternative methods are used to implement the ban list and other rules in the case of NGINX. Is this understanding correct? If so, how can I stop that error from showing up in the logs? If not, is there an NGINX version of the server config rules that I can send to the host?

    Kind regards,

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

  • Hi hcst,

    I’m a bit puzzled by your topic.

    The error indicates the site is using Apache web server.

    But you are looking for NGINX clarification.

    Or are you considering switching from Apache to NGINX because of the error ?

    +++++ To prevent any confusion, I’m not iThemes +++++

    Thread Starter hcst

    (@hcst)

    Hi nlpro

    Thanks for your response.

    The web server is NGINX, but your question made me realise this might be causing confusion somehow:

    “The .htaccess file works differently on the WP Engine platform because we use a dual web-server combination of Apache and Nginx. This means settings and directives in the .htaccess file will only apply for uncached requests.

    The .htaccess is processed by Apache, which does not serve traffic on WP Engine. This is incredibly important when it comes to items such as redirects and headers, as Nginx is actually serving traffic instead.”

    https://wpengine.com/support/htaccess/#:~:text=.-,htaccess%20and%20WP%20Engine,combination%20of%20Apache%20and%20Nginx.

    Could WP Engine’s dual use of Apache and NGINX be the cause?

    Kind regards,

    Ok, I see. Could be related.

    Another possibility is too much banned IPs.
    Navigate to the Banned Users card (Security > Dashboard). If there are lots and lots of IPs listed, get rid of most of them. That might clear the issue (according to another similar topic on this forum).

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘NGINX Clarification’ is closed to new replies.