Error messages, and what fixes them

The connection opened and closed with nothing in it. That points at a backend that never replied, and there is one log line that names the cause exactly.

The connection opened and then something slammed it shut. A reset is deliberate, which makes this one of the more findable errors once you know where to look.

Nothing answered at all. Silence means a packet was dropped rather than rejected, and that narrows the search to the firewall layers between you and the port.

The server answered, and the answer was no. That is a much more specific failure than a timeout, and it points at four causes rather than twenty.

The DNS server your device is pointed at is not answering. This is a configuration problem on your side, and the fix is almost always one setting.

Chrome could not reach any DNS server at all. That usually means the connection is down - but not always, and the exception is worth knowing.

Either the certificate expired or your device's clock is wrong. One command tells you which, and the answer changes the fix completely.

The certificate is readable but the browser does not trust its issuer. Usually a missing intermediate certificate - here is the one command that proves it.

An HTTP/2 stream was rejected as malformed. Usually a bad header, a proxy that mangles frames, or PHP emitting output after the response - here is how to find which.

Chrome tried to write a request to a socket that was no longer connected. This one is nearly always local - here is the order to check things in.

HTTP/3 runs over UDP, and plenty of networks handle UDP badly. Here is how to confirm QUIC is the cause in thirty seconds, and what to fix rather than just disabling it.

Chrome aborts a request when the network changes mid-flight. Usually harmless, sometimes a symptom - here is how to tell which, and how to stop it happening.

The connection opened, the request went out, and the server closed it without sending a response. Here is how to find out which layer hung up, and why.

The lookup failed before anything was dialled. Here is how to tell a missing DNS record from a resolver problem on your own machine, and fix whichever one it is.

Chrome says the address is unreachable when the network cannot get a packet to that IP at all. Here is how to tell a stale DNS record from a routing problem.

Chrome prints the same headline for a dozen unrelated failures. The capitalised code underneath is the real error - here is what each one means.

Getting DNS_PROBE_FINISHED_NXDOMAIN in Chrome? Here's how to tell if it's your device, your DNS records, or nameserver propagation - and how to fix each.

Cloudflare is retiring Page Rules for Redirect, Cache, Configuration & Origin Rules. Step-by-step guide to migrate your redirects and caching without downtime.

MySQL error 1226 'max_user_connections' exceeded on cPanel or WHM hosting? Here's exactly why it happens and how to raise the limit and fix it for good.

Still failing 'leverage browser caching' in PageSpeed or GTmetrix? Set Cache-Control and Expires headers correctly on cPanel and VPS hosting - step by step.

Getting 'Access denied for user' connecting to MySQL in cPanel? Fix unlinked users, host mismatches, wrong username prefixes, and stale credentials fast.

Composer install failing on cPanel or a VPS? Fix memory exhaustion, proc_open blocks, timeouts, and missing SSH access with these tested steps.

WooCommerce cart or checkout block showing a blank page or error after an update? Fix block registration, Store API, and shortcode fallback issues here.

WooCommerce site crawling to a halt? A bloated Action Scheduler queue is often the hidden cause. Learn how to diagnose, clear, and prevent it for good.