Nginx no longer working

  • Resolved DavidH64

    (@davidh64)


    7 years, 7 months ago

    (This is a continuation of https://www.ads-software.com/support/topic/quit-working-after-upgrade/)

    Since a few version ago, Nginx has been blocked:
    The Plugin automatically disables itself when it detects a Nginx standalone server configuration.

    I have the following questions:

    • What are the specific features and functionality which cannot be added or implemented with a standalone Nginx server configuration?
    • FAQs state, that “Your server must be configured to allow the use of an .htaccess file.”, however the .htaccess file does not contribute to the functionality of the plugin and only adds minor tweaks (see here for an overview), all of which can be optionally ported to the nginx configuration. Why is this a requirement?
    • Why is specifically Nginx being blocked? Lighttp, IIS and other servers do not seem to be on the “blacklist”.

    Also, here is my reply to your last reply:
    You are missing the point of this discussion. Please focus on the questions I asked and please try to answer them. You have yet to name one example as to why specifically Apache is needed and why Nginx wouldn’t work.

    P.S. Apple/MS does not work as an analogy: Different Kernel, different environments, different window manager, etc. It’s like trying to put a metric screw in a imperial hole. Apache and Nginx however both share the same system with only minor differences. So my question remains: Which difference irreversibly breaks compatibility of SpamShield with Nginx?

Viewing 16 replies (of 16 total)
  • Plugin Contributor redsand

    (@redsand)

    I’m sorry if I have offended you and by no means did I mean to troll you or anyone else involved.

    Well, intention or not, the way you have been coming at us on the forums and the way you have treated our tech support team, it is definitely has been unfriendly behavior.

    However, you failed to persuade me or provide examples/proof of how standalone Nginx is not enough to run WordPress and WP-Spamshield flawlessly.

    Part of the problem is that you don’t have the experience level with Nginx and Apache to be arguing as aggressively as you are. I’m sorry that you don’t understand the technical aspects from the info we’ve provided, but that kind of expertise is up to you to develop. That’s not on us. We have provided you specific examples and explanations, and if it still does not make sense, then I’m sorry, but there is nothing more we can do for you. That may only come with more experience.

    Again: .htaccess support is not required by this plugin, only enforced for some weird reason.

    Please stop pushing this false opinion — that is the definition of trolling. You’re just repeating the same thing, over and over, and even after 50 times, it still is not true.

    Also, I am running standalone Nginx, have not ported any .htaccess instructions of this plugin to my nginx config and it is all running without any issues for well over a year now, blocking all that awful spam flawlessly.

    As our tech support previously explained: it may seem like things are working flawlessly on the surface with your particular setup, but under the surface, there are features of the plugin that are not working as they should. If we ran diagnostics on your site, we could show you that. When we say that standalone Nginx is not compatible, we do that for a reason.

    If you don’t understand all the nuances of it, then that’s ok. However, to repeatedly come online and aggressively contradict us, that’s not exactly friendly behavior. For the last five months, the only thing you’ve posted on the forums here is about this topic…do you understand how that is trolling?

    It’s time to put it to rest.

    P.S. In the end, despite all this nginx-stuff, thank you for the plugin!

    You’re welcome. Take care and best of luck.

    – Scott

Viewing 16 replies (of 16 total)
  • The topic ‘Nginx no longer working’ is closed to new replies.