Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
litespeed_wiki:cpanel:whm-plugin-cache-manager-error-status [2018/03/29 15:18] Michael Alegre [Could Not Match WordPress siteURL To A Known cPanel Docroot] |
litespeed_wiki:cpanel:whm-plugin-cache-manager-error-status [2019/02/04 21:41] Lisa Clarke [Unexpected Error Encountered! See webcachemgr.log for more information] Proofreading |
||
---|---|---|---|
Line 3: | Line 3: | ||
While using the Web Cache Management feature of our WHM plugin, you might occasionally see an installation listed with an "Error" status. | While using the Web Cache Management feature of our WHM plugin, you might occasionally see an installation listed with an "Error" status. | ||
- | [IMG] | + | {{ :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. | 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. | ||
Line 14: | Line 14: | ||
**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. | **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 without issue but detected with this error, please [[#|contact our support team]] for further investigation. | + | **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 ===== | ===== Could Not Retrieve WordPress siteURL ===== | ||
Line 21: | Line 28: | ||
This message indicates that the installation was successfully discovered as a valid WP installation, but siteUrl could not be retrieved from WordPress. | 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. | + | **Cause:** WordPress' ''get_option()'' function failed to retrieve a siteUrl. |
- | **Resolution:** Since this error usually indicates some kind of database issue with WordPress, please [[#|contact our support team]] for further investigation if you know this to be a working WordPress site. | + | **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 ===== | ===== Could Not Match WordPress siteURL To A Known cPanel Docroot ===== | ||
Line 29: | Line 36: | ||
This message indicates that the siteUrl retrieved from WordPress did not match any known cPanel document roots. | This message indicates that the siteUrl retrieved from WordPress did not match any known cPanel document roots. | ||
- | **Cause:** This error can be encountered in one of two ways. | + | ==== Case 1 ==== |
- | The first being missing cPanel userdata for the installation. Without this userdata, the correct document root cannot be retrieved from cPanel. | + | **Cause:**: Missing cPanel userdata for the installation. Without this userdata, the correct document root cannot be retrieved from cPanel. |
- | The second case is one in which 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:** 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. |
- | **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 ==== |
- | Case 2: 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. | + | **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 ===== | ===== 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. | + | 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. | ||
+ | |||
+ | ===== Unexpected Error Encountered! See webcachemgr.log for more information ===== | ||
+ | |||
+ | After migrating all cPanel WordPress accounts to another server,and then scanning to manage with LiteSpeed, the following error was noticed on almost all accounts: | ||
+ | |||
+ | /home/user1/public_html - Install skipped due to Error status. Please Refresh Status before trying again. | ||
+ | |||
+ | After refreshing the status, the error changed to the following, still on nearly all accounts: | ||
+ | |||
+ | /home/user1/public_html - Unexpected Error Encountered! See webcachemgr.log for more information. | ||
+ | /home/user2/public_html - Unexpected Error Encountered! See webcachemgr.log for more information. | ||
+ | /home/user3/public_html - Unexpected Error Encountered! See webcachemgr.log for more information. | ||
+ | ... | ||
+ | |||
+ | ''/usr/local/lsws/logs/webcachemgr.log'' showed the following: | ||
+ | |||
+ | 2019-02-04 17:30:07 [ERROR] /home/user1/public_html - Your PHP installation appears to be missing the MySQL extension which is required by WordPress. | ||
+ | 2019-02-04 17:30:07 [ERROR] /home/user2/public_html - Your PHP installation appears to be missing the MySQL extension which is required by WordPress. | ||
+ | 2019-02-04 17:30:07 [ERROR] /home/user3/public_html - Your PHP installation appears to be missing the MySQL extension which is required by WordPress. | ||
+ | |||
+ | It looked like the PHP configuration was wrong and was missing the MySQL module. | ||
+ | |||
+ | The cPanel MultiPHP Manager showed PHP 7.2 (alt-php72) was set to the system default PHP version, and all accounts inherited it. It appeared something was wrong with alt-PHP72 in this case. Changing the default to ea-php72 solved the problem, and all LiteSpeed Cache enabling errors disappeared. | ||
- | **Cause:** When looking for an installation's wp-config.php file, the installations root directory and parent directory are both checked for a valid wp-config.php file. If one cannot be found, or the discovered wp-config.php file is believed to belong to a different WordPress installation (discovered in parent directory also containing a wp-settings.php file), this error is set. | + | ===== Still Need Help? ===== |
- | **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. | + | 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. |