Server not responding
Nothing answered: the server is off, overloaded, out of memory or disk, or a firewall is blocking it. Check it's running, then its resources, then the network.
Server overloaded
More work than the server can handle: a traffic spike, bots, a runaway process, or a slow query. Find what's using the CPU before upgrading.
Out of memory: process killed
The server ran out of memory and Linux killed a process to survive, often your app or database. Confirm it in the system log, then find what used the memory.
Disk full
With no disk space left, databases stop, logs can't be written and uploads fail. Find what filled it (usually logs, backups or cache) and clear it safely.
Server crash
Find out what crashed (the whole machine, or just your app or database), then read the logs from just before. Most crashes are memory, disk, or a code change.
Nginx error
Nginx's error log names the problem. 502 means the app behind Nginx is down; 504 means it's too slow; a failed reload means a config typo. Run nginx -t first.
Apache not working
Check the Apache error log first: it's where Apache records every problem. If Apache won't start, test the config with apachectl configtest.
More fix guides
Search everything →Not sure what's wrong with yours?
One click checks your site, and your Cloudflare if you connect it, and gives you a report of what's wrong and what to do. Your first report is free.
Run your free report