Jump to content

Catalogue and modules missing in Backoffice after port changes


ROE

Recommended Posts

Hi there,

Our hosting company recently updated the Mysql version on their servers to 8.4 and since we are running an older Prestashop installation, 1.7.2.1 and php 7.0, we were told to change our database server port to 6033 to maintain compatibillity. I have done so and frontend seems to be running fine again, but in backoffice I no longer have access to the catalogue and modules sections (i get Error 500) and I am now unable to add or edit any modules or items through the Backoffice. Any help or suggestions would be very much appriciated.

I have tried to enter debug mode, but the installation becomes unstable and eventually crashes.

//Best regards

Rasmus

 

Link to comment
Share on other sites

Hey @ROE no rest for the weary

Capture the real 500 error (don’t guess)

Do not rely on “debug mode” in BO if it makes the shop unstable. Instead, pull the error from logs.

Find your error log location first (before testing anything)

In your hosting panel (Plesk/cPanel or similar), locate:

  • Domain → Logs (Apache/Nginx)
  • PHP error log / PHP-FPM log
  • If your host provides “Live log” or “Follow log,” open it now.

With the log open, replicate the problem

  • In a new tab, go into Back Office and click the exact menu that triggers the 500:
  • Catalog → Products / Categories
  • Modules → Module Manager
  • Do not change settings yet. Just reproduce the error once.
  • Immediately re-check the log (this is the important part)
  • Look for the first relevant entry at the exact time you clicked:

PHP Fatal error

Uncaught PDOException

SQLSTATE[...]

memory/timeouts like Allowed memory size exhausted or Maximum execution time exceeded

Post the first error line + the next few lines

The first fatal line is usually enough to identify whether this is:

  • SQL mode / MySQL compatibility
  • ProxySQL (port 6033) limitations/rules
  • PHP 7.0 compatibility/fatal error
  • permissions / missing extension / memory

If you paste that error snippet (redacting domain/usernames), people can tell you quickly whether you need the host to adjust sql_mode, ProxySQL rules on 6033, or whether the legacy PS/PHP stack is now failing on specific BO queries.

Link to comment
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
×
×
  • Create New...