Failed to reset the cache for instance #34? Let’s look into the solution in this post. At Bobcares, with our WordPress Support Services, we can handle your WordPress-related issues.

A solution to use when failed to reset the cache for instance #34

One of the most important strategies for enhancing site performance is site caching and for good reason. Caching is enabled on almost all WordPress sites to store resources effectively and speed up the site. We might occasionally want to clear this cache. However, sometimes, the following error may appear while trying to reset the cache. This is because the information about the WordPress instance is present in the WordPress Toolkit database.

The steps to fix the issue are as follows:

1. By using SSH, connect to the Plesk server.
2. Make a copy of the wp-toolkit.sqlite3 database:

   cp /usr/local/psa/var/modules/wp-toolkit/wp-toolkit.sqlite3 /usr/local/psa/var/modules/wp-toolkit/wp-toolkit.sqlite3.bak
3. Access the WordPress Toolkit database.

   sqlite3 /usr/local/psa/var/modules/wp-toolkit/wp-toolkit.sqlite3
4. Using the instance ID from the error response, delete the orphaned records:

   sqlite> .headers on
   
   sqlite> delete from instanceProperties where instanceId = 34;
   
   sqlite> delete from instances where instances.id = 34;
   
   sqlite> .quit

[Looking for a solution to another query? We are just a click away.]

Conclusion

To sum up, our Support team went over the details on a simple method including 4 steps to fix the issue when failed to reset the cache for the instance #34.