Website Down? A Step-by-Step Troubleshooting Checklist

If your website suddenly stops loading, take a breath — most outages have a straightforward cause and a quick fix. Work through this checklist from top to bottom and you will almost always find the problem before you need to contact support.

Step 1: Confirm It Is Actually Down

Before troubleshooting your server, make sure the problem is not on your end.

1. Use an independent checker. Visit downforeveryoneorjustme.com or isitdownrightnow.com and enter your domain. If it says "It's just you," the site is reachable globally — the issue is local.
2. Try a different network. Switch from Wi-Fi to mobile data (or vice versa), or use a mobile hotspot. A broken home router or ISP block can make a working site appear offline.
3. Try a different device or browser. Open the site on a second phone, tablet, or computer to rule out a device-specific fault.
4. Clear your browser cache. In Chrome, press Ctrl + Shift + Delete (Windows) or Cmd + Shift + Delete (Mac), select Cached images and files, and clear. Then reload.
5. Try an incognito/private window. Press Ctrl + Shift + N (Chrome) or Cmd + Shift + N (Mac). This bypasses cached data and extensions.

Tip: If an outside checker confirms the site is down for everyone, continue to Step 2. If it is only down for you, jump to Step 4 (DNS) or check your local network settings.

Step 2: Identify the Exact Error Message

The error your browser shows is your biggest clue. Match it to the table below to understand the likely cause before you go any further.

Step 3: Check Billing First — Hosting and Domain Renewal

Billing lapses are one of the most common causes of a sudden outage. This check takes under two minutes.

1. Log in to your Momo Cloud client area at momo.tz/billing (or the link in your welcome email).
2. Go to Services and check your hosting plan status. If it shows Suspended or Expired, renew it immediately. Your site will normally be restored within a few minutes of a successful payment.
3. Go to Domains and confirm your domain's expiry date. An expired domain stops resolving instantly, making your site invisible to everyone.
4. Check your email inbox (including spam) for any overdue invoice notices from Momo Cloud.

Tip: Enable auto-renewal for both your hosting plan and domain inside the client area to avoid unexpected downtime in the future.

Step 4: Check DNS — Is Your Domain Pointing to Momo Cloud?

Even if your hosting is active, your site will not load if DNS is misconfigured or still propagating.

1. Verify your nameservers. Your domain must use Momo Cloud's nameservers: ns1.momo.tz and ns2.momo.tz. You can check current nameservers at dnschecker.org — select NS as the record type and enter your domain.
2. If nameservers were recently changed, allow up to 24–48 hours for full global propagation. During this window some visitors will see the old site and others the new one.
3. If your nameservers are wrong, update them in your domain registrar's control panel. If your domain is registered with Momo Cloud, do this inside your client area under Domains → Manage → Nameservers.
4. If you manage your own DNS records (A/CNAME), log in to cPanel and go to Zone Editor to confirm the A record for your domain points to the correct server IP address. Your welcome email contains your server IP.

Step 5: Check Resource Limits

A sudden spike in traffic, a runaway script, or accumulated data can push your hosting plan past its limits, causing slowdowns or a complete outage.

1. Log in to cPanel (usually at yourdomain.com/cpanel or via your client area).
2. Click CPU and Concurrent Connection Usage or look for the Resource Usage section. Check for high CPU, memory, or entry process counts.
3. Go to Metrics → Bandwidth to see if you have hit your monthly transfer limit.
4. Check Disk Usage to ensure your account is not full — a 100 % full disk causes database writes to fail and can crash your site.

Tip: If you are consistently near your limits, consider upgrading your hosting plan from inside the Momo Cloud client area.

Step 6: Check Recent Changes — The Most Overlooked Cause

Think about anything that changed in the hours before the site went down. A new plugin, a theme update, a code edit, or a WordPress core upgrade are the most common culprits.

1. Deactivate recently installed or updated plugins. In WordPress, if you cannot access the admin panel, connect via cPanel → File Manager and rename the wp-content/plugins folder to plugins_disabled. Reload your site. If it works, rename it back and reactivate plugins one by one to find the bad one.
2. Switch to a default theme. In File Manager, rename your active theme folder to force WordPress to fall back to a default theme like twentytwentyfour.
3. Restore a backup. If a recent change broke things, go to cPanel → Jetbackup (or Backup Wizard) and restore a known-good snapshot from before the issue started.
4. Check and repair .htaccess. In File Manager, open public_html/.htaccess. For WordPress sites, replace the contents with the standard WordPress default rules and save.

Step 7: Enable Debug Mode and Check Error Logs

Error logs tell you exactly what is failing, which makes diagnosis much faster.

1. In cPanel, go to Metrics → Errors to see the last 300 Apache error log entries for your account.
2. For WordPress, open wp-config.php in File Manager and temporarily set WP_DEBUG to true and WP_DEBUG_LOG to true. Errors will be written to wp-content/debug.log. Remember to set them back to false once you have identified the problem.
3. Check the PHP error log in cPanel under Metrics → PHP Errors or look for error_log files inside public_html.

Step 8: Check Your SSL Certificate

An expired or misconfigured SSL certificate will show a browser warning that many visitors will not click through, effectively taking your site offline.

1. In cPanel, go to Security → SSL/TLS Status and check that your domain shows a green, valid certificate with a future expiry date.
2. If the certificate is expired, click Run AutoSSL to issue a free replacement. The process usually completes within a few minutes.
3. If AutoSSL fails (for example because your domain's DNS is not pointing to Momo Cloud), fix the DNS issue first (Step 4), then re-run AutoSSL.

When and How to Contact Momo Cloud Support

If you have worked through every step above and the site is still down, Momo Cloud's support team is available 24/7 and ready to help. To get the fastest resolution, include the following information in your first message:

• Your full domain name (e.g., example.co.tz)
• The exact error message your browser displays
• A screenshot of the error (attach it to your ticket or live chat)
• The date and time the problem started
• Any recent changes you made before it went down (plugin installs, DNS edits, code changes)
• What steps you have already tried from this checklist

Open a support ticket from your Momo Cloud client area, start a live chat from the main website, or call our local support line — all available around the clock. The more detail you provide upfront, the quicker our team can pinpoint and resolve the issue without back-and-forth delays.

Closing Reassurance

A website going down feels stressful, but almost every outage has a clear cause and a clean fix. By working through this checklist — confirming the outage, reading the error, checking billing and DNS, reviewing recent changes, and inspecting logs — you can resolve the vast majority of issues yourself in under 15 minutes. When you do need us, Momo Cloud's team is here around the clock to get your site back online and your visitors served as quickly as possible.