Skip to content
Website Rescue Rescue

General Website Problems

Website Will Not Load

Intermediate Risk: medium

Last reviewed

Hosting access may not be needed Database access usually not needed

Direct answer

A site that will not load is usually a DNS failure, an SSL/certificate block, a server 5xx, or a WordPress PHP fatal—not one generic bug. Identify the browser error or HTTP status first, then follow the matching specialized fix; do not rebuild WordPress while the domain still fails to resolve.

“Will not load” covers several different failures that need different repairs. This triage guide separates local browser/network issues from DNS, SSL warnings, HTTP 5xx, and WordPress critical errors or white screens, then points you to the right next guide so you spend time on the actual layer that broke.

Intermediate

What the error means

Loading a website is a chain: the device must resolve the hostname (DNS), open a TCP/TLS connection (network and certificate), receive an HTTP response from the origin or CDN, and finally run application code such as WordPress/PHP. A break at any step looks like “the site is down” to visitors, but DevTools, dig, and status codes tell you which layer failed. Treating every outage as a plugin problem wastes hours when the domain does not resolve or the certificate is expired. Triage top-down: confirm your own network, then DNS, then TLS, then HTTP status, then WordPress logs.

Common symptoms

  • Browser shows a connection error, blank page, timeout, or interstitial instead of the site
  • ERR_NAME_NOT_RESOLVED / NXDOMAIN while other websites still work
  • Certificate or “Your connection is not private” interstitial before any page content
  • HTTP 500, 502, 503, 504, or Cloudflare 5xx-style error page
  • WordPress critical error message or white screen of death after the connection succeeds
  • Site loads on mobile data but not Wi-Fi (or the reverse), suggesting local DNS or firewall
  • Temporary host URL or raw IP works while the custom domain does not

Most likely causes

  1. 01 Local device offline, captive portal, VPN, or browser extension blocking the request
  2. 02 Domain DNS misconfigured, expired, or still propagating after an NS/A change
  3. 03 TLS certificate missing, expired, mismatched, or incomplete chain
  4. 04 Origin or CDN returning 5xx (overloaded host, bad gateway, maintenance)
  5. 05 WordPress PHP fatal from plugin, theme, core update, or PHP version change
  6. 06 Firewall, WAF, or bot challenge blocking your IP while others still see the site

What changed before the problem started

  • Domain, nameserver, or hosting IP migration
  • SSL renewal failure or CDN SSL mode change
  • WordPress core, plugin, theme, or PHP update
  • Host outage, resource limit, or Cloudflare proxy setting change
  • New security plugin, WAF rule, or VPN on the visitor device

Troubleshooting steps

  1. 01

    Rule out a local browser or network problem

    Try another browser, a private window with extensions disabled, and another network (phone data vs Wi-Fi). If only one device fails, fix local DNS, VPN, or extensions first. Success signal: another network or device reaches the site—or every client fails the same way, so the problem is upstream.

  2. 02

    Read the exact browser error or HTTP status

    Note ERR_NAME_NOT_RESOLVED, connection timeout, certificate interstitial, or an HTTP status from DevTools → Network on the document request. That single clue chooses the next guide. Success signal: you can say “DNS,” “TLS,” “5xx,” or “WordPress HTML error” instead of “down.”

  3. 03

    If DNS fails, stop and fix resolution first

    NXDOMAIN / ERR_NAME_NOT_RESOLVED means the name never became an IP—WordPress is irrelevant until dig and ICANN Lookup look healthy. Follow the domain-not-resolving guide for NS, A/AAAA, expiration, and glue. Success signal: the domain resolves to the intended IP from a public resolver.

  4. 04

    If TLS warns, fix certificates before chasing plugins

    Certificate errors and “Not secure” interstitials are SSL/TLS problems: renew or reissue the cert, align www and apex, and clear mixed-content issues after HTTPS works. See the Not secure guide. Success signal: HTTPS loads without a certificate interstitial.

  5. 05

    If you get HTTP 5xx, check host and CDN then application logs

    502/503/504 and many Cloudflare edge errors point at origin health, timeouts, or proxy misconfiguration. Confirm the host panel and CDN status, then read origin error logs. Use the 500 and Cloudflare 522 guides when those match. Success signal: you know whether the origin answers or the edge is failing first.

  6. 06

    If HTML shows a WordPress critical error or white screen, isolate PHP

    When the connection succeeds but WordPress returns a critical error or blank page, enable debug logging (display off), check recovery email, and isolate plugins/themes. Use the critical error and white screen guides. Success signal: logs name a plugin/theme path or recovery mode restores admin.

When to stop troubleshooting

Hand off when you lack registrar, DNS, host, or wp-admin/FTP access; when DNS and SSL look correct but 5xx persists after host checks; or when WordPress fatals continue after basic plugin isolation on a revenue site. Provide the exact browser error, dig output, HTTP status, timestamps, and what already changed so a pro starts at the right layer.

Information to collect before requesting help

  • 01 Exact browser message or Chromium error code
  • 02 HTTP status of the main document request (if any)
  • 03 Whether other devices/networks can load the site
  • 04 dig/nslookup result for the domain (A/AAAA/NS)
  • 05 Whether a temporary host URL or IP loads
  • 06 Recent DNS, SSL, hosting, or WordPress/PHP changes
  • 07 Screenshots of certificate warnings or WordPress critical/white screens

How a professional repairs the problem

We triage by layer—client, DNS, TLS, edge/origin HTTP, then WordPress—using dig, certificate inspection, and status codes before touching plugins. Once the failing layer is identified, we apply the matching repair path (DNS correction, certificate reissue, origin/CDN recovery, or PHP isolation), verify the full load path from public resolvers through HTTPS to a clean HTML response, and leave you with the specialized follow-up guide for that root cause.

Frequently asked questions

Why does this guide not give one universal fix? +
Because “will not load” is a symptom shared by DNS, SSL, server, and WordPress failures. The correct fix depends on which link in the chain broke; triage first, then use the specialized guide.
The site works on my phone but not my laptop—what now? +
That pattern usually means local DNS cache, VPN, hosts file, or a browser extension—not a full outage. Flush local DNS, disable VPN/extensions, and compare dig from both networks.
Is a white screen the same as DNS failure? +
No. DNS failure never fetches your server. A white screen means the connection reached WordPress/PHP and the app crashed with errors hidden. Different tools and different guides.
Should I reinstall WordPress immediately? +
Not until DNS resolves and HTTP reaches the origin. Reinstalling core does nothing for NXDOMAIN or an expired certificate and can complicate a simple plugin fatal.
What does HTTP 503 usually mean here? +
The server or edge is unreachable or intentionally unavailable—overload, maintenance, or a crashed upstream. Check host status and CDN, then application logs if origin is up.
Where should I go next after triage? +
DNS errors → domain not resolving; certificate warnings → Not secure; 5xx → 500 or Cloudflare 522; WordPress message/blank page → critical error or white screen guides linked below.

Repair dispatch

Still Need Help Fixing Your Website?

If you are not comfortable editing website files, changing server settings, repairing a database, or troubleshooting a live website, professional help may prevent additional damage or downtime. We will review the problem before accepting the repair.

  • You will receive a clear explanation of the likely cause.
  • We will tell you if the issue falls outside our repair scope.
  • No additional work will be performed without approval.
  • A backup should be created whenever access and website condition allow it.
Emergency repair Request diagnosis

Do not share passwords through an unencrypted contact form.

Written by Website Rescue

Last reviewed

Platform note: Full rescue available for WordPress and self-hosted sites. Wix, Squarespace, Webflow, Weebly, and similar closed builders have very limited backend access — fixes may not be possible. I will tell you honestly before we start.