Walkthrough · Intermediate · 30 minutes
How to Fix a WordPress 500 Error
Trace an internal server error straight back to its actual cause — a hands-on walkthrough in plain words that names the classic mistake before you reach it.
The short answer
One line covers it: trace an internal server error straight back to its actual cause — a intermediate-level job of roughly 30 minutes.
Below are the precise steps, the classic stumble, and one tip from the support desk. Wherever the platform already does a step for you, the guide says so rather than handing you a machine's chores.
By the Hosting & Domains team · Reviewed 18 August 2026
Intermediate
Skill rating
30 minutes
Time budget
5
Steps in total
24/7
Support on call
No prior knowledge assumed — a hosting account, a browser and 30 minutes of attention is the whole entry requirement. Every instruction runs on our platform exactly as printed, and carries over to any standard cPanel host.
First rule: read the snag section before you start, not afterwards. It was distilled from the tickets of everyone who tried the other order.
The outline first, then the detail
Set out end to end, the route is: read the error log first, question the .htaccess file, grant php more headroom, bisect the plugins and the theme and check the php version.
No part of this needs code or a terminal unless the guide says so plainly — and where it does, the exact commands are printed. The step-by-step is below, with the surrounding sections supplying the context that makes it hold.
The error nearly everyone hits
Refreshing and hoping. A 500 is deterministic: the same cause produces it every time until somebody removes that cause, and the error log named it on the very first occurrence.
Forewarned is genuinely forearmed here. This one mistake accounts for most of the frustration the topic ever causes — and it disappears entirely once somebody points it out.
What we tell every customer
Write down everything that changed in the hour before the error: updates, new plugins, template edits, PHP settings. There is nearly always a moment when a 500 was born, and that moment names its parent.
Habits this small are what separate the people who find hosting effortless from the people who find it draining. The same tools on both sides — a different way of working.
The parts that look after themselves here
Some steps in this guide exist only because hosting traditionally forced them on you. Here the SSL issues itself, the copy is taken daily without being asked, and one-click installers remove the manual setup. What is left is the part that was always genuinely yours.
Should a step still misfire, support answers at any hour with an actual fix rather than a knowledge-base link and a shrug. Half the guides on this site began as repeat patterns in our ticket queue.
Why this job is shorter on our plans
Tutorials written against imaginary hosting go stale fast. Ours are written against the real thing: the same panel, installer and defaults waiting in your account.
NVMe storage and LiteSpeed caching sit under every tier, the smallest plan included — that is the floor here, not an upgrade.
- Every step checked exactly as published
- The snag named before it arrives
- The dull steps taken out of your way
- People reachable at any hour you stall
Why Hosting & Domains
Standard on every plan
Works exactly as printed
Every step is proven on the platform we run — none of the 'your host may vary' hedging.
Taken from real tickets
These guides came out of the support queue, so every snag flagged is one people genuinely hit.
Honest about how big it is
Trace an internal server error straight back to its actual cause is a intermediate-level job — set aside 30 minutes, with the platform-absorbed steps marked.
Every undo written out
Any step that could bite is marked, together with the exact way to wind it back.
Jargon never charges you
Every term is defined on the spot or linked to the jargon buster — nothing assumes prior knowledge.
5 steps, nothing padded
Each stage is a few minutes of steady clicking, and the fiddly moments are labelled fiddly.
Quick Start
Order placed to site online
- 1
Read the error log first
cPanel's error log, or WP_DEBUG_LOG where it is switched on, usually names the exact file and line. The 500 page visitors see is vague deliberately; the log behind it rarely is.
- 2
Question the .htaccess file
Rename it and reload the site. If the site comes back, rebuild the rules by re-saving permalinks under Settings. Corrupted rewrite rules are among the three commonest causes there are.
- 3
Grant PHP more headroom
A script that runs out of memory throws a 500, sometimes only under load. Raise the memory limit in wp-config.php or the panel's PHP settings, then trigger whatever caused it again.
- 4
Bisect the plugins and the theme
Renaming folders in File Manager disables components from outside WordPress, which is how you corner a fatal error in a plugin or theme even when the dashboard itself will not load.
- 5
Check the PHP version
A 500 that appears straight after a PHP version change means some component is not ready for it. Step the version back in the panel, update the laggard, then go forward again.
Built In
Fitted to every plan
- The name's first year included when you order annually
- Spam and virus screening on every mailbox by default
- DDoS filtering absorbed at the network edge
- SSH, Git and Composer on the developer plans
- WordPress and 400+ further applications installed in one click
- People on the support desk every hour of every day
- Mailboxes that answer at the name you hold
- Staging copies for trying a change before it goes live
- cPanel, which is what most of the industry already runs
- Upgrades applied in place, with no migration when you change plan
Frequently Asked
The questions that come up most
Nobody touched the site and the error appeared — how?
Something changed all the same: an automatic update ran, a cron task fired, a resource ceiling was reached, or the host adjusted PHP. The error log carries the timestamp; line it up against update logs and traffic and the cause usually appears.
Do 500 errors affect search rankings?
A short outage is shrugged off entirely. Days of them on end will push pages down. Fix it quickly and rankings barely register it, because search engines mostly tell an incident from a dead site by how long it lasts.
Where does the hardware physically sit?
The platform runs from a London datacentre with redundant power, cooling and several upstream carriers, with server-level caching in front that keeps cached pages quick for visitors anywhere. For most sites how the platform is built — NVMe disks, LiteSpeed, restrained account density per machine — counts for far more than where it sits.
Does hosting include mail?
Yes — every hosting plan includes mailboxes at your own name, with webmail, IMAP, POP and SMTP plus spam filtering on from the start. There is standalone email hosting too, for a name whose website lives somewhere else.
Keep reading
How to Create a WordPress Child Theme
Customise a theme so the next update rolls through without erasing your work — intermediate level, about 20 minutes.
How to Publish a DMARC Policy
Instruct receiving servers on how to treat mail that flunks your authentication — intermediate level, about 15 minutes plus a monitoring month.
Best Website Builder vs WordPress
Weighed properly, ending in a verdict rather than a table of ticks.
WordPress Hosting
WordPress looked after for you — LiteSpeed caching, staging copies and a daily backup.
Web Hosting
cPanel hosting on NVMe drives — SSL, the migration and year one of the name all included.
Changing hosts? Run through our checklist first.
A plain order of work for a move nobody visiting will notice: which files go over first, how to carry the mail across without losing a message, when exactly to repoint DNS, and the two mistakes behind nearly every outage we are asked to rescue.
Put the site on ground you own.
Free SSL, a free migration, renewals billed at the original rate, and people on support around the clock. That is the whole of it.
View WordPress Hosting plans