Referencing topic Logout supercache nginx wps-hide-plugin bug
-
Hi, I just wanted to alert you on this issue in which WPS Hide Plugin has a role to play.
I just created a ticket at Supercache plugin, but the solving action could be yours, I don’t know.
https://www.ads-software.com/support/topic/logout-supercache-nginx-wps-hide-plugin-bug/Ticket text:
Hi,
what has changed during the last update? I now keep getting “502 Bad Gateway (nginx)” errors everytime I log out, using the logout link, like https://example.com/admin-login/?action=logout&_wpnonce=9a6947bc48.
Never had this issue before. Just spend hours trying to pinpoint the cause, switching settings, plugins, disabling proxy server/cache/cdn etc.
My conclusion is that it only occurs when nginx is running as a proxy to apache, wp supercache’s cache is enabled, and the plugin WPS Hide Login is enabled, which changes the login path. When nginx is disabled as proxy or supercache’s cache is disabled or the plugin WPS Hide Plugin is disabled, then the error does not occur.
Nginx has been running for ages with the current config, with both plugins enabled, so the only thing I can think of causing this is a recent update of WP Supercache, effecting the logout procedure, which is using a different path than ‘wp-login.php’ because of the config of the WPS Hide Plugin.
The last supercache changelog update says something about nonces, could this be a regression? Or should the folks at WPS Hide Plugin do a logic update to keep playing nice with Supercache?
Thanks.
- The topic ‘Referencing topic Logout supercache nginx wps-hide-plugin bug’ is closed to new replies.