Difference between revisions of "Troubleshooting Guide"

Latest revision as of 20:06, 9 May 2022

You may encounter some common errors while using WHMCS. Before contacting support, run through the steps below to attempt to resolve the issue yourself.

Known Bugs

When we identify issues between releases, we publish individual patches (hotfixes) outside of the update structure.

For more information, see How we handle Bug Reports.

Module Command/Registrar Error

Module Command Errors are error messages that third party systems return via modules.

For more information, see:

Unknown Errors

Sometimes a third party system or module will provide a response that WHMCS is unable to recognise and interpret. This can result in the display of an Unknown Error message.

For more information, see Troubleshooting Module Problems.

Oops!, Blank, or Partially Loading Page

When you see an "Oops!", blank, or partially loaded page, an error condition has occurred.

For more information, see:

Payments Not Recorded

The callback setting configuration must communicate with your WHMCS installation. If it does not, the system may not successfully record payments in WHMCS.

For more information, see Troubleshooting Payment Record Issues.

500 Internal Server Error

The 500 internal server error is usually due to a customisation or an issue with the PHP configuration causing issues.

For more information, see PHP and WHMCS.

@@ Line 21: / Line 21: @@
 ===Unknown Errors===
-Sometimes a third party system or module will provide a response that WHMCS is unable to recognise and interpret. This can result in the display of an "Unknown Error" message.
+Sometimes a third party system or module will provide a response that WHMCS is unable to recognise and interpret. This can result in the display of an '''Unknown Error''' message.
 For more information, see [[Troubleshooting Module Problems]].

Documentation