Jan 06, 2023
ERR_CONNECTION_CLOSED: What It Is and 3 Ways to Fix It
If you’re a Google Chrome user, there’s a chance you’ve encountered the ERR_CONNECTION_CLOSED error message.
This issue indicates that the connection to the website is disrupted because of a server or hosting service flaw. Therefore, the target host cannot process the request and sends the ERR_CONNECTION_CLOSED response instead.
In this article, we will explain the possible causes of the ERR_CONNECTION_CLOSED issue and discuss three effective methods to solve it.
|Error type||Browser protocol error|
|Error causes||QUIC protocol|
Incompatible third-party extensions
Incorrect proxy configuration
Poor internet connection
Compromised SSL certificate
What Does ERR_CONNECTION_CLOSED Mean?
ERR_CONNECTION_CLOSED is a Chrome error that indicates that the browser fails to connect to the web server. Therefore, the connection is closed, and the error occurs. This may occur for several reasons, such as a null route, low hosting resources, corrupted cache, slow internet connection, and VPN service issues.
Some common causes of the connection closed error include:
- Null route – the server or host may experience downtime, making the system unavailable.
- Hitting server limits – the current hosting usage may overload the server resources.
- Internet connection – slow or unstable internet may interrupt the network connection.
- Browser or DNS cache – corrupted cache may cause connectivity issues.
- Virtual Private Network (VPN) service issues – certain settings inside the VPN software may block specific sites.
3 Effective Methods to Fix ERR_CONNECTION_CLOSED
Before getting to the methods to solve the ERR_CONNECTION_CLOSED error, we recommend trying some quick fixes first. These approaches are worth trying to ensure the error is not just a temporary glitch. Here are several solutions you should try:
- Check your internet connection by accessing other websites.
- Restart your internet router to fix connectivity issues.
- Check if the website is just down for you or everyone else. This helps ensure whether the issue is with the server or the device you’re using.
- Delete browser cache via Chrome settings to clear browsing data and history.
- Disable your VPN service or proxy server since it may block the website you’re trying to access.
- Flush the DNS cache to remove all existing DNS lookup records and establish a new connection using the latest ones.
- Access the website using a different network connection to ensure your Internet Service Provider (ISP) doesn’t block the site you’re trying to visit.
- Temporarily disable the firewall system or antivirus software as it may block specific websites.
- Reset Chrome settings to default. Doing so will also remove all the installed extensions, cookies, and other temporary site data.
- Use the Google DNS.
- Reinstall Chrome.
If none of the above fixes resolve the error, proceed to the following methods.
1. Check the Hosting IP Address
The ERR_CONNECTION_CLOSED error may occur if the web hosting is experiencing a null route. The most convenient way to check whether the server is up and running is by using the ping command.
The ping command will send a data packet to the target host and transmit it over the network’s switch and router. The command usually submits four to five pings at once to ensure the result is valid.
Upon receiving a data packet, the machine with the specified address returns a pong reply, confirming that it is online.
Before running the command, make sure to know your hosting’s Internet Protocol (IP) address. If you’re a Hostinger user, you can find it in hPanel -> Manage -> IP Address.
Here’s how to ping an IP address on Windows:
- Open Command Prompt by typing in the search field on the taskbar. Alternatively, use the keyboard shortcut WIN + R, type in cmd, and press Enter.
- Run the ping command along with the domain name or IP address you want to check. For example, we will ping 220.127.116.11.
- Press Enter. The pong reply will appear four times.
The command prompt will show the ping statistics at the end of the fourth reply.
Follow these steps to ping an IP address on macOS:
- Access Terminal by clicking the Launchpad icon in the Dock and typing in the search field. Alternatively, select Finder, open /Applications/Utilities, and double-click on Terminal.
- In this example, we will enter ping 18.104.22.168.
- To stop the ping command from running, press Ctrl + C. The ping statistics will show once the connection is closed.
Here’s how to ping an IP address on Ubuntu:
- Open Terminal using Ctrl + Alt + T shortcut. Alternatively, click the Show Applications button on the bottom-left corner of your screen and type in Terminal.
- Run the ping command followed by the IP address you want to check.
- Hit Ctrl + C to close the connection, and the ping statistics will appear.
If the host doesn’t send a pong reply, it may be causing the ERR_CONNECTION_CLOSED issue.
2. Check the Hosting Resources
The ERR_CONNECTION_CLOSED error message may occur if your hosting is hitting its resource limits. To prevent this issue, we recommend continuously monitoring the CPU, memory, processes, entry processes, inodes, and disk usage.
Note that hitting the resource limits can also cause the 503 Service Unavailable error message.
Here’s how to check the Order Usage for Hostinger users:
- Log in to your Hostinger account.
- On the hPanel dashboard, select the Hosting tab.
- Choose the hosting you want to check and click Manage.
- On the Hosting Account, go to Order -> Order Usage.
- See the CPU, Memory, Processes, and Entry Processes tab. Check if any of them has reached your plan’s maximum capacity.
- If either Processes or Entry Processes hit the limit, scroll down to find the Stop running processes option and click Stop. However, this is only a temporary solution. You still need to find the root cause by disabling certain plugins and reducing the number of running cron jobs.
- If most parameters inside Order Usage are constantly high, try to optimize the website.
- If there are sudden spikes in both Order Usage and Total Requests, the error may be caused by DDoS attacks. To solve this issue, apply website security best practices.
Alternatively, check the disk and inodes usage to determine the root cause of this error message. Access hPanel -> Manage -> Order Disk Usage and Order Inodes.
If one or both statistics are hitting the limits, remove unnecessary files using the File Manager to reduce the resources used.
If you have checked your hosting resources and they are still well within limits, performing a server transfer is best. Our Customer Success team can assist you with the procedure.
3. Contact Support
Since the connection closed error occurs on the server side, it can be tricky to solve it from the client side. Although there are methods to try on that end, most require prior technical knowledge.
So if the earlier solutions can’t fix ERR_CONNECTION_CLOSED on the website, we suggest contacting your hosting or internet service provider for help.
Other Error Messages Similar to ERR_CONNECTION_CLOSED
Here are five common error messages similar to the connection closed error:
ERR_CONNECTION_TIMED_OUT indicates that the browser is trying to load more than the server can handle, thus overloading the system.
This problem may occur for many reasons, such as exceeded hosting resource limits, incorrect internet settings, VPN connection issues, or faulty proxy server configuration.
Aside from that, the error connection timed out message may occur if your internet is slow. Therefore, the system can’t establish a reliable connection with the server and takes too long to respond.
ERR_CACHE_MISS is a common Chrome browser problem that indicates a caching-related issue or incorrect DNS settings. However, it is more of a warning than a standard error.
The Confirm Form Resubmission message may appear when a user reloads a web page or clicks the back button after submitting a form to a site. It usually occurs alongside the ERR_CACHE_MISS error.
This warning’s purpose is to stop the Google Chrome browser from unintentionally duplicating information entered on a web form.
When visiting a website, your computer sends a DNS request to get the server’s IP address.
Sometimes, the website may have moved to another address, but the system still cached the old one. Since the browser can’t find the IP address of the domain you want to visit, it throws the ERR_NAME_NOT_RESOLVED error message.
Possible causes of this issue include problems with the DNS settings or cache, local network configurations, a flaw with the firewall system, and DNSSEC issues.
ERR_CONNECTION_REFUSED is a typical Google Chrome error that indicates a browser’s attempt to connect to a website is refused.
Usually, it is a client-side issue related to local network settings, browser extensions, synchronization, or third-party applications. In rare cases, it can be caused by server downtime.
This error also appears on other browsers. Microsoft Edge shows “Hmmm…can’t reach this page”. Meanwhile, Mozilla Firefox displays the “Unable to connect” message instead.
ERR_CONNECTION_RESET is a frequent Chrome error that occurs when the browser fails to connect with a target host. In this case, the server cannot process the request or send the data back to the browser.
Identifying the exact reason for this error message can be tricky. In most cases, the root issue lies with the client’s side, including incorrect Chrome settings, third-party software interference, outdated browser cache, network device problems, or bad proxy.
ERR_CONNECTION_CLOSED is a typical Chrome error that indicates the connection between the browser and the server is closed. Since the target host fails to process the request and send the data, the browser can’t load the website.
Before examining the server state, check your internet connection, disable the proxy server, reset Chrome settings, clear cache, use a different network, restart the internet router, deactivate the firewall system, and flush DNS.
If the above fixes don’t work, verify if the IP address is online, check the hosting resources, and contact your hosting’s support team.
We hope this article has helped you solve this Chrome error. Feel free to leave a comment if you have any questions or suggestions.