← All errors

Joomla 'Sorry, there was a problem we could not recover from' (500): Fix

Symptoms: Big, unstyled red error screen that no longer matches your site theme · Message: 'Sorry, there was a problem we could not recover from.' · 'The server returned a 500 - Whoops, looks like something went wrong.'

Mostly verified. Researched 2026-06-01 (Joomla Community Magazine, official forum threads, GitHub issue #41569).

✅ Verified on a live Joomla 5.4.6 install: configuration.php ships with public $debug = false; — flipping it to true is exactly the right lever. We reproduced this exact red page by breaking the database password; with debug on it revealed the real cause (Access denied for user …) — proof that this screen is just a wrapper around the underlying fatal error.

This styled red error screen appears in Joomla 4 and 5 (it was introduced when Joomla 4 added the styled error renderer). The message itself is generic — it just means a fatal error was caught. It could be a database, extension, .htaccess or PHP configuration problem. The screen hides the real cause, so your job is to reveal it.

Step 1 — Turn on debug to see the real error

Edit configuration.php and change:

public $debug = true;

For the fullest detail, pair it with maximum error reporting:

public $error_reporting = 'maximum';

Reload the page. Instead of the red screen you’ll now get a specific error message, file and line number — that’s what actually tells you what’s wrong. (Turn debug back off once you’ve finished.)

Step 2 — Fix the underlying cause

The revealed message will usually point to one of:

Don’t trust unsourced “13 causes” lists floating around — the message is generic by design. The reliable path is always: enable debug → read the real error → fix that.

joomla sorry there was a problem we could not recover from · joomla 500 whoops looks like something went wrong · joomla red error screen 500

Sources