409 errors and reload loop on wp-admin

  • Resolved averixus

    (@averixus)


    3 months, 1 week ago

    I just activated W3 Total Cache to try to improve performance on my site. Now when I try to go to /wp-admin, it gets stuck in an endless reload loop.

    View post on imgur.com

    If I clear my browser history, then I can successfully load the page – once. The page seems to load normally but there are 409 errors shown for many of the files in the developer tools.

    View post on imgur.com

    If I reload the page again, it goes back to the endless loop until I clear the history again.

    Any ideas? If I uninstall the plugin things go back to normal, but I’d like to actually be able to use it.

    • This topic was modified 3 months, 1 week ago by averixus. Reason: Added screenshots
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @averixus

    Thank you for reaching out and I am happy to help!
    Can you please sahre if the issue occured when istalling the W3 Total cache as a fresh install, or have you made any configuration changes within the plugin?

    Are you using any other caching solution or have another layer of caching besides the W3 Total Cache?

    Thanks!

    Thread Starter averixus

    (@averixus)

    The errors started after I activated it and followed the setup guide. I didn’t have any other caching plugins, but I’ve realised that my host had automatic server caching. I’ve disabled that and reactivated W3TC and it’s working fine with no errors now.

    Thread Starter averixus

    (@averixus)

    @vmarko I’m reopening this, because the problem has started happening again even with the server host cahing disabled. It’s seemingly come back out of the blue, after several days of not doing anything to the site at all. It seems to be restricted to Firefox browser, and it only happens while logged in as admin. It still happens in a private window with all extensions disabled.

    • This reply was modified 2 months, 3 weeks ago by averixus.
    Thread Starter averixus

    (@averixus)

    Scratch that, it’s not limited to firefox – it started happening in chrome too after a while of using the site. Disabling the plugin resolves the issue so it’s definitely plugin-specific and not a browser problem.

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.