Oops! Errors

Problem

You see an Oops! error while using WHMCS. For example:

Oops! Something went wrong and we couldn't process your request

Cause

WHMCS returns Oops! errors for many reasons. Perform the troubleshooting steps below to identify the cause for your error.

Addon Modules

If you see an Oops! error while viewing the list of addon modules, you may be using an incompatible addon module.

For more information, see Addon Module Oops! Errors.

Authentication

If you see an Oops! error while trying to log in to WHMCS, your administrator role may be missing required permissions or, if an admin is logging in as a client, there may be an issue with the client’s password.

For more information, see Oops! Access Denied Errors.

Domains

If you see an Oops! error while managing a domain in the Admin Area, your MySQL® database may contain an invalid character in a domain-related field.

For more information, see Domain Management Oops! Errors.

Failed Opening

If you see an Oops! error with the following message, a required WHMCS file is missing:

main(): Failed opening required '/path/to/whmcs/filename.php'...

For more information, see Failed Opening Errors.

PHP Upgrades

If you see the following Oops! error after you upgrade PHP, your PHP version is missing some of WHMCS’s required extensions or there are PHP files on your system that use deprecated or unavailable functions:

Oops! Something went wrong and we couldn't process your request

Troubleshooting

To find the cause of an Oops! error:

  1. Enable error reporting.
    For more information, see Enable Error Reporting.
  2. Trigger the error again.
  3. Examine the output to find more information.
troubleshooting troubleshooting-article php-upgrades oops-errors

Last modified: 2025 March 28