Knowledge base

My site shows a 500 error

A 500 means the site's own code stopped. The error log names the file and line — here is how to read it.

A 500 is the server saying your application stopped and did not say why to the visitor. It is almost always the last thing that changed.

1. Read the error log

Sites → your site → Statistics → Access and error logs. The newest entry names the file and the line. That one line usually is the answer — a missing function, a syntax error, a call to something that no longer exists.

2. Think about what changed

A plugin update, a theme edit, a PHP version change, an edited config file. If the site was fine an hour ago, the cause is in that hour.

3. Undo the most recent thing

Disable the plugin you just updated, or restore the file you just edited. If you cannot reach the admin area, rename the plugin's folder over SFTP — WordPress disables a plugin it cannot find.

4. Check the PHP version

Code written for an older PHP can stop dead on a newer one. Sites → your site → PHP shows the current version and lets you move it back while you fix the code. ⚠️ Moving back is a breathing space, not a fix — old PHP versions stop getting security patches.

5. Out of memory

If the log says "allowed memory size exhausted", the site needs more memory than it has. Raise the PHP memory limit on the same PHP screen.

If the log is empty and the site still 500s, open a ticket with the exact time — we can see things in the server logs that a site's own log never receives.

Latest from the blog

What we have been writing about hosting, SEO and running sites at scale.

SEO and Link Building from the Hosting Layer: A 2026 Operator's View

How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.

Read the post →

Making WordPress Fast and Secure: A Performance and Plugin Checklist

A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.

Read the post →

How to Choose Managed Web Hosting in 2026: A Buyer's Guide

What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.

Read the post →

Read the blog →

Still stuck?

Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.

Contact support → All articles →