How-to · Intermediate · 20–40 minutes
How to Fix a WordPress 500 Error
Everything you need to trace an internal server error back to whatever is actually causing it — the steps in order, the snag to watch, and the tip our support desk gives everybody.
Straight answer first
In a line: trace an internal server error back to whatever is actually causing it — a intermediate-level task that takes 20–40 minutes.
Below you get the exact steps, the classic snag, and a tip from the support desk. Where our platform handles a step for you, the guide says so rather than making you do the robot's work.
Written by the Hosting Seller staff · Checked 1 August 2026
Intermediate
Difficulty level
20–40 minutes
Time to allow
5
Stages
24/7
Help at any hour
This guide assumes no expertise at all — just a hosting account, a browser and 20–40 minutes of attention. Every instruction works on our platform exactly as written, and carries over to any standard cPanel host.
Rule of the road: read the snag section before you begin rather than after. It is harvested from the tickets of people who did it the other way round.
The overview before the detail
Here is the route in full: read the error log before anything, suspect the .htaccess file, give php a bit more room, bisect the plugins and the theme and check the php version it runs on.
No stage needs code or a terminal unless the guide says so outright, and where it does, the exact commands are printed. The full step-by-step sits below; the sections around it give the context that makes it stick.
The mistake nearly everyone makes
Hitting refresh and hoping. A 500 is deterministic — the same cause produces it every time until somebody removes that cause — and the error log has been naming it since the very first attempt.
Forewarned really is forearmed here. This one mistake accounts for most of the frustration the subject produces, and it is entirely avoidable once somebody names it.
The tip we hand out to everybody
Write down what changed in the hour before the error appeared: updates, new plugins, template edits, PHP settings. A 500 nearly always has a birthday, and the birthday points straight at the parent.
Small habits like this are the real difference between people who find hosting easy and people who find it stressful. The tools are identical; the working method is not.
What runs by itself here
Several steps in this guide exist only because hosting historically made you do them. On our plans SSL issues itself, backups run daily without being asked, and one-click installers replace the manual setup entirely. What is left is the part that is genuinely yours.
And when a step misbehaves anyway, support answers at any hour with the actual fix, not a knowledge-base link and a shrug. Half our best guides began life as a pattern in the ticket queue.
The hosting this guide is written against
Tutorials age badly when they are written against imaginary hosting. These are written against ours: the same panel, the same installer and the same defaults you will meet.
Backups run every day on every plan, and putting a file or a database back takes one click from the panel.
- Step by step, tested exactly as printed
- The snag flagged before you reach it
- The dull steps are already automated
- People on hand at any hour if you stall
Why Hosting Seller
On every plan, as standard
Works exactly as written
Every step tested on the platform we run — no 'your host may differ' hand-waving anywhere.
Written from real tickets
Our guides come off the support desk, so the snags flagged here are the ones people genuinely hit.
Scoped honestly
Trace an internal server error back to whatever is actually causing it is a intermediate-level task — this guide budgets 20–40 minutes and says which steps the platform absorbs.
The undo is always named
Where a step could bite, the guide says so and tells you how to put it back again.
No jargon toll
Terms are explained where they appear or linked to the glossary — nothing assumes you already know.
5 steps, no filler
Each stage is a few minutes of steady clicking, with the fiddly parts marked as fiddly.
First Steps
From choosing to live
- 1
Read the error log before anything
cPanel's error log, or WP_DEBUG_LOG if you have it switched on, usually names the exact file and line. The 500 shown to visitors is deliberately vague; the log behind it rarely is.
- 2
Suspect the .htaccess file
Rename the file and reload the site. If it comes back, regenerate the rules by re-saving your permalinks under Settings. Corrupted rewrite rules are among the three most common causes there are.
- 3
Give PHP a bit more room
A script running out of memory throws a 500, often only under load. Raise the memory limit in wp-config.php or through the panel's PHP settings, then reproduce whatever triggered it.
- 4
Bisect the plugins and the theme
Renaming folders through File Manager switches things off from outside WordPress, which isolates a fatal error in a plugin or theme even when the dashboard itself will not load.
- 5
Check the PHP version it runs on
A 500 appearing right after a PHP version change means some component is not ready for it. Roll the version back in the panel, update the component that is lagging, then move forward again.
In the Box
Packed with every plan
- SSH, Git and Composer on the plans built for developers
- The renewal price printed on the tag matches the order price
- Mailboxes that carry your own domain name
- One-click installs for WordPress and 400+ other applications
- Staging copies so changes get tested before they go live
- Nothing added at setup — no joining fee, ever
- Upgrades apply to the account in place, with no move between plans
- Spam and virus filtering fitted to every mailbox
- A backup taken daily, with restores you run yourself
- A 99.9% uptime commitment, watched by monitoring day and night
Across the Counter
The questions we get asked most
Nothing was changed and the error appeared anyway — what then?
Something changed regardless: an automatic update ran, a scheduled task fired, a resource limit was reached, or the host adjusted PHP. The error log gives you the timestamp; line that up against update logs and traffic and the cause usually appears.
Will a 500 error damage my search rankings?
A short episode is shrugged off entirely. Days of them will see pages pushed down. Fix it promptly and rankings barely register it — search engines tell an incident from an abandoned site mainly by how long it lasts.
Where do the servers actually sit?
Our hosting runs from European datacentres with London at the centre, behind server-level caching that keeps cached pages quick for visitors anywhere. For most sites the build of the platform — NVMe disks, LiteSpeed, sensible numbers of accounts per machine — decides the speed far more than the postcode does.
Does hosting come with mailboxes?
It does — mailboxes on your own domain ship with every hosting plan, with webmail, IMAP, POP and SMTP access and spam filtering fitted as standard. There is also standalone email hosting for domains whose website lives somewhere else entirely.
Is the SSL certificate genuinely free?
On every plan, with nothing held back. The certificate is issued the moment your domain points here and reissues itself well before expiry. The encryption is the same as a paid DV certificate — paid tiers exist only for wildcard coverage or organisation validation, which most sites never need.
What does round-the-clock support actually stretch to?
People at the counter at every hour, and a scope that takes in the practical work: mailbox setup, DNS records, WordPress trouble, restores. Not 'the server responds, ticket closed'. Ask us something hard before you order — the reply is a fair sample of what you would get afterwards.
What happens to my files if I leave?
The site and the files stay yours. Pull a full backup from the panel whenever you like, before or during cancellation. Domains remain registered in your name for the term you paid for and can move to any registrar once the standard 60-day window has passed.
Read next
How to Add TXT Records for Verification
Prove the domain is yours to Google, Microsoft and everyone else who asks — beginner level, about 5 minutes per service.
How to Create a WordPress Child Theme
Customise a theme in a way that survives the next update intact — intermediate level, about 30 minutes.
Domain Names
Search, register and transfer names — year one free with annual hosting.
Drupal Hosting
Drupal hosting with Composer, Drush and the PHP version set per site.
Packing up and moving host? Take our checklist.
A plain running order for a move nobody notices: what to copy first, how to carry email across without dropping a single message, when to point DNS, and the two slips behind nearly every hour of downtime we get called about.
Your site is worth better hosting.
Quick NVMe hosting, SSL and the move in included, and real people on the counter at any hour — on a price that doesn't shift.
See the plans