Jump to content
lesmonds

Oops! Something went wrong (Again)

Recommended Posts

With a new install of whmcs 7.5 the warnings report "Your PHP version 7.0.30 is supported by WHMCS." When I change the version to ea-php71/72 in cpanel "MultiPHP Manager" I get the "Oops! Something went wrong" page on load the site.

I have tried to display the error with "Tick to enable Display Errors and hit Save." under General Settings, no errors are displayed, each time I have to revert back to ea-php70.

Thanks

Les

Share this post


Link to post
Share on other sites

One or more of your modules/gateways/addons is not compatible with PHP 7.1/7.2

Share this post


Link to post
Share on other sites

I have disabled all mods/addons one by one, still the same, the only 2 gateways I have are the ones that are already in whmcs, paypal and stripe, I would assume they are php 7.1/7.2 compatible.

Share this post


Link to post
Share on other sites

Normally under the "Oops! Something went wrong" there is an error debug output would you be able to share that as it should help narrow down where to look.

 

Share this post


Link to post
Share on other sites
Posted (edited)
On 7/9/2018 at 12:44 PM, lesmonds said:

With a new install of whmcs 7.5 the warnings report "Your PHP version 7.0.30 is supported by WHMCS." When I change the version to ea-php71/72 in cpanel "MultiPHP Manager" I get the "Oops! Something went wrong" page on load the site.

I have tried to display the error with "Tick to enable Display Errors and hit Save." under General Settings, no errors are displayed, each time I have to revert back to ea-php70.

Thanks

Les

The Tick to enable Display Errors doesn't always return the error on screen. Try placing this code at the end of your configuration.php file. It should give you something on screen.

$display_errors = true;
$display_errors = E_ALL;

Anyway I bet 2$ that it depends on ionCube encoding caused by a Paymet Gateway or Registrar.

Edited by Kian

Share this post


Link to post
Share on other sites
2 hours ago, Kian said:

The Tick to enable Display Errors doesn't always return the error on screen. Try placing this code at the end of your configuration.php file. It should give you something on screen.


$display_errors = true;
$display_errors = E_ALL;

Anyway I bet 2$ that it depends on ionCube encoding caused by a Paymet Gateway or Registrar.

Added the code to the end of the configuration.php file still no errors showing! 

payment gateways we have are paypal and stripe, register mod is RC & LB Tools v2 free, its supposed to be php 7.1/7.2 compatible. 

PHP Version Compatibility check shows all files are compatible.

if it helps, we have a dedicated server, with Virtualizor, and the latest cpanel running centos 7 on a VPS, 

Share this post


Link to post
Share on other sites

Just a random thought but after changing your PHP version is IonCube also still available and at a compatible version?

Share this post


Link to post
Share on other sites

Hello,

I am sorry to hear that you are having issues with Oops errors on your installation when switching to PHP 7.1/7.2. It is indeed odd that the full error isn't displaying when you enable display errors. I'd recommend opening a support ticket so we can investigate and help you resolve this. Thanks!

Share this post


Link to post
Share on other sites
Posted (edited)
On 7/10/2018 at 8:07 PM, lesmonds said:

Added the code to the end of the configuration.php file still no errors showing! 

payment gateways we have are paypal and stripe, register mod is RC & LB Tools v2 free, its supposed to be php 7.1/7.2 compatible. 

PHP Version Compatibility check shows all files are compatible.

if it helps, we have a dedicated server, with Virtualizor, and the latest cpanel running centos 7 on a VPS, 

Utilities > System > PHP Info > ionCube version? Is it 10.x?

Edited by Kian

Share this post


Link to post
Share on other sites

just to elaborate, it needs to be IonCube Loader 10.1 or newer. 10.0 and older won't work, but will usually give a false error about a file being corrupted instead.

Share this post


Link to post
Share on other sites
1 hour ago, Kian said:

Utilities > System > PHP Info > ionCube version? Is it 10.x?

v10.2.0

Share this post


Link to post
Share on other sites

Since errors are not displaying still, I would recommend ensuring the display_errors option is set to On in your php.ini file. If that still doesn't reveal the error, I would recommend opening up a Support Ticket so we can further assist you by looking directly at your installation.

Share this post


Link to post
Share on other sites
24 minutes ago, WHMCS Marcus said:

Since errors are not displaying still, I would recommend ensuring the display_errors option is set to On in your php.ini file. If that still doesn't reveal the error, I would recommend opening up a Support Ticket so we can further assist you by looking directly at your installation.

Tried that too :( Ticket sent

Share this post


Link to post
Share on other sites

Look at the "error_log" file in your WHMCS install folder, it should show at the end of the file why your page is not loading with date and time included. 

Share this post


Link to post
Share on other sites
4 hours ago, ITWolfy said:

Look at the "error_log" file in your WHMCS install folder, it should show at the end of the file why your page is not loading with date and time included. 

I could not find an "error_log" file in the WHMCS install folder!

Share this post


Link to post
Share on other sites

If you using a Linux base OS the 'error_log' file will be in the '/var/log/httpd/' or '/var/log/apache/' folder.

Also if you are using Apache with SSL you will need to check the ssl_error_log files.

Sorry but I don't know where the would be if you are using IIS.

 

Share this post


Link to post
Share on other sites

Also if you have 'root' access to the server can you send the output of 'php -m' and 'php -v' these will show what modules and IonCube version are running at the time. If you could do this for the working version and the broken version we can check that both have all the required modules/extensions.

Share this post


Link to post
Share on other sites

With the help from support team, it has been fixed, it looks like a number of extensions were missing from the php 7.1/7.2 branch, I have installed them now.

All looking good so far :)

Thanks to all for your input, much appreciated  👍

  • Like 2

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×

Important Information

By using this site, you agree to our Terms of Use & Guidelines