Chrome's prediction service and a full socket pool can hold a dead connection open, so the timeout repeats in Chrome while the site loads elsewhere.
Chrome's prediction service and a full socket pool can hold a dead connection open, so the timeout repeats in Chrome while the site loads elsewhere.
Test the URL in an incognito window with extensions disabled. If it loads, an extension or a stale socket pool is the cause — flush it at chrome://net-internals/#sockets.
Chrome has its own failure mode, but ERR_CONNECTION_TIMED_OUT has a wider set of causes. The most common one overall is: The origin server is down or the web server process has stopped.
Check the service is running and listening on the expected port, then restart it and confirm from outside the network.
An uptime probe from outside your network tells you whether the server is unreachable for everyone or only from where you are sitting — which is the first fork in every timeout diagnosis.
Chrome's prediction service and a full socket pool can hold a dead connection open, so the timeout repeats in Chrome while the site loads elsewhere.
Test the URL in an incognito window with extensions disabled. If it loads, an extension or a stale socket pool is the cause — flush it at chrome://net-internals/#sockets.
DNS resolved and the browser tried to open a TCP connection, but nothing answered before the timeout. The server is unreachable, overloaded, or a firewall is dropping the packets silently.