Pause and back up
Take a full backup of the current state before changing anything. If the site is down, preserve the logs too.
A 500 error is a symptom, not a diagnosis. The fastest route is usually the error log, the last change and a staging copy—not disabling extensions on the live site and hoping. This guide shows the order we use.
The audit is an external check. It cannot read your PHP error log; a diagnosis needs hosting or administrator access.
Do not start by disabling random plugins on production.
Take a full backup of the current state before changing anything. If the site is down, preserve the logs too.
Check the hosting PHP error log and Joomla logs. A single fatal message is worth more than ten guesses.
Was it an update, a template edit, a PHP change or a host migration? Test the likely cause on staging.
If the live site must be restored, do that first and investigate from a copy.
Apply the verified fix, test the affected pages and record what changed.
The error message narrows the list; these are the frequent candidates.
An old extension or template calls code removed by the host’s PHP upgrade.
A plugin, module or component fails after a partial update.
Wrong ownership or permissions can make the site unreadable or unwritable.
A bad redirect or handler rule can return a server error before Joomla loads.
A failed update or corrupt table can stop the bootstrap from completing.
Memory or process limits can look like a random 500 until the log says otherwise.
A useful report is not “the site is broken”.
The page or area that fails.
The visible error and any PHP fatal line from the hosting log.
The last update, edit, host change or traffic event.
Hosting and Joomla access via an agreed method—never in a public message.
The latest backup and whether it has been restore-tested.
Whether email, forms, checkout or only the front end is affected.
“They are very knowledgeable about Joomla!® and were very helpful throughout the project, even though we were not 100% sure about what we wanted to do.”
What to do next and what not to do.
Common causes include a PHP version mismatch, a broken extension, file permissions, a corrupted .htaccess rule, database errors or a failed update. The error log is the fastest way to narrow it down.
A fatal PHP error where display_errors is off. The page returns nothing visible. Error logs and a staging copy are safer than editing production files to find it.
If the site was working before a recent change and you have a tested backup, restore to a staging copy first so you can compare and identify the cause without taking the live site down again.
No. Diagnosing a Joomla fatal requires hosting or administrator access to logs and files. The public audit can show external symptoms, not the PHP error itself.
Pick the next question that matches your situation.
Send the error message, last change and access route. We will confirm the diagnostic scope and quote before changing the live site.