Português
English
·
When a site breaks, the number on screen is not decoration: it tells you which side the problem is on. Three or four of them are worth knowing how to read.
| Code | What is happening |
| 500 Internal Server Error | The server tried to run the site and something blew up. Usual suspects: a broken .htaccess, wrong permissions, or a plugin/theme that failed after an update. |
| 403 Forbidden | Access was refused. Either the folder has no index file, or permissions are wrong, or our security system blocked the request as suspicious. |
| 404 Not Found | The address does not exist. If it hit the whole site at once, on WordPress it is usually .htaccess — saving the permalinks again fixes it. |
| 508 Resource Limit Reached | Your plan hit its resource limit (CPU, memory or simultaneous processes). The site is not broken: it is asking for more than the plan allows. Check Resource Usage in cPanel. |
| 502 / 504 | The service behind it took too long to answer. Usually a heavy database query or a process that got stuck. |
| Error establishing a database connection | The database credentials in wp-config.php no longer match, or the database is not responding. |
| Blank white screen | A PHP error with no visible message. The error_log in the site folder has the exact line. |
Error 508 deserves its own note
It is the most misunderstood one. It is not a fault on our side, and the site is not "broken": it is your site consuming more than the plan allows, and the server stopping it before it affects the neighbours. It typically shows up when the site has grown, when a new plugin is too heavy, or when someone is hammering the site with automated requests.
|
|
|
|
Where to find the exact cause
In cPanel, under Errors, you get the server's latest messages. In the site folder, the error_log file holds the same with more detail. One line from those logs beats an hour of guessing — if you write to us, send it.
| Before you change anything, keep a way back. Rename .htaccess instead of deleting it, and keep a recent copy — see how to restore your data with JetBackup . Plenty of sites got worse while being fixed. |
| If the site is gone entirely with no error at all, it may be something else — start with what to check when your site is down . |
|
Give us the code, the time and the address — we will go into the server logs. Open a support ticket |
|
SEE ALSO If error 508 keeps coming back, the plan is no longer enough — Shared hosting vs VPS: which one does your project need?. Many 500 errors are fixed by the right PHP version: How to change your PHP version. If the error mentions the database: Creating databases and using phpMyAdmin. |
|
WEB HOSTING Looking for hosting that stays out of your way? cPanel, a free SSL certificate, backups every night before dawn kept for a year, and support that answers in your language. See hosting plansFree migration of your current site · no lock-in |
RECOMMENDED PRODUCT Web hosting with cPanel Domain and SSL included, daily backups and the panel you already know. from $15.00/mo See plans |
- 0 Users Found This Useful
