Support » Plugin: W3 Total Cache » HTTP ERROR 500 when manually purging cache

  • Updating from version 0.9.5.4 to 0.9.6 throws a HTTP ERROR 500 – every time page cache is manually purged, or ‘purge all caches’ is selected from the menu.

    Anyone else experiencing this?

Viewing 4 replies - 1 through 4 (of 4 total)
  • I did too but then I removed the plugin and re-did everything. I followed a tutorial
    https://bloggingwizard.com/w3-total-cache-cloudflare/
    to set it up and now it works fine.

    Thanks @davesohan for the tip.

    I did try uninstalling / deleting / re-installing but the HTTP ERROR 500 still occurs on manual cache purges.

    Incidentally I have a test server running an older version of WP – 4.8.4 and that works fine with W3 Total cache 0.9.6 – but when I upgraded to WP 4.9.1 the HTTP ERROR 500 started occurring there as well.

    I will await future W3TC releases and hope for a fix.

    • This reply was modified 1 year, 9 months ago by  Plan9.

    I found that this is a known bug in the 0.9.6 update. It’s related to cloudlfare (any previous and current use with W3TC) and the fix / workaround is provided here: https://wordpress.org/support/topic/fatal-error-2749/

    Hopefully W3TC developers will fix this in future releases.

    • This reply was modified 1 year, 9 months ago by  Plan9.

    I had the same problem too. My diagnosis is that the purge of the cache is caused by the huge CPU time it costs to delete all the individual folders that contain the cached pages (25000 in my case).
    I have solved this by creating a background task that removes each folder and immediately after that request that page again, so that the cache is immediately rebuilt. I pick one page per second. The purge & refresh of my total of 25000 pages takes then apx 8 hours. In foreground this would break the connection with the server after one minute, producing the “Internal server error 500” messsage.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘HTTP ERROR 500 when manually purging cache’ is closed to new replies.