You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading to node version 22, it seems the proxy configuration is not working anymore.
We are behind a corporate proxy, so we use local proxy servers to install node packages; we tried with fiddler, px and others, but the result is the same.
We tried with the previous LTS (node 20) and everything worked as expected; the same goes for node 21.
When we upgraded to node 22, when we tried to install packages we got an ECONNREFUSED issue. We tried also with node 23, but we got the same issue.
We also checked the documentation and internal changelogs, but it seems to be no reference to changes that may have affected the proxy configuration.
Im having similar issue after upgrading from 22.11.0 to 22.12.0
I have a scenario with angular + net 9 backend + httponlycookies authentication. I have implemented this proxy to be able to test locally while debugging (localhost:4200 for angular and localhost:60112 for backend)
I just downgraded to 22.11.0 and it works fine and proxied to localhost:60112 (my backend only accepts localhost, and not 127.0.0.1)
In 22.12.0, it is always translated to 127.0.0.1 regardless of the localhost configuration.
Node.js Version
v22.12.0
NPM Version
10.9.0
Operating System
Microsoft Windows 10 Pro
Subsystem
Other
Description
After upgrading to node version 22, it seems the proxy configuration is not working anymore.
We are behind a corporate proxy, so we use local proxy servers to install node packages; we tried with fiddler, px and others, but the result is the same.
This is our configuration:
We tried with the previous LTS (node 20) and everything worked as expected; the same goes for node 21.
When we upgraded to node 22, when we tried to install packages we got an ECONNREFUSED issue. We tried also with node 23, but we got the same issue.
We also checked the documentation and internal changelogs, but it seems to be no reference to changes that may have affected the proxy configuration.
Are we missing some configuration or similar?
Thanks.
Minimal Reproduction
You should get an ECONNREFUSED issue
Output
npm http fetch GET [INTERNAL_REGISTRY] attempt 1 failed with ECONNREFUSED
Before You Submit
The text was updated successfully, but these errors were encountered: