How to clear https proxy setting of NPM?

Question

How can I clear the previous ssl proxy setting of NPM? well, I search a lot, but all post I got is mainly about how to set proxy in corporate network.

I try to set proxy to nothing:

npm config set http-proxy
npm config set https-proxy

the first command pass yet the second one warn that:

npm WARN invalid config proxy=""
npm WARN invalid config Must be a full url with 'http://'

is the warning neglectable and I have successfully clear the proxy setting?

You can manually delete proxy settings from `/.npmrc` file – Salman Jan 20 '14 at 10:38 — Salman, Jan 20 '14 at 10:38

score 523 · Answer 1 · answered Jul 23 '14 at 12:18

523

None of the above helped me, but this did:

npm config rm proxy
npm config rm https-proxy

Source: http://jonathanblog2000.blogspot.ch/2013/11/set-and-reset-proxy-for-git-and-npm.html

answered Jul 23 '14 at 12:18

sra

6,338
3
20
17

Works on windows – Leon Africa Apr 02 '19 at 07:59
6

Can use `npm config list` to check the proxy config, maybe `npm config rm http-proxy` is needed, too – Tina Chen Aug 17 '19 at 09:42
@Anatolii has an answer for cleaning up **global** configuration settings below. The `rm` parameter doesn't work on old versions of `npm` for Windows -- see @Aaron's answer below. – dan Mar 10 '20 at 19:37

score 158 · Answer 2 · edited Apr 07 '16 at 09:15

158

Try deleting them with:

npm config delete proxy
npm config delete https-proxy

edited Apr 07 '16 at 09:15

dube

4,898
2
23
41

answered Jan 20 '14 at 18:19

Aaron

2,236
1
16
28

It outputs the same warning. – Allan Ruin Apr 11 '14 at 05:04
7

shouldn't it be npm config delete proxy? – Frank Fu Aug 15 '14 at 13:03
6

This work on windows. Try `npm config rm http-proxy` on linux – Sydwell Jun 14 '15 at 18:18

score 49 · Answer 3 · answered Feb 22 '15 at 18:19

49

npm config rm proxy
npm config rm https-proxy
unset HTTP_PROXY
unset HTTPS_PROXY
unset http_proxy
unset https_proxy

Damn finally this does the trick in Debian Jessie with privoxy (ad remover) installed, Thank you :-)

answered Feb 22 '15 at 18:19

privoxyd

491
4
2

This was the correct solution on OSX 10.11, tried everything else – Shooky Mar 24 '17 at 13:12
This solution works but doesn't seem to stick, after logout / reboot I had the same issue again. Can anyone explain where these variables are getting set? @privoxyd – Shooky Apr 06 '17 at 16:05

Anatolii Gabuza · Answer 4 · 2017-05-09T12:14:52.480

43

This was already answered but I think the --global config is not covered properly.

By running npm config rm proxy you remove proxy from user configuration.
This can be easily verified by running: npm config list.

If there is proxy or https-proxy setting set in global config you have to use --global in the command to remove it.

So at the end this will clean-up proxies from both local and global configs:

npm config rm proxy
npm config rm https-proxy
npm config --global rm proxy
npm config --global rm https-proxy

edited May 09 '17 at 12:14

answered Mar 17 '17 at 08:43

Anatolii Gabuza

6,184
2
36
54

2

This --global thing did the trick for me while just removing from the user configuration had no effect. Running on an old NPM version though. #thanksanatolii – Matti.b May 10 '19 at 07:42

score 31 · Answer 5 · answered Mar 24 '19 at 10:25

31

In the latest version npm rm proxy does not work. Instead use npm rm http-proxy

npm config rm proxy npm config rm https-proxy

answered Mar 24 '19 at 10:25

Oguz Ozcan

1,497
13
21

score 28 · Answer 6 · answered May 13 '14 at 23:05

28

By the default value npm is looking for packages from https://registry.npmjs.org. What you also need to do is override the registry and strict-ssl values.

npm config set registry "http://registry.npmjs.org"
npm config set strict-ssl false

answered May 13 '14 at 23:05

Michel Hua

1,614
2
23
44

This is a nice solution to overcome the whole issue of npm behind proxies. – markau Oct 29 '14 at 01:49
Thanks for this solution! – pramod singh Apr 11 '21 at 16:22

score 22 · Answer 7 · answered Jun 19 '18 at 11:55

22

I have used the below commands for removing any proxy set:

    npm config rm proxy
    npm config rm https-proxy

And it solved my problem :)

answered Jun 19 '18 at 11:55

Shagun Pruthi

1,813
15
19

nagu · Answer 8 · 2014-11-20T09:11:57.870

21

If you go through the npm config documentation, it says:

proxy

Default: HTTP_PROXY or http_proxy environment variable, or null

Type: url

As per this, to disable usage of proxy, proxy setting must be set to null. To set proxy value to null, one has to make sure that HTTP_PROXY or http_proxy environment variable is not set. So unset these environment variables and make sure that npm config ls -l shows proxy = null.

Also, it is important to note that:

Deleting http_proxy and https_proxy config settings alone will not help if you still have HTTP_PROXY or http_proxy environment variable is set to something and
Setting registry to use http:// and setting strict-ssl to false will not help you if you are not behind a proxy anyway and have HTTP_PROXY set to something.

It would have been better if npm had made the type of proxy setting to boolean to switch on/off the proxy usage. Or, they can introduce a new setting of sort use_proxy of type boolean.

edited Nov 20 '14 at 09:11

answered Nov 20 '14 at 08:33

nagu

877
10
17

3

This helped me, all the other suggestions (`delete` & `rm`) only remove `https-proxy` & `proxy` settings for your local npm config - **not** the default, by setting null it overrides these default settings – Wayne Austin Jan 09 '15 at 09:59
npm 3 does not honor `--proxy=null` anymore, does anyone know details? – C-Otto Jul 14 '16 at 10:37
3

To answer my own question, `--no-proxy` seems to work – C-Otto Sep 19 '16 at 07:33
@C-Otto Thank you so much for writing the only answer that worked after hours of banging my head! – Mustafa Alammar Oct 23 '16 at 04:22
@C-Otto Thank you so much. This is the only solution which worked for me. I tried hundreds of other solution but nothing worked. '--no-proxy' did the trick. But do you know why does it pick old proxy settings without '--no-proxy' option and from where? – Lokesh Jain Feb 14 '19 at 14:54

score 17 · Answer 9 · answered Jun 19 '17 at 14:56

17

there is a simple way of deleting or removing the npm proxies.

npm config delete proxy
npm config delete https-proxy

answered Jun 19 '17 at 14:56

hannad rehman

4,133
3
33
55

score 17 · Answer 10 · answered Nov 24 '17 at 14:04

I had the same problem once.
Follow these steps to delete proxy values:

1.To delete proxy in npm:
(-g is Important)
npm config delete proxy -g
npm config delete http-proxy -g
npm config delete https-proxy -g

Check the npm config file using:
npm config list

2.To delete system proxy: set HTTP_PROXY=null set HTTPS_PROXY=null

Now close the command line and open it to refresh the variables(proxy).

score 15 · Answer 11 · answered Apr 23 '17 at 13:26

15

Nothing above worked for me. I had to edit the file ".npmrc" which will be under user home directory (ex: c:\users\abcuser) :

http_proxy=null
registry=https://registry.npmjs.org/
strict-ssl=true
proxy=null

answered Apr 23 '17 at 13:26

velu

161
1
5

3

This Worked for me... To remove proxy we have to change registry as https://registry.npmjs.org/ and strict-ssl as true – Vicky May 15 '17 at 11:27
I am trying this out to see if my project specific .npmrc setting for proxy will override any global settings in the user's home dir which clobber us in a shared build environment. – httpete Aug 28 '19 at 15:35
I updated my project .nprmc file. It did not work – Rohit Singh Oct 12 '21 at 16:23

score 14 · Answer 12 · answered Jul 17 '16 at 07:18

14

This works

npm config delete http-proxy
npm config delete https-proxy

npm config rm proxy
npm config rm https-proxy

set HTTP_PROXY=null
set HTTPS_PROXY=null

answered Jul 17 '16 at 07:18

venkat7668

2,657
1
22
26

score 13 · Answer 13 · answered Oct 26 '15 at 14:39

13

Running npm version 2.10.1 in windows 7, I used:

npm config delete proxy
npm config delete https-proxy

answered Oct 26 '15 at 14:39

James Drinkard

15,342
16
114
137

score 11 · Answer 14 · answered Mar 25 '20 at 05:24

11

Try This,

npm config delete http-proxy

npm config delete https-proxy

npm config rm proxy

npm config rm https-proxy

set HTTP_PROXY=null

set HTTPS_PROXY=null

answered Mar 25 '20 at 05:24

Shehara Jayashan

111
1
2

If you're using bash (Linux, or Window Git bash), try `export HTTP_PROXY=` and `export HTTPS_PROXY=` rather than `set ...=null` – cmousset Jul 19 '21 at 17:15

Seun S. Lawal · Answer 15 · 2017-02-10T20:48:19.373

The easiest way to remove any configuration at all from npm is to edit the npm config file. It only takes two(2) commands to do this; one to open npm config file for editing, the other to confirm your change.

type npm config list to view a list of all npm configurations that are active.
type npm config edit to open a text editor with npm configurations. To remove the proxy line ( or simply comment it out ).
Save the config file and close it.
type npm config list to confirm that the proxy configuration has been removed.

C'est la vie!

I tried everything listed on this page, none worked, then I tried to the config edit. It worked instantly. (I use Windows 10)

@Madhan it is the Swiss Army knife for npm configuration – Seun S. Lawal Apr 01 '17 at 06:59 — Seun S. Lawal, Apr 01 '17 at 06:59

score 8 · Answer 16 · edited Oct 06 '15 at 18:56

8

npm config delete proxy -g

worked for me.

-g was important as initially it was set with that option. You can check configurations set with :

npm config list

edited Oct 06 '15 at 18:56

spenibus

4,339
11
26
35

answered Sep 26 '15 at 03:29

Amit Teli

875
11
25

npm write config also on ./etc – venergiac Nov 26 '16 at 08:06

score 6 · Answer 17 · edited Aug 24 '15 at 05:47

6

npm config rm proxy
npm config rm https-proxy

Worked for me

edited Aug 24 '15 at 05:47

ketan

19,129
42
60
98

answered Aug 24 '15 at 05:15

moukhan

69
1
3

score 5 · Answer 18 · answered Apr 09 '14 at 19:52

5

I think it's not http-proxy but proxy:

npm config set proxy="http://yourproxyhere"

answered Apr 09 '14 at 19:52

Ziggurat

257
1
4
8

It always showed `npm ERR! If you are behind a proxy, please make sure that the` `npm ERR! 'proxy' config is set properly. See: 'npm help config'` None of the other options worked. This one worked best. – Shiyaz Jul 15 '15 at 09:33

score 3 · Answer 19 · answered Apr 11 '14 at 02:28

3

Got exactly the same problem, I keep seeing my proxy configuration even after removing the npmrc file and deleting the keys.

I found out that npm were using windows env key http-proxy by default.

So go in Computer->Properties->Advanced system settings->Environement variables and check there is no http-proxy key configured.

answered Apr 11 '14 at 02:28

Cyril

741
1
6
16

Interesting, I checked the environment variables and I don't have things like `http-proxy`. Maybe the warning is really neglectable. – Allan Ruin Apr 11 '14 at 05:06

score 3 · Answer 20 · answered Jun 11 '14 at 13:40

In my case (Linux Mint 16 based on Ubuntu), I had to:

npm config delete https-proxy, and also
clear the https_proxy Bash environment parameter — oddly enough, although I cannot find this behavior documented anywhere, npm fallbacks to https_proxy:
```
$ http_proxy='' https_proxy='' npm config get https-proxy
null
$ http_proxy='' xxhttps_proxy='' npm config get https-proxy
https://1.2.3.4:8080
```

score 3 · Answer 21 · answered Feb 05 '16 at 15:51

3

See the npm Settings in file C:\Users\myusers.npmrc file. Sometime the npm proxy config settings does not apply. so its worth checking in there.

answered Feb 05 '16 at 15:51

Hari Gillala

11,736
18
70
117

score 3 · Answer 22 · answered Nov 26 '16 at 08:09

3

npm config delete http-proxy
npm config delete https-proxy

npm config delete proxy -g
npm config delete http-proxy -g

then

npm config get proxy

null

also

npm i -g bower to update

npm had a bug on the proxy

answered Nov 26 '16 at 08:09

venergiac

7,469
2
48
70

score 3 · Answer 23 · edited Jan 23 '20 at 13:31

3

If you want to switch between proxy for company network and remove proxy for home/personal network you can use --no-proxy

Sample usage:

npm install --save-dev "@angular/animations@8.2.14" --no-proxy

edited Jan 23 '20 at 13:31

pix

1,264
19
32

answered Jan 23 '20 at 12:41

Anand

51
4

score 2 · Answer 24 · answered Aug 21 '18 at 07:04

2

execute npm config list it will list down all proxy values.. in my case proxy value was fetched form global npmrc file, removed it and was able to complete npm install on my windows machine

answered Aug 21 '18 at 07:04

Ankur Dhawan

21
2

I removed proxy in Global .nprmc . I started getting 407 Error. I was behind corporate proxy – Rohit Singh Oct 12 '21 at 18:26

score 2 · Answer 25 · answered Feb 25 '19 at 18:51

Well, I'm gonna leave this here because I was having a big trouble with NPM.

I was trying to change a proxy setting using npm config set proxy "http://.../" and then running npm config get proxy. It was ALWAYS returning a wrong value, different from the one that I'd set.

I found out that I had a .npmrc COMMITED on the project I was trying to run npm install and that this file was overriding my own config.

So it was cleaning the proxy value, but I needed to also change the .npmrc inside the folder's project.

After that, everything worked fine.

score 1 · Answer 26 · answered Jul 13 '16 at 23:00

1

I've used

npm config set proxy null
npm config set https-proxy null

and it worked for me.

Best regards

answered Jul 13 '16 at 23:00

Dirceu Henrique

39
6

score 1 · Answer 27 · answered Jan 19 '17 at 11:25

1

this works for me fime

proxy=http://<username>:<pass>@proxyhost:<port>

https-proxy=http://<uname>:<pass>@proxyhost:<port>

sample in my instance username:uname and password:pword

npm config set proxy=http://uname:pword@192.168.5.8:8080

npm config set https-proxy=http://uname:pword@192.168.5.8:8080

answered Jan 19 '17 at 11:25

Ravinath

1,620
1
14
8

This is setting, we are looking for clear which is exact opposite – Satish Patro May 02 '19 at 08:36

score 1 · Answer 28 · answered Sep 27 '18 at 14:56

I was struggling with this for ages. What I finally did was go into the .npmrc file (which can be found in the user's directory followed by the user's name, ie. C:\Users\erikj/.npmrc), opened it with a text editor, manually removed any proxy settings and changed the http:// setting to https://. In this case, it is a matter of experimenting whether http or https will work for you. In my case, https worked. Go figure.

Lautaro Mascitti · Answer 29 · 2020-03-20T21:18:43.583

1

In my case, (windows OS), after put all those commands listed, npm kept taking the proxy in the setting of windows registry

\ HKEY_CURRENT_USER \ Environment

just remove the proxy settings there, after that, I restarted the pc and then "npm install" worked for me

Example

edited Mar 20 '20 at 21:18

answered Mar 20 '20 at 20:41

Lautaro Mascitti

311
2
4

score 0 · Answer 30 · edited Feb 24 '19 at 18:07

0

Http Module is deprecated and it is replaced with HttpClient.

Change your imports to import { HttpClientModule } from '@angular/common/http';

edited Feb 24 '19 at 18:07

Rishabh Agarwal

1,988
1
16
33

answered Feb 24 '19 at 15:00

Santy

1

score 0 · Answer 31 · answered Sep 28 '21 at 01:34

0

Here is my solution: Step 1:

env |grep proxy e.g,I got: http_proxy https_proxy

Step2: unset the proxy variables

unset http_proxy unset https_proxy

Then npm install works ok now

answered Sep 28 '21 at 01:34

Cheung Riche

71
1
4

score 0 · Answer 32 · answered Feb 26 '22 at 12:57

0

this will clean-up proxies from both local and global configs without --global it will clear only from the current user profile:

npm config rm proxy npm config rm https-proxy npm config --global rm proxy npm config --global rm https-proxy

answered Feb 26 '22 at 12:57

Leon1246

13
3

score 0 · Answer 33 · edited Jan 30 '23 at 18:42

0

You can delete the proxy and https-proxy manually from the .npmrc file

edited Jan 30 '23 at 18:42

Tyler2P

2,324
26
22
31

answered Jan 29 '23 at 10:36

Ali Nasir

1

score -1 · Answer 34 · answered Jul 07 '15 at 22:05

You will get the proxy host and port from your server administrator or support.

After that set up

npm config set http_proxy http://username:password@proxyofmycomp.com:itsport npm config set proxy http://username:password@proxyofmycomp.com:itsport If there any special character in password try with % urlencode. Eg:- pound(hash) shuold be replaced by %23.

This worked for me...

score -1 · Answer 35 · answered Oct 06 '15 at 18:49

-1

ok, "NPM config delete ..." is the right command for Windows environment, viceversa "NPM config rm ..." it is for Unix-like environment. Moreover, at least for me, it was mandatory to add the option "-g" because the command worked properly

answered Oct 06 '15 at 18:49

rappo

1

How to clear https proxy setting of NPM?

35 Answers35

Linked