A 500 internal server error is a message from a website's server saying that something went wrong on its side and it does not know how to describe the problem. Your request was fine, but the server could not finish the job. You may see it written as "HTTP Error 500", "Internal Server Error", "error code 500" or just a blank white page with a short line of text.
Because the fault sits inside the website, the visitor can do very little. Still, a few checks tell you whether it is a short glitch or a long outage, and whether the trouble is only on your side. Site owners will find the usual causes and the order to check them further down the page.
Common causes
1A bug in the website's code
How to tellOne page or one action fails every time, while the rest of the site works
What fixes itOwner reads the error log and fixes or rolls back the code
2A broken plugin, theme or update
How to tellStarted right after something was installed or updated on the site
What fixes itOwner disables the latest plugin or theme and tests again
3Wrong file permissions or a bad server rule
How to tellWhole site fails after a move, a restore or a settings edit
What fixes itOwner checks the rules file and sets standard file permissions
4Server out of memory or script time
How to tellFails on heavy pages like reports, uploads or checkout
What fixes itOwner raises limits or makes the heavy task lighter
5Database cannot be reached
How to tellPages that need saved data fail, static pages may still load
What fixes itOwner checks database login details and that the database is running
6A temporary glitch on the host
How to tellThe error disappears on reload after a minute or two
What fixes itWait briefly and reload once
How to fix it, step by step
Reload the page once, after a pause
Many 500 errors are short glitches. Give it about a minute, then tap the reload arrow or press F5. Do not keep tapping reload, because repeated requests can make a struggling server slower.
Open the site's home page
If the home page opens but one link gives the error, the fault is limited to that page. Write down which page it is, so the owner knows exactly where it breaks.
Open it in a different browser
Open the same address in an incognito or private tab. A bad saved cookie can sometimes trigger a 500 on a login page. If it loads in private mode, clear cookies for that site only.
Check from a second connection
Put your phone on its SIM data, or send the link to a friend who uses another provider. When they get the same page of trouble too, the site is failing for all and you can only wait.
Undo your last action if you were submitting a form
If the error came after you pressed Submit or Pay, do not send it again straight away. Check your email, order history or bank app first, since the action may have gone through before the error showed.
Report it to the site's support
Write to them with the page address, the clock time and the button you pressed. Support teams can find the matching entry in the server log far faster with these three details.
Leave it and check back
If nothing changes in an hour or two, leave it for later. A service's phone app often talks to different servers than its website, so the app can keep working. Wider checks live in apps and websites not working.
What a 500 internal server error tells you
Every reply from a web server begins with a three digit status. Codes that start with 5 say the server failed. The number 500 is the general one: the server hit a condition it did not expect and has no more specific code for it. That is why the message feels so vague. It is a catch all, and the real reason is written only in the server's private log.
You tap Place Order and the page shows 500 Internal Server Error. The server encountered an internal error and was unable to complete your request. The shop's server crashed while building your order page. Nothing is wrong with your phone or your internet.
500 compared with nearby server errors
| Code | Meaning | Who usually fixes it |
|---|---|---|
| 500 | Unexpected failure inside the server | Site owner |
| 501 | Feature asked for is not supported | Site owner |
| 502 | Middle server got a garbled answer | Owner or host |
| 503 | Server too busy, or paused | Time or owner |
| 504 | Middle server ran out of patience | Owner or host |
Related guides: 502 Bad Gateway, 503 Service Unavailable, 504 Gateway Timeout. The HTTP status codes page lists the rest.
How site owners track down a 500 error
- Open the error log. On most hosting panels it is called Error Log or Logs. The last lines usually name the file and line that failed.
- Undo the latest change. Switch off the newest plugin, theme or code update. If the site returns, you found the cause.
- Check the server rules file. A single wrong character in an Apache
.htaccessfile or an nginx config can return a 500 for the whole site. - Check permissions. Folders are normally 755 and files 644. Wrong values after copying files are common.
- Check memory and the database. A full disk, an exhausted memory limit or a stopped database all produce a 500.
Take a backup before you edit server files. If you use shared hosting and cannot find the cause, hosting support can read logs you cannot see.
Proxy and network pages that show a 500
If the error page shows the name of a content delivery network, the message may come from that layer. In that case the site's own server (the origin) usually returned the failure, and the network simply passed it on. The fix is still on the origin. Visitors can do nothing different, and owners should check the origin logs rather than the network settings.
Is it your device, or the website?
A genuine 500 never comes from your phone, laptop or browser. If other websites open normally, your connection is fine. If every site fails, check internet not working instead. The one exception is a login or checkout page that errors only on your account, which points to bad data saved for you, so contact the site's support.
Frequently asked questions
What does error 500 mean?
It means the website's server ran into an unexpected problem and could not complete your request. The code does not say what the problem was. Only the site owner can read the details in the server log.
Can I fix a 500 internal server error myself?
As a visitor, not really. You can reload after a minute, try another browser and check whether others see it. If it persists, tell the site's support team. Site owners can fix it by reading the error log.
What is the internal server error meaning in Hindi?
It means "server ke andar koi gadbad ho gayi hai". The website's computer failed while doing your request. The fault is with the website, not with your phone or internet.
Is a 500 error caused by my internet?
No. A dead connection gives a "cannot connect" screen with no page at all. Seeing a 500 page proves your request arrived and the server stumbled afterwards.
What does a 500 internal server error nginx page mean?
It means the nginx web server returned the 500 status, usually because the app behind it crashed or a config rule is wrong. The site owner should check the nginx and app error logs.
How long does a 500 error last?
A glitch may clear in minutes. A bad update can last until the owner rolls it back, which is often within hours. If one site stays broken for days, use its other contact channels.