Errors & Troubleshooting

Nothing happens when the button is clicked, and the failure could be sitting in the browser, the server, or the email step after both.

Your page is secure but one thing on it is not, and the browser is refusing to pretend otherwise — here is how to find that one thing.

PHP could not even read the file, let alone run it — here is how to use the exact line it names to find the real mistake.

Visitors landing on adverts or a strange site instead of yours almost always means injected code somewhere, not a lost or destroyed site.

Working on a laptop and broken on a phone is a specific, common pattern with a small set of specific, common causes.

The page itself loaded fine — it is the stylesheet that failed, and the browser network tab will show you exactly why.

A bare list of files and folders is what a server shows when it cannot find an index file — here is why that happens and the fix.

A holding page tells visitors you are working on it, rather than leaving them staring at a half-finished change or an error mid-update.

One log entry usually says more than an hour of guessing — here is where to find it and how to read what it is telling you.

The gap between a ticket solved in one reply and one that takes five is almost always down to five specific pieces of detail.

A site that looks down to you might only be down for you — here is how to check from outside your own network before assuming the worst.

Two redirects are fighting over the same request, and the browser is caught between them — here is how to work out which one is wrong.

The specific error changes every time, but the method for tracking it down barely does. Here is that method, laid out in order.

It means the server tried, failed, and chose not to tell you why in public — the real reason is written to a log only you can read.

Your files and data are still there — a suspension is a switch, not a deletion. Here is what causes it and how to get it lifted.

If it loads for you and not for someone else, the site is not broken in general — something between the two of you is different.

Your page never rendered because the server handed out the raw source code instead of running it — here is why that happens.

A plain list of filenames where your homepage should be means the server has nothing to show instead — here is the fix.

The change genuinely saved. Something between the server and your screen is still handing out a copy made before it happened.

To a browser, www.yourdomain.com and yourdomain.com are two different addresses unless something explicitly ties them together.