Sorry, there was a problem we could not recover from. The server returned a "500 - Whoops, looks like something went wrong." - Forum | JoomShaper
Solved SP Page Builder

Sorry, there was a problem we could not recover from. The server returned a "500 - Whoops, looks like something went wrong."

Asked by Alba 1 month ago Last activity 3 weeks ago

Hello,
I am not able to edit any pages from the front end. I get the following error:

Sorry, there was a problem we could not recover from.
The server returned a "500 - Whoops, looks like something went wrong."

Here is my system information:

System Information

Joomla! Version Joomla! 5.4.8 Stable [ Kutegemea ] 18-August-2026 16:00 GMT
Joomla Backward Compatibility Plugin Enabled ()
PHP Version 8.4.24

I am running SPPageBuilder Pro 6.8.0

How can I fix this issue?
Thanks

Accepted answer

Marked as the solution
Rashida Rahman Staff

Hi there,

Thanks for reaching out.

Your Joomla, PHP, and SP Page Builder versions appear to meet the current requirements.

Since a 500 error is only a generic server error, we need to see the actual error message to identify the cause.

Could you please enable Joomla Debug and set Error Reporting to Maximum, then try opening the front-end editor again and share the complete error message or stack trace with us?

Also, if possible, please check your server/PHP error log for the corresponding error.

Best regards,

Alba Asked this

Thank you Rashida, I have included the links to the screenshots in the hidden area.
Alba

5 more replies

Alba Asked this

Hello,
I have not received a response and need to update my website ASAP. Do you need any additional information from me?

Alba

Rashida Rahman Staff

Hi Alba,

Thanks for the screenshots — they pinpoint the cause, and it isn't SP Page Builder or Joomla.

Behind the generic 500 page is this database error:

User 'o13*******' has exceeded the 'max_user_connections' resource (current value: 4)

Your MySQL user is limited to 4 simultaneous connections. The front-end editor loads page data, addons and media through several parallel requests, each needing its own connection, so it goes over that limit almost every time — while normal page visits stay under it. The "error in your SQL syntax… near ''" message you saw is a side effect of the same dropped connection.

Two things to do:

  1. Lower what your site needs. In System → Global Configuration → System tab, change Session Handler from Database to Filesystem, and set Cache to Conservative Caching. Also keep just one tab open on the site while editing, and turn Debug back off once testing is done.

  2. Ask your hosting provider to raise the limit. Four concurrent connections is very low for a CMS — most shared hosting plans allow 20 or more. You may ask them:

    My Joomla site returns HTTP 500 errors and MySQL reports "User '…' has exceeded the 'max_user_connections' resource (current value: 4)". Please raise max_user_connections for this database user, or advise which package provides a higher limit.

Step 1 often gets the editor working again straight away; step 2 is the permanent fix. If anything remains after both, let us know and we'll continue from there.

Best regards,

Rashida Rahman Staff

Did you check?

Alba Asked this

Thank you. My hosting provider wouldn't increase my max user connections but lowering what the site needed did help. I just have to make sure I don't have too many windows open.

Thanks again.
Alba

Rashida Rahman Staff

Glad that it helped and You are always welcome Alba:)

Log in to reply.