WP site crashes since 6.7 upgrade, WP Cache seems to be the issue

  • Hi,

    This night my site automatically upgraded to the latest WP 6.7, and soon after my site went offline according to the Jetpack monitor.

    I deactivated WP Total Cache and my site is available again, so it seems to be caused by the plugin. I don’t see any errors in my http logs however, or in the output, so I can’t give you any more details unfortunately on what exactly is going wrong.

    Is there a known issue with the latest WP version?

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @n3wjack

    Thank you for reaching out and I am happy to help!
    I’ve tried to replciate the issue with the auto-update and manual update and I was not able to do so as the website did not break of went offline in my case.
    Are there any logs in the mentioned monitoring service? Have you tried purging the cache and see if this helps!?
    Is there any cahnce you can share the website URL and where the website is hosted and please try to manually delete the entire /cache/ folder and see if this helps also

    Thanks!

    Thread Starter n3wjack

    (@n3wjack)

    Where is the cache folder located for WP Total Cache?
    I see a number of cache related folders in my wp-content, but am not sure which I should delete.

    I deactivated the plugin in the meantime, so you can’t see any errors at the moment.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @n3wjack

    Thank you for your feedbac

    The W3 Total Cache creates the cache folder in the wp-content folder. So the path is in your website root -wp-content/cache/
    Within that folder, depending on the configuration, you can see different folders like disk_enhanced, object, minify, etc

    Thanks!

    Thread Starter n3wjack

    (@n3wjack)

    I deleted the cache folder, but it still crashes when I reactivate the plugin.

    I tried turning off some caching, and when I disable the DB cache it works again. So that seems to be the culprit. Is there a way to get an error log somehow of what might be going wrong?

    My 500 error pages are empty, so those don’t contain any extra info. I also don’t see anything in the logs.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @n3wjack

    Thank you for your feedback
    Can Can you please sahre which caching method you are using for DB Caching?
    If it’s Disk, please keep it disabled and only use Object Caching instead

    Thanks!

    Thread Starter n3wjack

    (@n3wjack)

    My DB cache was set to disk, so I turned it off now. It used to work that way, so it’s weird it suddenly stopped.

    I activated Object Cache instead now, also set to disk.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hey @n3wjack

    Thank you for your feedback.
    This may have something to do with the cached data and autoupdate so it is only a temporary problem.
    I would also like to empasize that as you can se ein the description, it’s recommended to use memory-based caching method like Redis or Memcached for Object Caching and DB Caching so if your provider has the option, please check this in order to avoid issues in the future

    Thanks!

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