Yarn - There appears to be trouble with your network connection. Retrying

I have been trying to do the quickstart guide for react native, but kept getting this error

There appears to be trouble with your network connection. Retrying...

My connection works just fine.

This happens when your network is too slow or the package being installed is too large, and Yarn just assumes it's a network problem. Try increasing Yarn network timeout:

yarn add <yourPackage> --network-timeout 100000

Deleting the yarn.lock file and rerunning "yarn install" worked for me.

I got this issue because I was working within my company internal network and proxy needed to be set.

$ yarn config set proxy http://my_company_proxy_url:port
$ yarn config set https-proxy http://localhost:3128

example $ yarn config set https-proxy http://proxy.abc.com:8080

Simple working solution (right way of doing it):

Looks like yarn was trying to connect via a proxy. The following worked for me:

npm config rm proxy
npm config rm https-proxy

Source: https://github.com/yarnpkg/yarn/issues/4890

Turning off "real time protection" with windows defender fixed it for me.

Sucks but it appears the checks are too much for yarn to handle.

1. Could be that your network speed is too slow and timeout is relatively short, you can set yarn install --network-timeout=30000
2. If you still have the error, could be solved by proxy, vim ~/.yarnrc and add useful proxy setting.

Could be a proxy issue. Run the command below to delete the proxy.

yarn config delete proxy

yarn config set network-timeout 600000 -g

Often, your error is caused by hitting the network connection time limit, and yarn simply reports there is "trouble with your network connection".

The line of code at the top of my answer sets the global yarn network timeout to 10 minutes.

Having a long network timeout is probably okay, because yarn uses caches and if it's big and you don't have it, you probably want it to just go ahead and take the time to download.

The following helped me

yarn config delete https-proxy
yarn config delete proxy

they set your https-proxy and proxy values to undefined. My https-proxy was set to localhost. Check that proxy and https-proxy config values are undefined by using the following

yarn config get https-proxy
yarn config get proxy

The large package involved often can be Material Design Icons.

Check if you make use of the Material Design Fonts material-design-icons in your package.json and remove it!

material-design-icons is too big to handle and you should only use material-design-icons-fonts if you only need them.

https://medium.com/@henkjan_47362/just-a-short-notice-for-whomever-is-searching-for-hours-like-i-did-a741d0cd167b

When I want to use yarn I have above error, but there is not any error with npm, for this situation you can install react project from npm

npx create-react-app app --use-npm

Deleting the yarn-lock file, doing a yarn cache clean and then a yarn solved my issue

Turn off or disable your antivirus before run this command. I am also facing same issue than i disable quick heal antivirus and it is works.

create-react-app my-app

In short, this is caused when yarn is having network problems and is unable to reach the registry. This can be for any number of reasons, but in all cases, the error is the same, so you might need to try a bunch of different solutions.

Reason 1: Outdated Proxy Settings

This will throw the "network connection" error if you are connected to a network that uses a proxy and you did not update yarn configs with the correct proxy setting.

You can start running the below commands to check what the current proxy configs are set to:

yarn config get https-proxy
yarn config get proxy

If the proxy URLs returned are not what you expect, you just need to run the following commands to set the correct ones:

yarn config set https-proxy <proxy-url>
yarn config set proxy <proxy-url>

Similarly, if you have previously set up the proxy on yarn but are no longer using a network connection that needs a proxy. In this case, you just need to do the opposite and delete the proxy config:

yarn config delete https-proxy
yarn config delete proxy

Reason 2: Incorrect Domain name resolution

This will throw the "network connection" error if for whatever reason your machine cannot resolve your yarn registry URL to the correct IP-address. This would usually only happen if you (or your organization) are using an in-house package registry and the ip-address to the registry changes.

In this case, the issue is not with yarn but rather with your machine. You can solve this by updating your hosts file (for mac users, this should be found in '/etc/hosts') with the correct values, by adding a mapping as follows:

<ip-address> <registry-base-url>

example:

10.0.0.1 artifactory.my.fancy.organiza.co.za

npm install 

worked for me (but my project was built with yarn)

I encountered this error while attempting yarn outdated. In my case, a few of the packages in my project were hosted in a private registry within the company network. I didn't realize my VPN was disconnected so it was initially confusing to see the error message whilst I was still able to browse the web.

It becomes quite obvious for those patient enough to wait out all five retry attempts. I, however, ctrl-c'd after three attempts... 

In my case I found a reference to a defunct registry in my ~/.yarnrc file

When I removed that the error went away

This happened in my case trying to run yarn install.

My project is a set of many sub-projects. After a couple of retries, it showed a socket-timeout error log:

error An unexpected error occurred: "https://<myregitry>/directory/-/subProject1-1.0.2.tgz: ESOCKETTIMEDOUT".

I cloned subProject1 separately, did yarn install on it and linked it with main project.

I was able to continue with my command on main project after that. Once done, I unlinked the subProject1 and did a final yarn install --force which was success.

I got this error while trying to run yarn install - i use WSL with ubuntu distro, the following command fixed it,

echo "nameserver 8.8.8.8" | sudo tee /etc/resolv.conf > /dev/null

If you are working within a docker environment or elsewhere that might need a different approach where you are not modifying the installation process, try adding a file named .yarnrc in the root of the project with the problem (where your package.json resides) and in that file write:

network-timeout 600000

Docker will still run without modifying the docker-compose.yml file and you get the timeout solution.

This may be a late answer but here are some possible reasons:

• If you are behind a proxy you may need to configure .npmrc if you are using npm or .yarnrc if you are using yarn
• If proxy is well setup, you may need remove yarn.lock or package-lock.json and re-run npm i or yarn

Adding option --network=host was the solution in my case.

> docker build --network=host --progress=plain .