Website Errors

How to Fix ERR_CONNECTION_ABORTED in Chrome

ERR_CONNECTION_ABORTEDPlain English: Chrome started loading the page, then stopped the load before it finished.
Quick answer: ERR_CONNECTION_ABORTED means Chrome stopped loading a page before it finished. Start by reloading once and waiting for the page to finish, then clear Chrome's cache and cookies, disable extensions that filter traffic, disconnect your VPN and clear any proxy, and flush DNS. If only one site keeps failing, that site's server may be ending its responses early. The full steps are below.

What ERR_CONNECTION_ABORTED means

ERR_CONNECTION_ABORTED means Chrome started loading a page and then stopped the load before it finished. Picture a download that gets cancelled halfway: the browser asked for the page, the server began answering, and then the connection ended before the full page arrived. Unlike a timeout, where nothing ever comes back, an aborted connection means something actively ended the transfer — and that something is often on your own side of the connection.

That is why this error is so often a one-off: refresh too fast, switch networks, or let a VPN drop for a second, and the load dies. When it keeps happening on the same site, though, a repeatable cause is at work — an extension, a VPN rule, a damaged cache, a firewall setting, or a server that keeps cutting responses short. The steps below remove those causes one at a time, starting with the quickest checks.

Common causes

How to fix ERR_CONNECTION_ABORTED — step by step

Work through these fixes in order. Most cases are fixed by step 1, 2, or 4.

  1. Reload the page properly and check whether one site or all sites fail. Start with the simplest explanation, because this error often means the load was interrupted rather than blocked. Press Ctrl + R once and wait for the page to finish before clicking anything else; hammering refresh, clicking a link, and hitting the back button in quick succession can each abort the load in progress and produce this exact error. Then open two or three unrelated sites. If only one site shows the error, that site's server is the likeliest cause. If every site fails, your connection, VPN, or browser is at fault, and the steps below apply. Also try the same site on another device on the same Wi-Fi: if it loads there, the problem is confined to this computer's browser or network settings.
  2. Clear Chrome's cache and cookies, then test in an incognito window. A damaged cached file or a stale cookie can make Chrome abandon a page partway through loading it. Press Ctrl + Shift + Delete on Windows, or Cmd + Shift + Delete on a Mac, set the time range to All time, check Cached images and files and Cookies and other site data, and click Clear data. Then open an incognito window with Ctrl + Shift + N and load the site there. Incognito starts with no stored cache, no cookies, and no extensions, so if the page loads there, the fault is in your saved browsing data or an extension, not your internet connection.
  3. Disable extensions, especially ones that change how pages load. Extensions that filter, redirect, or scan traffic — ad blockers, VPN extensions, download managers, script blockers, and security toolbars — can cut a connection short when they decide a request looks suspicious or when they crash mid-load. Type chrome://extensions in the address bar and toggle every extension off, then reload the page. If it loads, switch the extensions back on one at a time, reloading after each one, until the error returns; the last one you enabled is the culprit. Leave that extension disabled or remove it, and check whether it has an update that fixes the conflict.
  4. Disconnect your VPN, clear proxy settings, and steady your network connection. This error appears often when the network path changes while a page is loading — a VPN server switching nodes, a laptop hopping between Wi-Fi networks, or a mobile hotspot dropping for a second. Disconnect your VPN completely, not just pause it, and reload the page. Then clear any leftover proxy: on Windows, open Settings, go to Network and internet, then Proxy, and turn off Use a proxy server under Manual proxy setup. On a Mac, open System Settings, go to Network, select your Wi-Fi, click Details, then Proxies, and uncheck every option. Finally, restart your router: unplug it from power, wait 30 seconds, plug it back in, and wait for the lights to settle before reloading.
  5. Flush DNS and reset the network stack. Stale DNS records and a damaged network stack can cause Chrome to give up on a connection after it has already started. On Windows, open Command Prompt as Administrator and run ipconfig /flushdns, then netsh winsock reset, then netsh int ip reset, and restart your computer. On a Mac, open Terminal and run sudo dscacheutil -flushcache followed by sudo killall -HUP mDNSResponder. If the error continues, try a public DNS service: on Windows, go to Settings, Network and internet, then Wi-Fi or Ethernet, edit the DNS server assignment, and enter 8.8.8.8 and 8.8.4.4. A different DNS provider rules out a bad or slow record from your internet provider.
  6. Update Chrome, reset its settings, and rule out your firewall and the site itself. An outdated or damaged Chrome build can abort loads that a current build handles fine. Click the three-dot menu, go to Help, then About Google Chrome, and let it install any available update. If the error persists, reset Chrome: go to Settings, then Reset settings, then Restore settings to their original defaults. This clears extension settings and custom configuration without deleting your bookmarks or saved passwords. Also check your firewall: on Windows, open Windows Security, then Firewall and network protection, then Allow an app through firewall, and make sure Google Chrome is checked for Private and Public networks. Try briefly pausing your antivirus web shield as a test and switch it back on right away. Finally, check a status checker: if the site is down for everyone, wait and try again later.

Did this fix it? Quick checklist

If the error is gone in incognito but returns in a normal window, an extension or damaged browsing data is still responsible — keep extensions off and clear data with All time selected. If it happens only when your VPN is connected, try a different VPN server or protocol, and check the VPN app for a kill switch that drops traffic during server switches. And if one site keeps aborting while it is up for everyone else, try it on mobile data: if it loads there, your home network or IP address is part of the problem, and restarting your router for a fresh IP address may clear it.

Frequently asked questions

What does ERR_CONNECTION_ABORTED mean?

It means Chrome began loading a page but stopped the load before it finished. Something interrupted the connection mid-load — you navigated away, the network changed, a VPN or extension cut it off, or the site's server ended the response early.

Why does ERR_CONNECTION_ABORTED happen when I refresh or click quickly?

Because each new navigation cancels the one before it. If you refresh, click a link, or press the back button while a page is still loading, Chrome aborts the in-progress load and may show this error instead of the page. Wait for the page to finish loading, then reload once with Ctrl + R.

What is the difference between ERR_CONNECTION_ABORTED and ERR_CONNECTION_CLOSED?

They are close cousins. An aborted connection is one Chrome itself stops, often because navigation changed, the network changed, or an extension or VPN intervened. A closed connection is one that ends before the page finishes arriving, often because the server or a middle layer stopped responding. The same fixes — clear cache, disable extensions and VPN, flush DNS — help both.

Can a VPN or antivirus cause ERR_CONNECTION_ABORTED?

Yes, both are common causes. A VPN that switches servers or drops for a moment breaks every load in progress, and an antivirus web shield can abort a connection it considers risky. Disconnect the VPN completely and briefly pause the web shield as a test, turning the shield back on immediately afterward.

Does ERR_CONNECTION_ABORTED mean the website is down?

Not on its own. If every site shows the error, your connection or browser is the problem. If only one site shows it and it loads on your phone's mobile data, that site's server may be ending connections early. Check a status checker to see whether the site is down for everyone before assuming the fault is yours.