JoomlaFreaks
Joomla!® WordPress®
Home Services Portfolio About Contact
Joomla services WordPress to Joomla Joomla to WordPress K2 to Joomla articles VirtueMart developer Joomla maintenance plans Free Joomla site audit
Joomla guides & resources Joomla 3 migration Hacked Joomla cleanup Joomla upgrade cost Joomla 3 end of life Migration checklist 500 error / white screen Security hardening checklist Migration timeline
WordPress services Hacked WordPress cleanup WordPress speed optimization WooCommerce developer WordPress maintenance plans Elementor website design WordPress migration WordPress to Joomla Free WordPress site audit
WordPress guides & resources 500 error / white screen Security hardening checklist Migration timeline
Free Audit
Joomla troubleshooting

Joomla 500 Error or White Screen? Work Through It in the Right Order.

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.

First response

Work through it in the right order

Do not start by disabling random plugins on production.

1

Pause and back up

Take a full backup of the current state before changing anything. If the site is down, preserve the logs too.

2

Find the error

Check the hosting PHP error log and Joomla logs. A single fatal message is worth more than ten guesses.

3

Compare the last change

Was it an update, a template edit, a PHP change or a host migration? Test the likely cause on staging.

4

Contain the issue

If the live site must be restored, do that first and investigate from a copy.

5

Fix and verify

Apply the verified fix, test the affected pages and record what changed.

Common causes

The usual causes we see

The error message narrows the list; these are the frequent candidates.

PHP version mismatch

An old extension or template calls code removed by the host’s PHP upgrade.

Broken extension

A plugin, module or component fails after a partial update.

File permissions

Wrong ownership or permissions can make the site unreadable or unwritable.

.htaccess error

A bad redirect or handler rule can return a server error before Joomla loads.

Database issue

A failed update or corrupt table can stop the bootstrap from completing.

Resource limit

Memory or process limits can look like a random 500 until the log says otherwise.

What to send

What helps us diagnose it

A useful report is not “the site is broken”.

URL

The exact page

The page or area that fails.

Error

The message and log excerpt

The visible error and any PHP fatal line from the hosting log.

Timing

When it started

The last update, edit, host change or traffic event.

Access

A secure route

Hosting and Joomla access via an agreed method—never in a public message.

Backup

What you can restore

The latest backup and whether it has been restore-tested.

Scope

What is affected

Whether email, forms, checkout or only the front end is affected.

client proof
“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.”
Drew — Joomla client
BCCES website
Joomla projectBCCES
Questions

Joomla 500 error FAQ

What to do next and what not to do.

What causes a Joomla 500 error?

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.

What is a white screen of death?

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.

Should I restore a backup first?

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.

Can you fix it without admin access?

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.

Fix the cause, not the symptom.

Send the error message, last change and access route. We will confirm the diagnostic scope and quote before changing the live site.