JoomlaFreaks
Joomla!® WordPress®
HomeServicesPortfolioAboutContact
Joomla servicesWordPress to JoomlaJoomla to WordPressK2 to Joomla articlesVirtueMart developerJoomla maintenance plansFree Joomla site audit
Joomla guides & resourcesJoomla 3 migrationHacked Joomla cleanupJoomla upgrade costJoomla 3 end of lifeMigration checklist500 error / white screenSecurity hardening checklistMigration timeline
WordPress servicesHacked WordPress cleanupWordPress speed optimizationWooCommerce developerWordPress maintenance plansElementor website designWordPress migrationWordPress to JoomlaFree WordPress site audit
WordPress guides & resources500 error / white screenSecurity hardening checklistMigration timeline
Free Audit
WordPress troubleshooting

WordPress 500 Error or White Screen? Diagnose It Without Guessing.

A 500 error is a symptom, not a diagnosis. The fastest route is the error log, the last change and a staging copy—not disabling plugins 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 before changing anything. Preserve the logs too.

2

Find the error

Check the hosting PHP error log and WordPress debug log. A fatal line is worth more than ten guesses.

3

Compare the last change

Update, theme edit, PHP change or host migration? Reproduce it on staging.

4

Contain the issue

If the live site must be restored, restore 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 theme or plugin calls code removed by the host’s PHP upgrade.

!
Broken plugin or theme

A fatal after a partial update or a conflict between two extensions.

!
File permissions

Wrong ownership or permissions can stop WordPress loading.

!
.htaccess error

A bad redirect or handler rule can fail before WordPress boots.

!
Database issue

A failed update or corrupt table can stop the bootstrap.

!
Resource limit

Memory or process limits can look random 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.

Timing

When it started

The last update, edit, host or PHP change.

Access

A secure route

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

Backup

What you can restore

The latest backup and whether it has been tested.

Scope

What is affected

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

client proof
“They actually explained what they were doing instead of just billing us for it. Our booking site has paid for itself twice over.”
Courtney Evans — Acacia Dental Centre
Acacia Dental Centre website
WordPress projectAcacia Dental Centre
Questions

WordPress 500 error FAQ

What to do next and what not to do.

What causes a WordPress 500 error?

Common causes include a PHP version mismatch, a broken plugin or theme, file permissions, a corrupted .htaccess rule, database errors or a failed update. The PHP error log is the fastest way to narrow it down.

What is the white screen of death?

A fatal PHP error with display_errors off, so the page returns nothing visible. 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 staging first so you can compare and identify the cause without taking the live site down again.

Can you fix it without admin access?

No. A fatal WordPress error 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.