When a site is down, confirm first that it fails for everyone and not just your network. Then read the exact error: a DNS failure, a 500, a 502, a 503 or a billing lock each has a different fix. Change one thing at a time, and keep a backup ready.
See whether it fails for everyone or just you
Load the site on mobile data with Wi-Fi off, then in a private window. If it opens on mobile data but not on your Wi-Fi, the fault is your network, DNS cache, VPN or browser rather than the server. A hard refresh, Ctrl+Shift+R or Cmd+Shift+R, bypasses a stale local copy.
If it fails on mobile data too, the site or its DNS is down for everyone, and the rest of this page applies. The public status page for this network is network status.
Read the error you actually see
The error narrows the fault before you change anything: a DNS failure or an expired name means the domain, a 500 means the application, a 502 or 504 means the server waited on PHP or the database, and a 503 means the server is overloaded or in maintenance.
| What you see | What it usually means | What to do next |
|---|---|---|
| DNS error, name does not resolve | Domain expired, or its A record or nameserver is wrong | Check the domain expiry date and the DNS record in the host panel |
| 403 | A file or folder permission, or a firewall rule | Undo the last permission change; ask the host if a rule was added |
| 404 on every page | The document root or a rewrite rule is wrong | Restore the .htaccess or the site root path from the last working copy |
| 500 | The application threw an error, often a plugin or a broken file | Read the error log, then disable the last plugin or theme change |
| 502 or 504 | The web server waited on PHP or the database and gave up | Check PHP workers, database connections and slow queries |
| 503 | Overload, maintenance or a resource limit | Read CPU and entry processes in the panel |
| Database connection error | The database service is down, or its user or password changed | Check the database service and the credentials in the config file |
| SSL warning or expired certificate | The certificate lapsed or the domain on it changed | Renew or reissue the certificate after the DNS is correct |
Undo the last change
- Note the plugin, theme, deploy or file you changed last, with its time.
- Turn that one change off and purge the cache.
- Reload on mobile data, not on the browser tab you already have open.
- If the site returns, leave the change off until you know why it broke.
A stack of five edits hides the one that broke the site, and so does a cache that still serves the old page. If a deploy went out in the last hour, roll it back before you read any further.
Check the host panel, DNS and SSL certificate next
When nothing changed, the cause is usually outside the code: a suspended account, an expired domain, a wrong DNS record or an expired certificate. Read the host panel first for a suspension or resource notice, then check the domain expiry date and the certificate date.
An unpaid invoice can suspend an account while every file is still in place, so pay it and reload before debugging anything else. An expired domain fails DNS even when the server is healthy, and a certificate that lapsed shows a browser warning rather than a server error.
If the panel shows a hard resource limit rather than a fault, the plan is the problem. On 30 October 2026, WebJi shared plans are ₹300 and ₹700 a month, and a KVM VPS starts at ₹499, all before 18% GST. WebJi states a 99.9% uptime target; a bad plugin still takes a site down inside that target.
Restore a backup only when the files are the broken part
Restore when the files or the database are damaged and a rollback does not bring the site back. Copy the broken state first so the cause can still be found, then restore from a point before the break.
Check uploads and the database separately, because a backup can be partial: a site that loads with missing images has restored files but not the media folder. Test the restore on a staging copy when the host allows it, and only then replace the live site.
Tell users and search engines while the site is down
For planned downtime, return a 503 with a Retry-After header so crawlers treat the outage as temporary, and put one line on a status page or social profile. A 503 is read as maintenance; a 404 or a 500 left for days is read as a broken site.
Pause paid campaigns while the site is down, otherwise you pay for clicks that land on an error. When the site is back, post the same one-line update in the same place, so nobody keeps retrying an old page.
What to check after the site is back
Confirm the fix held for an hour, write down the start time and the cause, and test that the backup you rely on actually restores. Then check whether the same fault can repeat before the next campaign; how to prevent a crash when traffic spikes covers the capacity side.
If the host must look, email support@webji.services. That mailbox is 24/7 in Hindi and English. The office number is for business hours and is not a support line.
Frequently Asked Questions
How do I know the website is really down?
Open it on mobile data with Wi-Fi off, then in a private window. If it loads there, the fault is your network, DNS cache or browser; if it fails there too, the site or its DNS is down for everyone.
What does a 500 error mean?
The application on the server threw an error. A plugin, a theme or a broken file is the usual cause, so undo the last change first and reload. If the error started on its own, read the server error log for the failing file.
What if only I cannot open it?
Hard-refresh the page, clear the browser cache, and switch off a VPN or proxy. A site that opens on mobile data is up for everyone else, so the fault is on your network or device.
What do 502 and 503 mean?
A 502 means the web server got an invalid answer from PHP or another upstream service, and a 504 means that upstream took too long. A 503 means the server is overloaded or in maintenance, and a planned 503 with Retry-After tells search engines the downtime is temporary.
When do I restore a backup?
Restore when the files or the database are the broken part and undoing the last plugin does not bring the site back. Copy the broken state first, restore from a point before the break, and check uploads and the database separately.
Is WebJi® an Indian company?
Yes. WebJi® is headquartered in Jaipur, Rajasthan and has operated since 2005. Billing, support and governance all run from India.
Do you provide GST invoices?
Every purchase and renewal gets a GST invoice with our GSTIN, and hosting prices are quoted exclusive of 18% GST. Claim input credit as applicable.