Possible Issue Caused by LiteSpeed Cache Plugin Update – Site Marked as Broken
-
Hello,
After an automatic update to the latest version of the LiteSpeed Cache plugin, I encountered an issue with my WordPress site. WP Toolkit is now reporting that the site is broken, and I am unable to access the WordPress dashboard. Below are the specific errors that appeared:
- 2024-09-08 03:14:35
- Error Message: Site data was refreshed and stored in cache. The site is now marked as broken since WP Toolkit could not establish a connection to it due to the following issue:
Error: The site you have requested is not installed. Run 'wp core install' to create database tables. [error]FailedToExecuteWpCliCommand: exit status 1[/error]
.
- Error Message: Site data was refreshed and stored in cache. The site is now marked as broken since WP Toolkit could not establish a connection to it due to the following issue:
- 2024-09-08 03:14:37
- Error Message: Data refresh failed. Site data was not refreshed due to the following error: Failed to reset cache for the instance #77:
Error: The site you have requested is not installed. Run 'wp core install' to create database tables. [error]FailedToExecuteWpCliCommand: exit status 1[/error]
. Cache tags: [“action-log-existence”, “main-information”, “ip”, “ssl-statuses”, “remote-agent-instance”, “cloud-linux-cagefs”, “cpanel-links”, “admin-credentials”, “admin-login-link”, “php”, “plugins”, “themes”, “config”, “nginx-caching”, “maintenance-mode”, “table-prefix”, “force-updates”, “security-measures”, “protected-dir”, “screenshot”, “virtual-patches”, “available-minor-update-version”, “virtual-patches-for-end-customer”].
- Error Message: Data refresh failed. Site data was not refreshed due to the following error: Failed to reset cache for the instance #77:
Additionally, Wordfence has flagged the site as potentially insecure and redirects to
wp-admin/install.php
. It seems like the LiteSpeed Cache plugin update was the last change made before these issues occurred.Could you please check if the automatic update to the latest version of the plugin might have caused this problem? I would appreciate any assistance you can provide to help resolve this issue.
Thank you.
- 2024-09-08 03:14:35
- You must be logged in to reply to this topic.