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

[id77]

➜  fuc git:(master) yarn install
yarn install v1.3.2
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
error An unexpected error occurred: "http://npm.byted.org/debug/-/debug-2.6.9.tgz: getaddrinfo ENOTFOUND npm.byted.org npm.byted.org:80".
info If you think this is a bug, please open a bug report with the information provided in "/Users/Jimmy/reactjs/react-native/fuc/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
➜  fuc git:(master) ✗

I cloned a project and I looked at the value of yarn.lock, package key 'resolved', which starts with 'http://npm.byted.org'.

I think this is the author custom yarn registry, but I can not visit 'http://npm.byted.org', but yarn config did not fix it.

[torifat]

What do you mean by "but yarn config did not fix it"? What did you try?

[id77]

expected:
If 'yarn.lock resolved' is unreachable, can I ignore 'resolved' in yarn.lock and install it using 'yarn config registry'.

doubt:
Or recommend me delete the lock file?

Sorry, forgive me, my English is not good.

[torifat]

Sorry, forgive me, my English is not good.

It's not a problem as long as I can understand. And, I'm also not very good either 😄

It's not a bug. This is an expected behavior. You can either delete yarn.lock file and yarn install again. Or, if you need the exact packages then you can replace http://npm.byted.org with https://registry.yarnpkg.com in yarn.lock file.

[marcelhageman]

Adding this comment for other Googlers: What worked for me was increasing the Yarn network timeout:

yarn add YourPackageHere --network-timeout 100000

Apparently the package I was installing was too large (or my network too slow) so it assumed it was a network problem. It might've been, but this solved it. Just took a while.

[AnthonyLamot]

I'm experiencing this issue now as well. None of the aforementioned solutions seem to be working. Internet still works fine though, and no one else in the co-working space where I'm at seem to be experiencing any network issues?

[sandinosaso]

yarn install --network-timeout 1000000
Did the trick for me:

⇒  yarn install --network-timeout 1000000
yarn install v1.3.2
[1/4] 🔍  Resolving packages...
warning react-native > connect@2.30.2: connect 2.x series is deprecated
warning react-native > fbjs-scripts > gulp-util@3.0.8: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning "jest-expo > babel-jest@21.2.0" has unmet peer dependency "babel-core@^6.0.0 || ^7.0.0-alpha || ^7.0.0-beta || ^7.0.0".
[4/4] 📃  Building fresh packages...
success Saved lockfile.
✨  Done in 234.36s.

[AnthonyLamot]

Figured out was wrong. One of my dependencies (react-native itself) had the wrong value and it got stuck there. Took me a while to realize because it did not show in the error report but only while the yarn command was running would it pop up for a moment.

…

On Jan 17, 2018 10:54, "Sandino" ***@***.***> wrote: yarn install --network-timeout 1000000 Did the trick for me: ⇒ yarn install --network-timeout 1000000 yarn install v1.3.2 [1/4] 🔍 Resolving packages... warning react-native > ***@***.***: connect 2.x series is deprecated warning react-native > fbjs-scripts > ***@***.***: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5 [2/4 <https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5%5B2/4>] 🚚 Fetching packages... [3/4] 🔗 Linking dependencies... warning "jest-expo > ***@***.***" has unmet peer dependency "babel-core@^6.0.0 || ^7.0.0-alpha || ^7.0.0-beta || ^7.0.0". [4/4] 📃 Building fresh packages... success Saved lockfile. ✨ Done in 234.36s. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#4890 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJeQ6UFZ6q3OqEIdUXRZKUsuoMFkbJtJks5tLWDzgaJpZM4QXTQJ> .

[JochenFromm]

Same problem here, increasing the network timeout solved it

yarn install --network-timeout 1000000

Maybe the default timeout is too small?

[HarshulSharma000]

I am facing the same issue on Windows and setting timeout does not resolve it. On the other hand npm works fine.

[anujthakwani]

Task :wherehows-web:yarn
yarn install v1.3.2
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
error An unexpected error occurred: "https://registry.yarnpkg.com/babel-polyfill/-/babel-polyfill-6.26.0.tgz: ESOCKETTIMEDOUT".
info If you think this is a bug, please open a bug report with the information provided in "/Users/athakwani/Desktop/WhereHows/wherehows-web/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

FAILURE: Build failed with an exception.

Any help here ?

[jensbodal]

Don't have a solution or why there was network issues in the first place, but the default for NETWORK_TIMEOUT is 30 seconds. Note that network-timeout is in ms, I probably wouldn't set this to higher than 5 minutes otherwise your build will just sit there for ~16 minutes (1000000ms) is there truly is network connectivity issues.

https://github.com/yarnpkg/yarn/search?utf8=%E2%9C%93&q=NETWORK_TIMEOUT&type=

[marcelorl]

@HarshulSharma000 same issue