Key takeaways
- Test in a private window and on a phone with Wi-Fi off before you touch the site. If the page loads there, the problem is your browser or network, not WordPress.
- A critical error or white screen usually comes from a plugin, theme or PHP update. WordPress Recovery Mode, added in version 5.2, emails the admin a link that names the failing extension.
- Re-saving Settings, then Permalinks, fixes 404s on pages that exist. It does nothing for deleted pages, DNS problems or fatal errors.
- A WooCommerce Cart or Checkout page only works once it is assigned under WooCommerce, then Settings, then Advanced, then Page setup. Creating the page is not enough.
- Health Check troubleshooting mode changes only your own session and does not put payment gateways into sandbox mode, so a test order can take a real payment.
A customer says the checkout won’t open on their phone. You try the link and get a white screen, a gray box with an error code, or Safari’s “Safari can’t open the page.” All three look like the same complaint. They have different causes, and the wrong fix can turn one broken page into a broken site.
No WordPress error is actually called “can’t open page.” It’s a description of what someone saw. Before you change anything, find out which layer is failing: the visitor’s device, the network, the server, WordPress itself or a single page.
Whose problem is it? Five minutes of checks decide that
Write down two things before you start clicking: the full URL from the address bar and the exact message, word for word. Then run these checks in order.
- Open the homepage and one other page. If only one URL fails, it’s a page or routing problem. If everything fails, it’s the site, the server or the domain.
- Open the failing URL in a private window. This drops your cookies and logged-in state. Pages that fail only for logged-out visitors are more common than people expect.
- Try your phone with Wi-Fi switched off. Mobile data takes your router, office network and DNS resolver out of the picture.
- Ask someone on a different network to try it. What one browser shows doesn’t prove the site is down. In one Reddit thread, an owner kept seeing a critical error while a commenter could load the site normally.
| What you see | Where the fault usually is | First check |
|---|---|---|
| “Safari can’t open the page”, ERR_NAME_NOT_RESOLVED, a timeout | Device, network or DNS | Another device on another network |
| “There has been a critical error on this website”, a white screen, HTTP 500 | PHP fatal error in a plugin, theme or custom code | Recovery Mode email, then the error log |
| 404 on a page you know exists | Rewrite rules, slug, or a deleted or private page | Settings, then Permalinks, then Save |
| Blank or 404 Cart, Checkout or My Account | WooCommerce page assignment, endpoints, cache | WooCommerce Page setup |
| ERR_TOO_MANY_REDIRECTS, “Your connection is not private” | Competing redirect rules or an SSL certificate | CDN SSL mode and redirect rules |
| “Error establishing a database connection”, 502, 503 | Database, host or server resources | Host status and logs |
| 403 Forbidden | File permissions, .htaccess rules or a firewall | Host and security plugin logs |
If the page opens on mobile data but not on your Wi-Fi, the site is fine. The fix is on your side: pause any VPN or security extension, flush your DNS cache and restart the router. Our guide to fixing DNS errors on your site covers the case where the domain itself doesn’t resolve for anyone. For whole-site outages, the walkthrough on why WordPress is not loading goes further than this article.
A critical error or white screen means read the error before you disable anything
Practitioners most often report this cause, usually right after a plugin, theme or PHP update. No dataset ranks these causes, though. WordPress’s own common-errors handbook lists plugin incompatibilities, PHP errors, memory limits and corrupted files without saying how often each one happens.
The generic message isn’t a diagnosis, but WordPress usually has the real one. Since version 5.2, Recovery Mode emails the site admin when a fatal error happens. The email has a special login link that shows the error and lets you pause the plugin or theme that caused it. Check the admin inbox, including spam, before anything else.
If no email arrives, read the newest lines of your host’s PHP error log for “Fatal error” or “Parse error” and note the file path. A path inside wp-content/plugins/ or wp-content/themes/ names the culprit. If the host has no log, have WordPress write one by adding these lines to wp-config.php above the “stop editing” line:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
Reload the failing page once, then read wp-content/debug.log. WP_DEBUG_LOG only works when WP_DEBUG is on. Keep display off, because errors shown on a public page can expose file paths and other details. Remove the lines once you have your answer.
If you can’t reach wp-admin, rename the plugin’s folder over SFTP or in the host’s file manager to deactivate it. Renaming the whole plugins folder is the blunt version. It leaves must-use plugins and cache drop-ins such as advanced-cache.php and object-cache.php running. In a 2026 WordPress.org thread about a client site moving hosts, those leftover drop-ins came up as a likely trap. Re-enable plugins one at a time or in small groups, and don’t leave everything off. One agency in another thread found that an automatic deactivation had quietly taken contact forms offline across client sites.
More detail, including memory errors, is in our guide to fixing a WordPress fatal error.
One page returns 404 while the rest of the site works
If the page exists in the editor but its address returns 404, the rewrite rules are usually stale. Go to Settings, then Permalinks, and click Save Changes without editing anything. WordPress regenerates its rules. WordPress’s handbook says to ask your host to check mod_rewrite if that doesn’t work.
Re-saving only fixes routing. It won’t bring back a deleted page, fix a mistyped slug or make a private page public, so check the page’s status and slug first. If a custom post type shares a name with the page, rename one of them. On Apache, back up .htaccess before you edit it and keep any custom redirect rules. On Nginx, .htaccess does nothing, so the host has to check the server rules.
Don’t change the permalink structure to make a 404 go away. Every URL on the site changes, and old links break. Our guide to permalinks that are not working covers the harder cases.
A WooCommerce Cart or Checkout page that is blank or missing
WooCommerce’s documentation lists four usual causes: a missing or unassigned page, permalink problems, stale caches and plugin or theme conflicts. A page called “Checkout” does nothing until WooCommerce knows it is the checkout. Create the page with the Checkout block (or the Cart or My Account block), then assign it under WooCommerce, then Settings, then Advanced, then Page setup, and save.
The order-received page and the My Account sections are endpoints, not separate pages. If one of them returns 404, re-save permalinks and check the slugs under WooCommerce, then Settings, then Advanced, then Endpoints. Exclude Cart and Checkout from page caching, because they hold session-specific content.
Be careful testing conflicts on a live store. WooCommerce warns that Health Check troubleshooting mode can give false positives with some plugin, theme and hosting combinations. It also doesn’t put payment gateways into sandbox mode, so a test order can take a real payment. A WordPress staging site is the safer place for that test.
Redirect loops and certificate warnings come from rules that disagree
ERR_TOO_MANY_REDIRECTS means two rules keep sending the request back and forth. A common pattern behind Cloudflare is the Flexible SSL mode combined with a server that redirects HTTP to HTTPS. Cloudflare’s documentation says to use Full or higher when your server has a certificate, and to look for redirect rules that conflict. Check WordPress, your host and the CDN, then retest in a private window, because browsers cache redirects and can make a correct fix look like it failed.
“Your connection is not private” points to a certificate that has expired, is missing or doesn’t match the domain. Your host or CDN issues the certificate, so the fix lives there.
The whole site is unreachable or shows a database error
If no page opens on any network, look outside WordPress first. Check that the domain hasn’t expired, that DNS still points at your host, and whether the host is reporting an outage. No WordPress setting can fix any of these.
“Error establishing a database connection” can mean wrong credentials in wp-config.php, a database server that is down, or a database too large or locked to answer. In one 2026 WordPress.org thread, the host blamed a 35.68 GB wp_options table, mostly transient data, plus MyISAM table locking. The advice there was to find what was writing the data, back up, and plan the cleanup with the host. Deleting rows at random can do real damage.
“Briefly unavailable for scheduled maintenance” that never clears usually means an interrupted update left a .maintenance file in the site root. Delete that file once you’ve confirmed no update is still running.
It opens for you but fails for visitors or for Google
A logged-in admin often sees a different site from everyone else. In one r/woocommerce thread, a store loaded only for logged-in users and showed 404s in the console for everyone else. Disabling an offload plugin and repairing permissions didn’t help. The cause turned out to be the theme’s full-page preloader, and switching themes fixed it. Test logged out, every time.
Cache is the other usual suspect. A caching plugin, the host’s server cache or CDN, and the visitor’s browser can each serve an old copy. Clearing your own browser only clears one of the three.
If people can open the page but Google reports it can’t, run the URL through Search Console’s URL Inspection tool and use Test live URL. Google’s help page lists the usual blockers: a password, a robots.txt rule, or a noindex tag, which allows access but keeps the page out of the index.
When to stop and get help
Stop when the next step means editing the database, changing file permissions across the site, or running conflict tests on a store that takes payments. Stop too when the log points at the server rather than a plugin. Hosts usually handle infrastructure but send plugin and theme faults back to you, so open the ticket with the URL, the exact error, the time it started and what changed just before.
Whoever does the work should log every change and take a backup first. A restore is fast, but it throws away everything changed since the backup and doesn’t always fix the problem. Read the logs before you decide.
If you’d rather hand the job over, SiteSelf takes the URL and the error through chat and troubleshoots the WordPress site directly. It needs hosting (SSH) access to read logs and edit files.
Frequently asked questions
How do I know if my site is down for everyone or just me?
Load it on a phone with Wi-Fi off, then ask someone on a different network to try. If it loads anywhere, the site is up and the problem is local: your browser, an extension, your router or your DNS resolver.
Why does the public site work but wp-admin won’t open?
Common causes are security or login-hiding rules, redirect conflicts and a mismatch between the WordPress Address and the Site Address. Our guide to fixing WordPress login by symptom works through each one.
Should I restore a backup or keep troubleshooting?
Read the error log first. It usually takes minutes and changes nothing. A restore discards orders, posts and settings changed since the backup, and if the cause is the server or a PHP version change, the restored site can fail the same way.
Can I use Health Check troubleshooting mode on a live store?
You can, and visitors won’t see the change because it only affects your session. WooCommerce warns that it can give false positives and does not sandbox payment gateways, so take a backup and don’t place test orders unless your gateway is in test mode.
Does clearing my browser cache fix a page that won’t open?
Only when the problem is a stale copy or a bad cookie in your browser. It doesn’t touch the caching plugin, the host cache or the CDN, and it can’t fix a server error.
Leave a Reply