CheckWebsiteNow

Connection errors

Firefox: The connection has timed out

The website did not answer Firefox in time.

Quick answer

Firefox waited for the server but got no reply. The server may be slow or down, or your connection, proxy or security software may be getting in the way.

When to wait: Often yes; try again in a few minutes.

If you are visiting the website

  1. Wait and reload Wait a few minutes, then click Try Again or reload the page once. Short overloads often fix themselves.
  2. Try another browser Open the same address in another browser. If it works there, the problem is in Firefox's settings or stored data, so continue with the next steps.
  3. Clear data for this one site Click the padlock icon in the address bar, then 'Clear cookies and site data'. This removes cookies and cached files for that site only; you may need to sign in again there.
  4. Check Firefox's proxy setting Firefox can use its own proxy (a middle server that forwards traffic). Open Settings, scroll to Network Settings, click Settings… and choose 'No proxy' if you do not need one, or 'Use system proxy settings' if your company requires a proxy.
  5. Clear Firefox's and your device's address cache Type about:networking#dns in the address bar and click 'Clear DNS Cache'. Then clear your device's cache too, so an old server address is forgotten.
    Windows
    Open Command Prompt and run: ipconfig /flushdns
    macOS
    Open Terminal and run: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
    Linux
    On systems with systemd-resolved, run: resolvectl flush-caches
    Android
    Turn Airplane mode on, wait about ten seconds, then turn it off again.
  6. Test in Troubleshoot Mode Open the menu, choose Help > Troubleshoot Mode… and click Restart. Extensions are turned off for this session; if the site now loads, re-enable extensions one at a time to find the cause.
  7. Try another network Switch from Wi-Fi to mobile data, or the other way round. If the site works there, your network or internet provider may be involved.

If you run the website

  1. Test from outside Run curl -v --connect-timeout 10 https://example.com (use your domain) from another network. A stall while connecting means packets to your server get no reply.
  2. Check server load Look at load, open connections and logs at the time of the timeouts. A fully busy server stops accepting new visitors.
  3. Check firewalls and security groups Rules that drop traffic on ports 80 and 443 cause timeouts. Make sure both ports are open to the public.
  4. Check your hosting provider's status Your host may have a known outage. Their status page or support can confirm it.

Is it Firefox, my device or the website?

If other browsers on the same device load the site, look at Firefox: its proxy setting, extensions or stored data. If every browser fails, test another network.

If the site fails on every device and network, the website itself is slow or down.

How it differs from "Server not found"

"Hmm. We're having trouble finding that site" means Firefox could not turn the name into an address. "The connection has timed out" means the address was found, but the server never answered.

So name settings (DNS) matter less here. Network path, proxy, firewall and server load matter more.

For developers: what happens technically

Firefox opened a TCP connection attempt (the basic link for web traffic) and got no reply before its time limit. The cause sits anywhere between the visitor and the server.

Typical server-side reasons are dropped packets at a firewall, a server that is off, or a backlog of connections the server cannot accept.

Common questions

Will clearing cookies delete my saved passwords in Firefox?

No. Clearing cookies and site data for one site signs you out of that site, but saved passwords are stored separately and stay.

Why does the site open in Chrome but not in Firefox?

Firefox has its own proxy setting, its own DNS cache and its own extensions. Check those first, especially the proxy setting in Network Settings.

Is Troubleshoot Mode safe to use?

Yes. It only turns off extensions and a few features for that session. Restart Firefox normally and everything comes back.

Likely causes

  • Common The website is overloaded or offline. (Website side)
  • Sometimes A slow connection or proxy problem. (Your side)
  • Rare Firefox's cache for the site is damaged. (Your side)

Is the website down? Check it now

One measurement point. Results explain what we saw, not a worldwide verdict.

Sources

Last reviewed: