CODEWITHSUNDEEP
reactjstimeoutpackageyarnpkg
dragi
dragi

Reputation: 1512

yarn is having troubles with the network connection

I tried to install a package with yarn earlier today and I got this

yarn install
yarn install v1.9.4
[1/4] 🔍  Resolving 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/eslint: getaddrinfo ENOTFOUND     registry.yarnpkg.com registry.yarnpkg.com:443".
info If you think this is a bug, please open a bug report with the information provided in "/Users/daviddragovacz/Documents/GitHub/react-    project-one/dragi/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

does anybody know how to fix this? My network seems to be okay, not slow at all.

It happens with every package I tried.

package.json 

{
    "name": "dragi",
    "version": "0.1.0",
    "private": true,
    "dependencies": {
        "axios": "^0.18.0",
        "prop-types": "^15.6.2",
        "react": "^16.4.2",
        "react-dom": "^16.4.2",
        "react-redux": "^5.0.7",
        "react-router": "^4.3.1",
        "react-router-dom": "^4.3.1",
        "react-scripts": "1.1.5",
        "redux": "^4.0.0",
        "redux-devtools-extension": "^2.13.5",
        "redux-thunk": "^2.3.0",
        "semantic-ui-css": "^2.3.3",
        "semantic-ui-react": "^0.82.3",
        "validator": "^10.7.0"
    },
    "scripts": {
        "start": "react-scripts start",
        "build": "react-scripts build",
        "test": "react-scripts test --env=jsdom",
        "eject": "react-scripts eject",
        "lint": "eslint src"
    },
    "devDependencies": {
        "eslint": "^5.5.0",
        "eslint-config-airbnb": "^17.1.0",
        "eslint-config-prettier": "^3.0.1",
        "eslint-plugin-import": "^2.14.0",
        "eslint-plugin-jsx-a11y": "^6.1.1",
        "eslint-plugin-prettier": "^2.6.2",
        "eslint-plugin-react": "^7.11.1",
        "prettier": "^1.14.2"
    },
    "proxy": "http://localhost:8080"
}

Also a quick note: npm i works fine - only yarn is having issues

Upvotes: 48

Views: 109344

Answers (19)

Yogesh
Yogesh

Reputation: 801

Even I was facing this issue, but in my case it was permission issue, thus I resolved it using

sudo yarn install

Upvotes: -2

pawanzZ
pawanzZ

Reputation: 59

On a Mac, I've tried cleaning cache, reinstalling VSCode. Nothing worked for me and I'm not connected to any VPN.

Connecting to a VPN solved the problem.

Upvotes: 0

Andrés Fernández
Andrés Fernández

Reputation: 3043

Had the same issue in Ubuntu, the solution was to disable IPv6 from network settings but also to edit the etc/hosts file, as mentioned in this Reddit post. I went with the former.

Upvotes: 0

Luci Furtun
Luci Furtun

Reputation: 179

I had this timeout issue and the problem for me was that the image was built from an M2 MacBook. The fix was to add the --platform linux/amd64 param to the docker build command: docker build --platform linux/amd64

Upvotes: 0

Yogesh Devgun
Yogesh Devgun

Reputation: 1577

I had the same network retrying issue when I used yarn install, simply using yarn worked for me or increase the timeout.

Upvotes: 0

Eduardo Ramos
Eduardo Ramos

Reputation: 534

Tired reinstall/install yarn but, not works, for me the problem was with the nvm cache:

nvm cache clear

After cleaning it solved the issue.

Upvotes: -1

Avinash Kesari
Avinash Kesari

Reputation: 181

I had the same issue and solved by following steps:

Run the terminal command

  1. clean npm cache
  2. npm cache clean --force
  3. set http_proxy=
  4. Set https_proxy=
  5. yarn config delete proxy
  6. npm config rm https-proxy
  7. npm config rm proxy
  8. Restart your terminal
  9. yarn
  10. yarn –network-timeout 100000

Restart your terminal.

it worked for me. #HappyCoding

Upvotes: 9

Osama Rashid
Osama Rashid

Reputation: 1019

here's what worked for me:

brew reinstall node

brew reinstall yarn

npm cache clean --force
 && yarn cache clean
 && yarn config delete proxy
 && yarn config delete https-proxy
 && yarn config delete registry

then RESTART immediately.

Upvotes: 2

Ridox
Ridox

Reputation: 1389

proxy in bash env caused my same problem.

after running cmd unset HTTP_PROXY HTTPS_PROXY ALL_PROXY, fixed this problem.

Upvotes: 2

Binita Bharati
Binita Bharati

Reputation: 5908

In my case, there was a hidden file .npmrc that had the registry pointed to a location in another private network, which my network did not have access to. Once, I commented out the private network related entries in this file, yarn install started working. Also, yarn-error.log was generated, that had this information.

Upvotes: 1

zangbianxuegu
zangbianxuegu

Reputation: 155

I have tried a lot:

  • npm clean cache
  • yarn clean cache
  • yarn config delete proxy
  • yarn config delete https-proxy
  • yarn config delete registry
  • yarn install --network-timeout 1000000

finally it works!

Upvotes: 1

Radosław Andraszyk
Radosław Andraszyk

Reputation: 460

If you are using WSL for linux just add the current ip domain in: C:\Windows\System32\drivers\etc\hosts e.g:

104.16.21.35    registry.yarnpkg.com

Upvotes: 5

Isaac Pak
Isaac Pak

Reputation: 4971

It may be the library was originally using npm instead of yarn. In my case I had to install everything with npm instead of yarn. I removed the yarn.lock file and then: 

npm install

Upvotes: 2

jfa
jfa

Reputation: 1101

I got this as well.

I ran yarn install --no-lockfile and it worked, so I deleted the node modules again and deleted yarn.lock. It looks like a bug in yarn, because yarn wasn't having issues in previous versions of my application.

Upvotes: 1

PolarisTLX
PolarisTLX

Reputation: 349

Check your internet speed / strength of connection. I had this problem while I was on a spotty public wifi. Noticed that it was a different package that threw the error each time I tried. And once I got faster / more stable internet this problem went away. (The packages were too large for my poor connection).

Upvotes: 1

matcha
matcha

Reputation: 81

i had a different error, but the same network connection issue. i read through this thread: https://github.com/yarnpkg/yarn/issues/15

and ended up uninstalling/reinstalling node/npm which fixed my issue. maybe there's something wrong with your node installation too?

Upvotes: 3

Jackie
Jackie

Reputation: 25989

retrying few times worked out for me on similar issue.

Upvotes: 0

Adeel Imran
Adeel Imran

Reputation: 13976

Try clearing your cache

$ yarn cache clean
$ yarn // to install dependencies, no need for "yarn install"

Approach 2

$ yarn install --network-timeout 1000000

Reference https://github.com/yarnpkg/yarn/issues/4890#issuecomment-358179301

Upvotes: 74

ramki
ramki

Reputation: 481

Try increasing network timeout

yarn install --network-timeout 1000000

found this on GitHub issues https://github.com/yarnpkg/yarn/issues/4890

Upvotes: 17

Related Questions