--- title: What Is Error 500? Causes, How to Trace It, and How to Fix It description: A 500 Internal Server Error means the server failed for an unspecified reason. Here are the usual suspects, how to read the logs, and what to avoid. canonical: https://penasihathosting.com/en/hosting-wiki/error-500 type: wiki locale: en updated: 2026-09-29 author: Willya Randika --- # What Is Error 500? Causes, How to Trace It, and How to Fix It ## Overview - **Summary:** A 500 Internal Server Error means the server failed for an unspecified reason. Here are the usual suspects, how to read the logs, and what to avoid. - **Author:** Willya Randika ([profile](/penulis/willya-randika)) ## Article ## What Is Error 500? Error 500, or *Internal Server Error*, is an HTTP status code that appears when the server fails to handle a request because of **something unexpected** — without telling you what. It isn't a specific diagnosis. It's a catch-all bucket: plugin conflicts, broken `.htaccess` rules, incompatible PHP versions, memory exhaustion — all can end up as a 500. Good news: almost every 500 traces back to something that recently changed on your side. Less good news: finding it takes some detective work. 💡 A Simple Analogy: Error 500 is the "check engine" light in a car. It knows something is wrong, it flags loudly, but it never names the broken part. You still need a reader tool — for websites, that tool is the error log. ## How Error 500 Happens on the Server Side The chain looks like this: 1. The request reaches the web server and gets passed to the [PHP](/en/hosting-wiki/php) application. 2. The application hits a condition it can't handle — an exception, an unknown function, a killed script. 3. No page output is produced; the web server responds with status 500 and the browser shows a generic "Internal Server Error" page. The actual details live in logs, not on screen. So step one of any 500 response is the same: find the error log. On [cPanel](/en/hosting-wiki/cpanel) there's an "Error Logs" menu; on a VPS it's usually under `/var/log/`. On managed hosting, support can pull it for you. ## The Most Frequent Causes * **Plugin or theme conflicts** — especially right after an update. One plugin calls a function that no longer exists. * **A broken [.htaccess](/en/hosting-wiki/htaccess) file** — a bad rewrite rule makes the web server refuse to process. The classic cause after installing security or SEO plugins. * **PHP memory limit exceeded** — the script needs more memory than the plan allows. * **PHP version mismatch** — moving to PHP 8 with older, incompatible code triggers fatal errors. * **Wrong file permissions** — FTP uploads with incorrect permissions can leave scripts un-executable. * **A half-finished migration** — or a `wp-config.php` still pointing at the old database. ## What This Means for You as a Site Owner Know your limits. If a 500 happens on shared hosting and you can't access logs, handing it to support is a perfectly reasonable move — they read these logs all day. What you *can* do: recall what changed last (an update? an install? a migration?) and undo that one change. If 500s appear repeatedly while you've touched nothing, that's a different signal: server quality, tight resource limits, or a plan that no longer fits your site. ## Common Mistakes When Fixing It **Deleting `.htaccess` without a copy.** It's a legitimate diagnostic step, but save the original first — the rules often encode caching and security configuration you'll want back. **Raising `memory_limit` to the sky.** Sometimes that's genuinely the fix. Sometimes a leaky plugin is just postponing the crash. Find what's hungry before expanding the plate. **Mixing up the codes.** An [error 503](/en/hosting-wiki/error-503) means the server can't respond right now — often load or maintenance, not broken code. An [error 429](/en/hosting-wiki/error-429) means rate limiting. Note which code you actually saw. **Panic-restoring an old backup.** Disable the recently updated plugin via File Manager (rename its folder) before you consider rolling back the whole site. ## FAQs ### Is error 500 bad for SEO? If it persists, yes — Google may treat the page as unavailable and drop it from the index. That's why a 500 that shows up during peak traffic shouldn't be left to "fix itself." ### Why does the 500 only appear on certain pages? Usually because those pages invoke the problematic code — a page with a form, checkout, or one generated by a specific plugin. That actually helps: narrow your investigation to what those pages use. ### Why did my site 500 after moving hosts? Common culprits: a different PHP version, file permissions, or a `wp-config.php` with old database credentials. Check the error log — it usually names the source directly. ### Can the hosting server itself cause a 500? It can, though it's less common. A saturated resource pool or a server-side software upgrade sometimes triggers 500s across many sites at once. If it hits many sites after a change you didn't make, ask support.