For example, if your password is: then it will be like Welcome%4012%23.Īdditionally, with your username, you may need to also include the domain name + username aswell.įor example, lets say we work at a company with domain BIGCORP and your username is johnnyweekend with password then your NPM proxy config might look something like this: Npm config set proxy config set https-proxy in mind that when you are using username and password, they need to be encoded. Now if your proxy requires authentication, we can do the following formats: Npm config set proxy You can replace the proxyurl and port with your company’s proxy url and port. The following commands will set your proxy settings. We are removing both the proxy config value and the https-proxy values.

Npm config set proxy To verify that you have the right proxy settings we can do the following steps: Remove current proxy settingsįirstly, use the commands to remove your current proxy settings ( rm) Typically, whenever I see a npm or node issue, the first step to have a look at is checking your current npm and node versions and updating if required.įirstly, open up the terminal and run the following commands to check npm and your node versions: Upgrade to the latest node and npm versions Use yarn to install packages instead of npm.Update request timeout settings npm config set fetch-timeout.

Verify to use the https version of npm registry url.

Check that you have internet connectivity.

Upgrade to the latest node and npm versions.

To fix this error ERR_SOCKET_TIMEOUT, we can try some of the following actions: Npm ERR! network 'proxy' config is set properly. Npm ERR! network If you are behind a proxy, please make sure that the Npm ERR! network In most cases you are behind a proxy or have bad network settings. Npm ERR! network This is a problem related to network connectivity.

Npm config set loglevel http