Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
litespeed_wiki:cpanel:whm-plugin-cache-manager-error-status [2018/06/04 14:25] Michael Alegre [WHM Plugin - Cache Manager Error Status] |
litespeed_wiki:cpanel:whm-plugin-cache-manager-error-status [2021/10/06 15:19] (current) Lisa Clarke Redirect to new Documentation Site |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== WHM Plugin - Cache Manager Error Status ====== | + | ~~REDIRECT>https://docs.litespeedtech.com/cp/cpanel/wp-cache-management/#whm-plugin-cache-manager-error-status~~ |
- | + | ||
- | While using the Web Cache Management feature of our WHM plugin, you might occasionally see an installation listed with an "Error" status. | + | |
- | + | ||
- | {{ :litespeed_wiki:cpanel:whm-err-status-example.png?direct |}} | + | |
- | + | ||
- | By hovering over the "Error" text, a small explanation as to the cause of the error will be displayed. Here we will list out and explain these possible errors and what can be done to fix them. | + | |
- | + | ||
- | + | ||
- | ===== Fatal Error Encountered During Action Execution ===== | + | |
- | + | ||
- | This message indicates that PHP encountered a fatal error while loading the WordPress environment and trying to perform some action. | + | |
- | + | ||
- | **Cause:** This most commonly indicates that the installation is invalid in some way, such as a broken backup/testing installation that was detected during scan. | + | |
- | + | ||
- | **Resolution:** Most of the time these installations can be ignored without issue. In the rare case where an installation is working as expected but is still detected with this error, please [[#still_need_help|contact our support team]] for further investigation. | + | |
- | + | ||
- | ===== Timeout Occurred During Action Execution ===== | + | |
- | + | ||
- | This message indicates that PHP timed out while loading the WordPress environment and trying to perform some action. | + | |
- | + | ||
- | ** Cause:** This error is most commonly caused by custom code added in a user's wp-config.php file. If the code runs into some issue when executed by our script call, it may hang. | + | |
- | + | ||
- | **Resolution:** If the installation is working as expected, you may try to manually locate the code which is causing the error and fix/remove it. If you are in need of assistance you may [[#still_need_help|contact our support team]] for further investigation. Just be aware that this issue likely falls outside of free support. | + | |
- | + | ||
- | ===== Could Not Retrieve WordPress siteURL ===== | + | |
- | + | ||
- | This message indicates that the installation was successfully discovered as a valid WP installation, but siteUrl could not be retrieved from WordPress. | + | |
- | + | ||
- | **Cause:** WordPress' ''get_option()'' function failed to retrieve a siteUrl. | + | |
- | + | ||
- | **Resolution:** Since this error usually indicates some kind of database issue with WordPress, please [[#still_need_help|contact our support team]] for further investigation, if you know this to be a working WordPress site. | + | |
- | + | ||
- | ===== Could Not Match WordPress siteURL To A Known cPanel Docroot ===== | + | |
- | + | ||
- | This message indicates that the siteUrl retrieved from WordPress did not match any known cPanel document roots. | + | |
- | + | ||
- | ==== Case 1 ==== | + | |
- | + | ||
- | **Cause:**: Missing cPanel userdata for the installation. Without this userdata, the correct document root cannot be retrieved from cPanel. | + | |
- | + | ||
- | **Resolution:** Case 1: This can be resolved by validating this user account and domain in cPanel. If set up correctly, you should find an entry for the site in the ''%%/var/cpanel/userdata/$user/%%'' directory. | + | |
- | + | ||
- | ==== Case 2 ==== | + | |
- | + | ||
- | **Cause:**: The siteUrl set in the WordPress backend is incorrect. This can happen when the WordPress site is set up using ''mod_userdir'' (resulting in an IP being set for siteUrl) or the siteUrl has been changed to an incorrect value in the WordPress backend. | + | |
- | + | ||
- | **Resolution**: This can be resolved by simply changing the value of siteUrl in the WordPress backend to use the site's fully qualified domain name. After which, a document root match should be found. | + | |
- | + | ||
- | ===== Could Not Find A Valid wp-config.php File ===== | + | |
- | + | ||
- | This message indicates that we could not find a possible ''wp-config.php'' file for that specific installation. | + | |
- | + | ||
- | **Cause:** When looking for an installation's ''wp-config.php'' file, the installation's root directory and parent directory are both checked for a valid copy. If one cannot be found, or the discovered ''wp-config.php'' file is believed to belong to a different WordPress installation (i.e. it is discovered in a parent directory also containing a ''wp-settings.php'' file), then this error is set. | + | |
- | + | ||
- | **Resolution:** Confirm that this installation has a valid ''wp-config.php'' file. If the ''wp-config.php'' file is kept more than 1 directory above the root installation using symbolic links, it will need to be moved to the installation root or parent directory. | + | |
- | + | ||
- | ===== Still Need Help? ===== | + | |
- | + | ||
- | If you are still running into issues after learning about the cases above, please [[https://www.litespeedtech.com/support|contact our support team]] for further assistance. | + |