The server received the request and failed while handling it. The page never says why — the server’s error log does. On most sites it is one of a handful of things: a broken line in .htaccess, a PHP fatal error in a plugin or theme, the memory limit, or wrong file permissions.
Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request.
How 6 other clients word the same error
nginx
500 Internal Server Error nginx
Apache, when the custom error page fails too
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
OpenLiteSpeed
500 Internal Server Error An internal server error has occured.
IIS
HTTP Error 500.19 - Internal Server Error
ASP.NET Core
HTTP Error 500.30 - ASP.NET Core app failed to start
curl -I
HTTP/2 500
| Error | 500 Internal Server Error |
| Usually fixed by | The site owner or host |
| Status | 500 (RFC 9110 §15.6.1) |
| Means | The server failed while handling the request |
| Where the cause is | The web server’s or PHP’s error log, at the time of the request |
Check the site from outside
Enter the address: we load it from our network and show the status code, how long it took, and the error if it failed.
What it means
A 500 is the server’s catch-all for “something went wrong on my side”. The request was fine; the software handling it — the web server’s configuration or the application behind it — failed. When PHP stops on a fatal error before sending anything, it sends the 500 itself, which is why the page is sometimes blank.
Why it happens
- A line in .htaccess the server does not understand — a module that is not installed, or php_value settings on a server running PHP-FPM or LSAPI.
- A PHP fatal error: a plugin or theme calling code that does not exist, often right after an update.
- PHP running out of memory or time.
- Files owned by the wrong user, or with permissions the server refuses to run.
- A rewrite rule that loops.
- On shared hosting, the account’s memory or process limits — CloudLinux says visitors then see 500 or 503 errors.
What the error log says
Apache, a line in .htaccess it does not understand
/home/user/public_html/.htaccess: Invalid command 'RewriteEngine', perhaps misspelled or defined by a module not included in the server configuration
Apache, a PHP or CGI script that died
End of script output before headers: index.php
Apache, a rewrite loop
AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary.
nginx, a rewrite loop
rewrite or internal redirection cycle while internally redirecting to "/index.php"
PHP, out of memory
PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes)
PHP, too slow
PHP Fatal error: Maximum execution time of 30 seconds exceeded
PHP, broken code
PHP Fatal error: Uncaught Error: Call to undefined function foo()
How to fix it
- Open the error log and look at the time of the request: the web server’s log, and PHP’s (on cPanel, the error_log file in the site’s folder, or Metrics → Errors).
- If the log names .htaccess, rename the file to test, then remove or fix the line; move php_value settings to .user.ini or the host’s PHP settings.
- If it names a plugin or theme, turn that one off — rename its folder if you cannot reach the admin.
- If it is memory, raise PHP’s memory_limit, or find what uses so much.
- Set folders to 755 and files to 644, owned by the account’s user.
If you are visiting the site
- Nothing on your side causes it. Reload once; if it stays, the site owner has to fix it.
See it for yourself
curl -sI https://example.com/
tail -n 50 /var/log/nginx/error.log
The status line shows what visitors get; the last lines of the error log (Apache: error_log or error.log) say why. Match the time of the request.
Questions
Why does the page say nothing about the cause?
On purpose: the details of a server error can help an attacker, so servers show a generic page and write the real reason to the error log.
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- RFC 9110: HTTP Semantics — rfc-editor.org
- httpd/modules/http/http_protocol.c at 2.4.x — github.com
- nginx/src/http/ngx_http_special_response.c at master — github.com
- php-src/Zend/zend_alloc.c at master — github.com
- Fix HTTP Error 500.19 in IIS Configuration Files — learn.microsoft.com
- Limits — docs.cloudlinux.com