Before reading on
First check whether the system requirements are met, whether there are service version differences between the old and new servers, whether the PHP version is compatible, and whether the PHP extensions are complete.
The error when moving WHMCS to another server:
Oops!
Something went wrong and we couldn't process your request.
Please go back to the previous page and try again.
When I moved my WHMCS site, the error above appeared. Several moves failed because of it, I left it alone for a while, and finally I found the solution.
There are many possible causes of this error.
A WHMCS technical engineer said:
Seeing an Oops error page like this means an error occurred while the page was being generated.
The error can be anything from a simple notice or warning to a fatal error that stops execution.
The server's PHP error-reporting level determines which types of errors trigger it.
In this case the error appears to be only a low-level warning, not something to worry about.
But it does indicate that your server's PHP error_reporting level is set too high for a production environment — we recommend lowering it to 0 in the server's PHP configuration, or at least excluding warnings and notices.
My problem: the old server ran the DirectAdmin panel, but I moved the site to Apache on aaPanel. A DA addon under ../modules/addons/DirectAdmin.... broke my WHMCS (the DA addon is encrypted with an ionCube Loader [PHP 5.6]-compatible encoding, while my aaPanel runs PHP 7.x+). Deleting or renaming that directory fixed it. If you try this and it still doesn't work, go back and check the basics: system requirements, service version differences between old and new servers, PHP version compatibility, missing PHP extensions, and so on.
If it is still not solved, you can run this in the database:
UPDATE tblconfiguration SET value='on' WHERE setting= 'DisplayErrors'
Remember to turn it off after fixing — run the following (you can leave it on, but I recommend turning it off):
UPDATE tblconfiguration SET value='off' WHERE setting= 'DisplayErrors'
Then, when you visit your site, you can see the actual error cause — by default the cause is hidden.
The above should be enough to solve the problems behind "Something went wrong and we couldn't process your request."
Sigh, more hair lost. A hard-won late-night lesson — take it if it helps, and comments are welcome.
Original article — please credit the source when reposting, thanks.
References
https://whmcs.community/topic/271837-oops-something-went-wrong-and-we-couldnt-process-your-request/
https://docs.whmcs.com/System_Requirements
https://docs.whmcs.com/Licensing
https://docs.whmcs.com/Further_Security_Steps#Secure_the_Writeable_Directories
https://docs.whmcs.com/Storage_Settings
Quantum Responses (0)