Hoping this is the right place to ask this. I'm trying to learn React Native and I'm using Expo as my medium for deployment, but I'm finding that I'm literally getting 20 minutes at a time before my browser fails to connect with the error code ERR_CONNECTION_FAILED. I've tried the following:
netsh winsock reset
, then the related ipconfig
commands for flushing DNS settingsI'm at my wits end as the only thing that completely solves it is restarting my laptop, which for obvious reasons isn't feasible every 20 minutes, so I'm hoping somebody can help.
rebooting the computer. resetting Chrome (deleting all Content & Cookies; restoring all default browser settings) launching Chrome with no extensions, as well as in incognito mode. disabling all extensions manually.
This error code problem indicates that the attempt to connect to the server failed. This Webpage is not Available ERR_CONNECTION_FAILED Chrome is the most common error which users get when browsing the internet.
The timed-out error is usually due to no communication between your browser and the website you are trying to access. This is because either your browser cannot receive the data or the time it took crossed the timeout session and couldn't establish a connection.
The ERR_CONNECTION_CLOSED message is an error that you might see in Chrome when you try to access a website. It means that something's going wrong with your device's connection that's preventing Chrome from successfully connecting to the website's server.
I'm experiencing the same issue with Expo in this environment:
These links were useful to learn why this is happening:
In essence, this issue seems to be due to a problem with WSL. Per a post in the first link, I tried the alternative to restarting the computer and it worked - it made the ERR_CONNECTION_FAILED problems disappear...for 20 minutes. That alternative is as follows:
This restarts the WSL service which also means that the WSL instance that was running gets terminated. This is less than ideal, but at least a computer restart is avoided. The third link says this WSL problem is fixed in Windows Insider Build 18890.
I am now considering spinning up a VM to run Ubuntu instead of trying to use WSL for Expo projects.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With