A website that suddenly stops loading can be worrying—especially if customers, leads or search-engine visitors depend on it.

However, a website being unavailable does not always mean the hosting server is down.

The problem could be caused by DNS, SSL, expired domain registration, WordPress errors, PHP configuration, database connectivity, incorrect files, caching, Cloudflare, resource limits or even a local internet issue.

The fastest way to restore a website is therefore not to start changing random settings.

Instead, identify where the problem exists and troubleshoot it systematically.

In this guide, we’ll cover 15 common reasons why a website is not loading, explain how to identify each problem and show you what to check before contacting your hosting provider.

---

First: Is the Website Down for Everyone or Just You?

Before changing anything, determine whether the website is actually unavailable to everyone.

Try opening your website from:

• Your normal Wi-Fi connection
• Mobile data
• Another device
• Another browser
• Private/incognito mode
• A different internet connection if available

If the website works on mobile data but not Wi-Fi, the hosting server may be perfectly fine.

The problem could instead involve:

• DNS caching
• Local browser cache
• ISP DNS
• Router cache
• Your public IP being blocked
• A local network problem

If your domain was recently pointed to new hosting, read our guide explaining DNS propagation and how to check it.

---

1. Your Domain Is Not Pointing to the Correct Hosting Server

One of the most common reasons a new website does not load is incorrect DNS configuration.

Your domain name must resolve to the server where your website is hosted.

If the domain is registered elsewhere and your hosting account is with myglobalHOST, you normally need to configure either:

• The correct nameservers, or
• The appropriate DNS records

If the domain points to the wrong server, your website may:

• Show an old website
• Display a parking page
• Show a hosting-provider default page
• Return an error
• Fail to load completely

How to Check

Use the myglobalHOST DNS Checker to examine your domain’s DNS status.

If you’re setting up a new hosting account, follow our complete guide on how to point a domain to myglobalHOST.

You can also confirm where to find your myglobalHOST nameservers.

Important

Do not repeatedly change nameservers or DNS records because a website fails to load immediately.

First verify whether the DNS configuration is correct and whether the change is still propagating.

---

2. DNS Propagation Is Still in Progress

Even if you configured the domain correctly, visitors may not immediately receive the updated DNS information.

DNS resolvers can temporarily cache the previous records.

This can produce confusing symptoms such as:

• Website works on your phone but not your computer
• Website works for you but not your customer
• Old website appears intermittently
• Different networks reach different servers
• SSL works on one connection but not another

Nameserver changes may take up to approximately 24–48 hours to become consistently visible across different networks, although many DNS updates appear much sooner.

Read DNS Propagation Explained: How Long Does DNS Take & How to Check It? before assuming the hosting server is down.

---

3. Your Domain Name Has Expired

A website cannot function normally if its domain registration has expired and the registrar has stopped resolving it correctly.

Depending on the registrar and domain extension, an expired domain may:

• Stop resolving
• Display a registrar parking page
• Redirect to a renewal notice
• Enter an expiry or redemption period

What to Check

Log in to your domain registrar and verify:

• Domain status
• Expiry date
• Auto-renewal status
• Renewal invoice/payment status

Remember:

Domain registration and web hosting are separate services.

An active hosting account cannot make an expired domain resolve correctly.

If you’re still learning how domains and hosting work together, our complete beginner’s guide to web hosting explains the relationship.

---

4. The Domain Has Not Been Added to cPanel

Pointing a domain toward a server does not automatically configure that domain inside every hosting account.

The web server must know which account and document root should handle requests for the domain.

If you’re using an additional domain, make sure it has been added to your hosting account.

Follow our guide on how to add a new domain in cPanel.

After adding the domain, confirm that:

• The domain name is correct
• The correct document root is assigned
• Website files exist in that document root
• DNS points toward the correct hosting server

---

5. Your Website Files Are Missing or in the Wrong Folder

If DNS is correct but the server cannot find the website files, the site may show:

• A blank directory
• A default page
• 403 Forbidden
• 404 Not Found
• A server-generated error page

On many cPanel accounts, the primary domain’s files are stored inside:

public_html

Additional domains may have their own document roots.

Check Your Files in cPanel

Log in to your hosting control panel using our guide on how to log in to cPanel at myglobalHOST.

Then open:

cPanel → File Manager

Check whether your website contains an entry file such as:

index.php

or:

index.html

inside the domain’s correct document root.

If you’re unfamiliar with File Manager, these guides may help:

5 life-saving cPanel File Manager tricks

and

cPanel File Manager vs FTP.

---

6. Your Website Is Showing a 404 Not Found Error

A 404 error means the requested resource could not be found.

If only one page shows a 404 error while the homepage works, this is usually not a server outage.

Possible causes include:

• Incorrect permalink structure
• Deleted page
• Broken link
• Incorrect .htaccess
• WordPress rewrite-rule problem
• Wrong URL
• Missing file

For WordPress websites, follow our dedicated guide on how to fix a 404 error in WordPress.

WordPress Permalink Quick Check

In WordPress, try:

Dashboard → Settings → Permalinks

Then save the permalink settings again.

This can regenerate WordPress rewrite rules in many common cases.

Do not manually overwrite .htaccess without first taking a backup.

---

7. Your Website Is Showing a 503 Service Unavailable Error

A 503 Service Unavailable response usually means the server or application is temporarily unable to handle the request.

Possible causes include:

• PHP resource exhaustion
• WordPress plugin problems
• Excessive requests
• Application overload
• Maintenance conditions
• Memory limitations
• Temporary backend failure

If you’re running WordPress, use our detailed guide to fix a 503 Service Unavailable error in WordPress.

Important

A 503 error does not automatically mean that the entire physical hosting server is offline.

If only your website is affected while other services remain accessible, the issue may exist at the website/account/application level.

---

8. WordPress Has Run Out of PHP Memory

WordPress websites can fail when PHP does not have enough memory to complete a request.

You may see an error containing text similar to:

Allowed memory size exhausted

This can be caused by:

• Heavy plugins
• Large themes
• WooCommerce
• Page builders
• Image-processing operations
• Poorly optimized code
• Large imports
• Excessive concurrent tasks

If you see an allowed-memory error, follow our guide on how to increase the WordPress memory limit.

Increasing memory can resolve legitimate memory shortages, but do not treat it as a substitute for finding a badly behaving plugin or application.

---

9. WordPress Cannot Connect to the Database

WordPress depends on its MySQL or MariaDB database.

If WordPress cannot connect to the database, the website may display:

Error establishing a database connection

Common causes include:

• Incorrect database name
• Incorrect database username
• Incorrect database password
• Database user missing privileges
• Damaged database
• Database service problem
• Incorrect wp-config.php values

Check wp-config.php

WordPress stores its database configuration in:

wp-config.php

Typical values include:

DB_NAME

DB_USER

DB_PASSWORD

DB_HOST

If your website was recently migrated, make sure these values match the database on the new hosting account.

Our WordPress migration guide explains how these database credentials must be updated after moving a website.

For database maintenance, you can also refer to our guide on how to repair and optimize a MySQL database.

---

10. Your SSL Certificate or HTTPS Configuration Is Broken

Sometimes the website itself is online, but visitors cannot access it correctly over HTTPS.

Possible symptoms include:

• Certificate warning
• Connection not private warning
• SSL handshake problem
• Too many redirects
• Mixed HTTP/HTTPS behavior
• Website works over HTTP but not HTTPS

Before troubleshooting SSL, first confirm that the domain actually points to the correct hosting server.

Once DNS is correct, check whether a valid SSL certificate exists for the domain.

Our guide explains how to install and activate SSL in cPanel hosting.

If the certificate is already valid but HTTP does not redirect correctly, see how to force SSL/HTTPS using .htaccess.

Avoid Redirect Loops

Do not stack multiple conflicting HTTPS redirects in:

• .htaccess
• WordPress
• Cloudflare
• Plugins
• Application configuration

Multiple redirect systems can create:

ERR_TOO_MANY_REDIRECTS

Use one clear, intentional HTTPS configuration.

---

11. A WordPress Plugin or Theme Has Broken the Website

A plugin or theme update can sometimes introduce:

• PHP fatal errors
• Compatibility problems
• White screens
• Broken layouts
• Redirect loops
• 500-level errors
• Admin dashboard failures

If your website stopped working immediately after:

• Installing a plugin
• Updating a plugin
• Updating WordPress
• Changing themes
• Updating PHP

the recent change is a strong troubleshooting clue.

Disable a Plugin Without WordPress Admin Access

If you cannot access wp-admin:

1. Open cPanel → File Manager
2. Navigate to:

public_html/wp-content/plugins/

3. Locate the suspected plugin folder.
4. Rename the folder temporarily.

For example:

plugin-name

to:

plugin-name-disabled

Then test the website again.

If it starts working, the plugin likely contributed to the issue.

Do not permanently delete the plugin until you understand the cause.

---

12. Your .htaccess File Contains Incorrect Rules

The .htaccess file can control important Apache/LiteSpeed behavior including:

• WordPress rewrites
• Redirects
• HTTPS enforcement
• Access restrictions
• Security rules

A small syntax or redirect mistake can make the website inaccessible.

Possible symptoms include:

• 500 error
• Redirect loop
• 403 error
• Pages returning 404
• Homepage works but internal pages fail

Before changing .htaccess, always create a backup.

For WordPress, you can temporarily rename:

.htaccess

to:

.htaccess-backup

and test the site.

If the website starts loading, the previous .htaccess configuration requires investigation.

You can then regenerate WordPress permalink rules through:

WordPress Dashboard → Settings → Permalinks → Save Changes

Be careful if your .htaccess contains custom security, SSL or application rules.

---

13. Cloudflare or CDN Configuration Is Incorrect

If you use Cloudflare or another CDN/proxy, visitors may communicate with that service before reaching your hosting server.

The request path can look like:

Visitor → Cloudflare/CDN → Hosting Server

A problem anywhere in that path can affect website availability.

Possible causes include:

• Cloudflare points to the wrong origin IP
• Incorrect DNS record
• SSL mode mismatch
• Cached error response
• Firewall blocking proxy IPs
• Redirect loops
• Origin server unreachable

If Cloudflare manages your authoritative DNS, changing a record only inside cPanel may not change the DNS response served publicly by Cloudflare.

Our guide on Cloudflare and SEO configuration contains additional Cloudflare configuration considerations.

Quick Diagnostic

If you recently changed hosting providers, confirm that Cloudflare’s A record points toward the new server IP, not the old hosting server.

---

14. Your Hosting Account Has Reached Resource or Disk Limits

Hosting accounts have finite resources.

Depending on the plan, limits may apply to resources such as:

• CPU
• RAM
• Processes
• Entry processes
• Disk space
• Inodes
• PHP resources

A poorly optimized application, traffic spike, malicious bot activity or heavy background process can cause the account to reach resource limits.

This may result in:

• Slow website
• Intermittent errors
• 503 responses
• PHP failures
• Upload failures
• Cron problems
• Database issues

Check Disk Usage

In cPanel, open:

Files → Disk Usage

Our guide explains how to use the cPanel Disk Usage tool.

Large files commonly include:

• Old backups
• Error logs
• Cache files
• Large email folders
• Staging copies
• ZIP archives
• Database exports

Do not delete files randomly simply to free space.

Identify what they are first.

---

15. Your Local IP, Firewall or Security Layer Is Blocking Access

If the website works for everyone except you, the problem may not be the website at all.

Your current public IP may have been temporarily blocked because of:

• Multiple failed login attempts
• Repeated email authentication failures
• Aggressive FTP connections
• Security rules
• Firewall protection
• Suspicious request patterns

Before assuming the website is down, test it using mobile data.

If it works on mobile data but not your normal internet connection, compare your public IP address using the myglobalHOST IP Detector.

Do not disable security systems merely to make the website accessible.

If you believe your IP has been blocked, contact support and provide:

• Your domain name
• Your public IP address
• The exact error
• Approximate time of the problem
• A screenshot if relevant

---

Bonus: Your Website May Be Loading, but Extremely Slowly

Sometimes users describe a website as “down” when it is actually taking a very long time to respond.

Slow loading can be caused by:

• Oversized images
• Too many plugins
• Poor database optimization
• No caching
• Slow external APIs
• Heavy page builders
• Too many HTTP requests
• Poorly optimized themes
• Resource-intensive cron tasks
• Malware
• Excessive bot traffic

For WordPress websites, follow our 15-step WordPress speed optimization guide.

If you’re using LiteSpeed hosting, also configure LiteSpeed Cache for WordPress.

---

Website Down After Moving to a New Hosting Provider?

If the problem started immediately after a hosting migration, check these items in this order:

1. DNS

Does the domain resolve to the new server?

Use the myglobalHOST DNS Checker.

2. Domain Configuration

Has the domain been added to the destination cPanel account?

3. Website Files

Are all files present inside the correct document root?

4. Database

Was the database imported?

5. wp-config.php

Do the WordPress database credentials match the new database?

6. SSL

Does the destination server have a valid certificate for the domain?

7. PHP Version

Is the application compatible with the PHP version enabled on the new hosting account?

8. Caching/CDN

Is Cloudflare or another CDN still pointing toward the previous server?

For the complete process, use our WordPress hosting migration guide.

---

Website Down After Updating WordPress?

If your WordPress website stopped working immediately after an update:

1. Check whether the frontend and wp-admin are both affected.
2. Check for a PHP error.
3. Temporarily disable the plugin that was updated.
4. Try switching away from a recently changed theme.
5. Verify PHP compatibility.
6. Check the WordPress memory limit.
7. Review the site’s error log.
8. Restore from a recent backup if necessary.

Before major WordPress updates, creating a backup is always recommended.

See how to take a full cPanel account backup manually for an additional recovery option.

---

Website Down After Changing PHP Version?

Older websites, plugins and themes may not be compatible with a newer PHP version.

Symptoms can include:

• Blank page
• Fatal error
• 500 error
• Broken plugin
• Broken WordPress admin
• Missing PHP extension errors

If your site stopped working immediately after changing PHP, that timing is an important clue.

Where appropriate, temporarily return to the previously working PHP version and investigate compatibility before upgrading again.

Do not leave outdated PHP versions in use permanently purely to avoid fixing incompatible code.

---

Website Is Blank With No Error Message

A completely blank page is often called the WordPress White Screen of Death, although blank pages can occur in other PHP applications too.

Potential causes include:

• PHP fatal error
• Plugin conflict
• Theme conflict
• Memory exhaustion
• Broken code
• Error display disabled
• Corrupt files

For WordPress, start by:

1. Checking error logs.
2. Disabling recently changed plugins.
3. Checking PHP compatibility.
4. Checking memory limits.
5. Testing the active theme.
6. Restoring known-good files if necessary.

Avoid enabling public PHP error output permanently on a production website because error messages can expose sensitive technical information.

---

How to Check Whether cPanel Is Working

If your website is unavailable, try logging into cPanel separately.

Use our cPanel login guide.

If cPanel loads but the website does not, this can help narrow the problem toward:

• Website configuration
• DNS
• Application
• PHP
• Database
• SSL
• Domain configuration

rather than assuming the entire server is offline.

---

When Should You Contact myglobalHOST Support?

Contact support when you have performed the basic checks but cannot identify the cause.

Providing useful information can significantly improve troubleshooting.

Include:

• Domain name
• Exact error message
• Screenshot
• When the issue started
• Whether the site previously worked
• Recent changes you made
• Whether cPanel works
• Whether email works
• Whether the site works on mobile data
• Your public IP if only you are affected

You can follow our guide explaining how to open a ticket at myglobalHOST.

Avoid sending only:

“Website not working.”

A detailed report makes technical diagnosis much faster.

---

Quick Website-Down Troubleshooting Checklist

Use this order before making major changes:

1. Test the website from another network.
2. Confirm the domain has not expired.
3. Check the domain’s DNS.
4. Check whether DNS propagation is still occurring.
5. Verify the domain exists in cPanel.
6. Confirm website files are in the correct document root.
7. Note the exact HTTP/error message.
8. Check SSL.
9. Check WordPress plugins/themes.
10. Check .htaccess.
11. Check database connectivity.
12. Check PHP compatibility and memory.
13. Check Cloudflare/CDN configuration.
14. Check account disk/resource usage.
15. Check whether your IP may be blocked.
16. Contact support with the diagnostic information if the problem remains.

---

Frequently Asked Questions

Why is my website not loading?

A website can stop loading because of DNS problems, an expired domain, missing files, WordPress errors, PHP problems, database connectivity, SSL issues, Cloudflare configuration, hosting-resource limits, security blocking or local internet/cache problems.

How do I know if my hosting server is down?

Test the website from multiple networks and check whether services such as cPanel are accessible. If only your website is affected, the issue may be limited to the website, DNS or hosting account rather than the entire server.

Why does my website work on mobile data but not Wi-Fi?

The two connections may use different DNS resolvers, or your Wi-Fi public IP may be blocked. DNS caching can also cause one network to resolve a newer IP while another continues using an older one.

Why is my website showing an old version after changing hosting?

Your domain may still be resolving to the previous server because of DNS caching, or the old content may be coming from browser, CDN, Cloudflare or application cache.

Why is my website showing 503 Service Unavailable?

A 503 response means the website or server is temporarily unable to handle the request. Possible causes include application errors, resource exhaustion, high traffic, memory limitations or temporary backend problems.

Why does my website show 404 on all pages except the homepage?

On WordPress, this commonly points toward a permalink or .htaccess rewrite problem. Re-saving WordPress permalinks may regenerate the rewrite configuration.

Can SSL make my website unavailable?

Yes. An invalid certificate, incorrect HTTPS redirect or conflicting SSL configuration can prevent visitors from accessing the website normally, even when the web server itself is online.

Can Cloudflare make my website look down?

Yes. Incorrect Cloudflare DNS, SSL settings, origin configuration, cache or proxy connectivity can cause errors even when the hosting server itself is working.

Should I reinstall WordPress if my website stops loading?

Usually not as the first troubleshooting step. Reinstalling WordPress can complicate the problem or risk data loss. Identify the actual cause first.

Should I restore a backup immediately?

A backup can be useful if the outage followed a known damaging change, but first identify when the problem began and make sure the backup itself is from a known-good point in time.

---

Final Thoughts

When your website is not loading, the most important step is to identify where the failure occurs.

A website request involves several layers:

Domain → DNS → Network → CDN/Firewall → Hosting Server → Web Server → PHP/Application → Database → Website

A failure at any one of those layers can make the website appear “down.”

Therefore, do not immediately assume that the hosting server has failed.

Start with the simplest checks:

• Test another network
• Verify the domain
• Check DNS
• Identify the exact error
• Verify the hosting configuration
• Check the website/application
• Review SSL, PHP and database status
• Check Cloudflare or other proxies
• Contact support with useful diagnostic information when necessary

If your domain was recently connected to hosting, start with our complete domain pointing guide.

If you recently changed DNS, read our DNS propagation troubleshooting guide.

These two checks alone can explain a large number of apparent website outages after new hosting setups and migrations.