Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Chris Reynolds

    (@jazzs3quence)

    The plugin definitely works on Nginx environments, so changing the webserver should not cause it to suddenly stop working. It’s likely an issue with the configuration. You might need to go through the setup/configuration process again (in fact, I would assume you would).

    My assumption is that the identity provider (IdP, your third party service) is configured to expect the request to look like the ones you’ve sent before (from the old server), but because the server has changed, it’s getting confused. In which case, you’d likely need to reset the IdP again for the new server.

    Thread Starter nemseck

    (@nemseck)

    Thanks for your answer. In the meantime I’ve figured it out what was the problem. We’re using WP-Hide PRO in order to change all basic WP paths for security reasons and the issue was caused by a conflict between virtual host rules and WP-Hide rewrite rules.

    In particular the lines related to wp-login.php rewriting rules had to be declared at the very bottom of the virtual host configuration. Probably the priority of rewriting rules generated a mismatch in the response.

    Plugin Contributor Chris Reynolds

    (@jazzs3quence)

    That makes sense to me, glad you figured it out!

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

The topic ‘Switch from Apache to NGINX environment’ is closed to new replies.