WordPress Tip: Site Shows Blank Page On Home Networks

7 min read

Last updated October 23, 2026

Last updated October 23, 2026: the diagnosis was rebuilt as a step-by-step checklist, with the checks that come before the fix (prove it is only you, cache, DNS, hosts file), the modern equivalents of the 2015 GoDaddy panel step, recovery mode, and the Short Version, FAQ, Bottom Line, and Winston poll added.

This is a very common problem, and a maddening one. A friend of mine in California, a friend for over twenty years, had a WordPress site on GoDaddy hosting that worked normally for everybody else on Earth. On his home network, the pages were completely blank. Nothing would load at all. He trusted me with his credentials, and I went hunting. This article is the hunt, in the order I would run it today, because a WordPress blank page that only you can see is almost never the mystery it appears to be.

Contents

• First, Prove It Is Only You
• Clear the Local Suspects
• The Fix That Worked: End All Processes
• If the Site Is Blank for Everyone
• Frequently Asked Questions
• The Bottom Line

Professor Winston Wants to Know

Our resident watchdog is taking the temperature of the room.

Has your own website ever vanished for you but worked for everyone else?

One tap, no account or email needed. Results are shown after you vote.

Has your own website ever vanished for you but worked for everyone else?

Yes, and it was my network or cacheYes, and it was a plugin or themeNo, but now I am nervousSomeone else handles my website

Cast your voteSee results

Want to say more? The comments below are open.

First, Prove It Is Only You

Before touching a single setting, establish whose problem this is. Pick up your phone, turn off Wi-Fi so you are on cellular data, and load the site. If it appears, your website is healthy and the fault lives in your house: your browser, your router, your ISP, or your hosting account’s view of your connection. If it is blank on cellular too, skip ahead to the last section, because the site itself is down. A checker like Down for Everyone or Just Me gives you the same answer from a third party. This one test, which takes twenty seconds, would have saved me the first hour of my friend’s case, because I started by suspecting his plugins.

I did what most people do. I disabled his security plugin, in case it had locked him out. Nothing. I disabled all his plugins. Nothing. I rebuilt his .htaccess file from scratch. Nothing, though I have left those steps in this article, because they genuinely fix other blank sites. His site was never broken. It was only broken from his house.

Clear the Local Suspects

Work these in order; each takes minutes.

Browser cache and a second browser

Hard-refresh the page, then try a private or incognito window, then a completely different browser. A corrupted cache can serve you a blank page long after the real site has healed, and this is the single most common cause of a site that is down only for its owner.

Flush your DNS cache and restart the router

Your computer and router remember where your site lives, and stale directions can point at a dead end. Restart the router first; it clears its cache and renews its own information. On a Mac, flush the local DNS cache from Terminal with sudo dscacheutil -flushcache followed by sudo killall -HUP mDNSResponder. On Windows, run ipconfig /flushdns from a command prompt. Then load the site again.

Check your hosts file

During development, people sometimes add a line to their computer’s hosts file pointing their domain at a specific server, then forget it exists. Months later the site moves and their machine keeps knocking on the old door. If you have ever edited the hosts file (on a Mac it is /etc/hosts, on Windows it sits in the System32 drivers folder), open it and look for your domain. Delete the line or comment it out.

The Fix That Worked: End All Processes

Drumroll, please. The solution was something quite unexpected, and it was on the hosting side all along. In his GoDaddy control panel there was a page called System Processes, with a black and green icon toward the bottom of the panel. It listed every process running on his hosting account. I selected All Processes and clicked End All, which is best understood as a reset button for the account: it kills anything hung, stuck, or quietly eating the account’s resources. The moment I clicked it, he could view his site again. Immediately.

Hosting panels have changed since 2015, and GoDaddy’s current dashboards do not look like these screenshots. The principle, however, has not aged a day: hosting accounts accumulate hung PHP and cron processes, and a stuck process can serve blank pages to the very connection that triggered it while the rest of the world browses happily. The modern equivalents are to look for a PHP or process restart option in your host’s panel, clear any server-side caching the host provides, and, failing all that, open a hosting support ticket and ask them, in exactly these words, to kill the hung processes on the account. It is a two-minute job on their side, and it ends cases like this one. GoDaddy and I have history, by the way: my separate wrestling match with a GoDaddy WordPress login loop is its own saga, and it taught me the same lesson about checking the account before blaming the site.

If the Site Is Blank for Everyone

That is the classic white screen of death, a different animal with a standard playbook.

Disable plugins by FTP

Connect with an FTP client or your host’s file manager and open the wp-content folder. Rename the plugins folder to plugins.old. Every plugin deactivates at once. If the site returns, rename it back and reactivate plugins one at a time until the blank page returns; the last one is your culprit.

Regenerate .htaccess

A corrupted .htaccess file breaks sites quietly. The easy regeneration, if you can reach the dashboard, is Settings, then Permalinks, then Save Changes, touching nothing. By hand, the default single-site file is:

# BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
# END WordPress

Switch themes and use recovery mode

A theme can white-screen a site just as thoroughly as a plugin. Rename your active theme’s folder inside wp-content/themes and WordPress falls back to a default theme. And since WordPress 5.2, a fatal error usually triggers recovery mode instead of a silent blank: the site emails the admin a special login link that lets you deactivate the offending plugin or theme from inside. Check the admin inbox before reaching for FTP.

Frequently Asked Questions

Why does my website work for everyone except me?

Because the problem is local to you or to your connection: a stale browser or DNS cache, a forgotten hosts file entry, your ISP’s resolver, or a hung process on the hosting account serving your requests. The cellular test separates your network from the site in twenty seconds.

What is the WordPress white screen of death?

A blank page with no error message, usually caused by a plugin or theme hitting a fatal PHP error, or by exhausted memory. Recovery mode, plugin renaming by FTP, and a clean .htaccess fix the large majority of cases.

Will ending all processes hurt my hosting account?

No. It terminates the account’s running tasks, which then restart cleanly as requests come in. It is the hosting equivalent of rebooting your own computer, and it was designed for exactly this kind of hang.

How do I know if it is a plugin?

Rename the plugins folder by FTP. If the site comes back, a plugin did it. Reactivate one at a time to find which. If the site stays blank with plugins off, the theme and .htaccess move to the top of the list.

So here is my question for you: has your own site ever gaslit you this way, perfect for the whole world and blank on your own screen, and what turned out to be the cause?