• Resolved tezalsec

    (@tezalsec)


    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.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support MaximeWPS

    (@seinomedia)

    Hello,

    Thanks for using WPS Hide Login.

    I guessed to many WP installs with WPS Hide Login on NGINX servers and didn’t noticed anything like thant.

    Neverthless, I can’t check on many install with WPS Hide Login AND WP Supercache.

    You mentionned a proxy. Did you try to deactivate it and check if the issue still occurs ?

    Di you try to deactivate every plugins except WP Supercache and WPS Hide Login ?

    Thread Starter tezalsec

    (@tezalsec)

    Thanks for your suggestion.

    Yes, I had deactivated the proxy, and like I said in my post, it does not occur then. but that does not mean the cause is there.

    I continued testing with deactivating all plugins and activating one at the time, and actually found out that the issue also depends on woocommerce being activated.

    I have had nginx, woocommerce, supercache and your plugin enabled for a long time, but for some reason now this issue occurs. I am assuming your plugin isn’t the direct cause, but more of a indirect consequence, I guess.

    It occurs when these are combined: nginx as proxy, supercache enabled, woocommerce enabled, and WPS Hide Plugin enabled.

    It’s hard to debug, with many factors in play and no clear error logging.

    Thanks again.

    • This reply was modified 2 years, 9 months ago by tezalsec.
    Thread Starter tezalsec

    (@tezalsec)

    I’ll close this ticket here for now, thanks.

    • This reply was modified 2 years, 9 months ago by tezalsec.
Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Referencing topic Logout supercache nginx wps-hide-plugin bug’ is closed to new replies.