Website Not Working? A Step-by-Step Checklist to Find and Fix the Problem Fast
Website down, showing errors or loading forever? Use this step-by-step checklist to find the cause, from server and DNS issues to API and database errors, and know when to call an expert.
Table of Contents
Quick answer: When a website stops working, check five things in order: whether it is down for everyone, the hosting and server status, the domain, DNS and SSL, the server error logs, and any recent code, plugin or API change. Most outages trace back to one of these. If you cannot find the cause within an hour, book on-demand technical support and let a verified engineer diagnose it.
A broken website costs leads, sales and trust every minute it stays down. The good news is that most failures follow a few predictable patterns. This checklist helps you narrow the problem quickly, even if you are not a developer.
Is the website down for everyone or just for you?
Start here because it saves the most time. Open the site on mobile data, in a private browser window and from a different device. If it loads elsewhere, the problem is local: browser cache, a VPN, a firewall or your internet provider.
If it fails everywhere, the issue is on the server, domain or code side. Move to the next step.
What do common website error messages mean?
The error message points you to the right layer. Use this table as a first diagnosis.
Error you see | What it usually means | Where to look first |
|---|---|---|
500 Internal Server Error | The server code crashed | Server error logs, last deployment, plugin updates |
502 Bad Gateway / 504 Gateway Timeout | The app server or an upstream service is not responding | App process status, server load, slow database queries |
503 Service Unavailable | Server overloaded or in maintenance mode | Hosting dashboard, traffic spikes, maintenance flags |
404 Not Found on many pages | Broken routing or permalinks | Rewrite rules, .htaccess, routing config |
"This site cannot be reached" / DNS error | Domain or DNS records are wrong or expired | Domain registrar, DNS records, domain expiry date |
"Your connection is not private" | SSL certificate expired or misconfigured | Certificate expiry, renewal job, CDN SSL settings |
Database connection error | Database is down, full or credentials changed | Database server status, disk space, config file |
Step-by-step checklist to fix a website that is not working
Check the hosting status page. Your hosting or cloud provider may have an outage you cannot fix yourself.
Confirm the domain and SSL are valid. Expired domains and certificates cause sudden, total outages.
Read the server error logs. The last error before the outage usually names the failing file, query or service.
Roll back the last change. If a deployment, plugin update or config change happened just before the failure, revert it first and investigate later.
Test third-party APIs. Payment gateways, CRMs and email tools can fail or change their responses. Check webhook and API logs.
Check the database. Look for a full disk, too many connections or slow queries locking tables.
Check server resources. CPU, memory and disk at 100 percent will slow or stop the site.
Why does a website suddenly stop working without any changes?
Even when nobody touched the code, something around it changed. The most common silent causes are:
An SSL certificate or domain that expired without renewing.
An automatic plugin, theme or package update.
A third-party API that changed or went down.
Disk space filling up with logs, backups or uploads.
A traffic spike, bot attack or crawler overload.
When should you call an expert instead of fixing it yourself?
Call for help when the site handles payments or leads, when the logs make no sense to you, or when your original developer is unavailable. Guessing on a live production server can cause data loss or a longer outage.
With QuickHire, you book hours, share the error details and a verified engineer starts after a short kick-off call with a project manager. On-demand technical support covers website and web app bugs, API and integration issues, backend errors, database problems and server deployments. If the problem is clearly in your hosting or pipeline, cloud and DevOps support is the more specific fit.
How to prevent your website from breaking again
Set uptime monitoring with alerts by email or chat.
Turn on auto-renewal for the domain and SSL certificate.
Test updates on a staging copy before production.
Keep daily backups and test that they restore.
Log every deployment so you know what changed and when.
Frequently asked questions
Why is my website showing a 500 Internal Server Error?
A 500 error means the server code crashed while building the page. It is usually caused by a bad deployment, a faulty plugin or theme update, a syntax error or a failed database query. The server error log shows the exact cause.
How do I know if my website is down for everyone?
Open the site on mobile data, in a private window and on another device. If it fails everywhere, the problem is on the server, domain or code side. If it works elsewhere, the issue is your browser, network or VPN.
Can an expired SSL certificate take my website down?
Yes. Browsers block sites with expired or misconfigured SSL certificates and show a privacy warning, which stops most visitors. Renewing the certificate and enabling auto-renewal fixes it.
How fast can I get help fixing a broken website?
With QuickHire on-demand technical support, you book hours and a verified engineer starts after a short kick-off call, usually the same day. Pricing starts at ₹1,250 per hour.
Should I roll back or fix forward when my site breaks after an update?
Roll back first if the failure started right after a change. Restoring service is the priority. You can then reproduce and fix the issue safely on a staging copy.
Get your issue fixed today
Book on-demand technical support on QuickHire, share the problem and a verified expert starts after a short kick-off call. For a full overview of every support service, read our guide to on-demand technical support.
