Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Troubleshooting

Why is my website down? A troubleshooting checklist

Published August 2026 · 11 min read

“The website is down” describes a symptom, not a cause. Fast troubleshooting starts at the outside and works inward so you do not restart an application that was healthy while the domain was pointing somewhere else.

1. Define what “down” means

Record the exact error, affected URL, time, and whether the problem appears on multiple networks or devices. A browser timeout, DNS error, certificate warning, HTTP 500, and blank page point to different failure layers.

2. Check DNS

Confirm the hostname resolves to the expected address. If DNS was recently changed, compare authoritative records with what recursive resolvers return. An application server cannot fix traffic that never reaches it.

3. Check the network and TLS path

Verify the expected ports are reachable and that the TLS certificate covers the requested hostname and has not expired. If a proxy or CDN sits in front of the origin, test the origin separately when possible.

4. Check the web server and application

Look at the HTTP status code and the relevant web-server and application logs. Confirm the application process is running and listening where the proxy expects it.

Avoid restarting everything before collecting evidence. A restart can temporarily hide a failure and erase useful context.

5. Check dependencies and resources

A healthy web process may still fail because the database is unavailable, disk space is exhausted, memory pressure killed a process, a filesystem became read-only, or an external dependency is timing out.

Check CPU, memory, disk and inode usage, database connectivity, queues, and recent deployment or configuration changes.

6. Restore service, then preserve the lesson

Once service is stable, write down the cause, detection gap, and prevention. If a full disk caused the outage, restarting the application is not the complete fix; monitoring and log-retention changes are part of it.

Next step

Work through DNS, TLS, HTTP, application, database, resource, and provider checks in a useful order when a website stops loading.

Ask DotMoose about hosting

Keep reading

Related guides.

HTTP 500, 502 and 503 errors explained for website owners

Learn what HTTP 500, 502 and 503 errors usually indicate, which layer to investigate, what evidence to collect, and when restarting a service is not the real fix.

Read the guide

Virtualmin vs cPanel: Which Control Panel Should You Choose?

Virtualmin vs cPanel compared on licensing cost, account and site management, email, DNS, backups and migration, so you can pick the control panel that fits how you host.

Read the guide

How to move web hosting without downtime

Move a website and database with destination testing, final synchronization, controlled DNS cutover, and rollback while preserving separate mail routing.

Read the guide

More web hosting guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move