ERR! 418 I'm a teapot (this is not a joke) #20791
Comments
I'm getting the same error, started today. Using Azure:
command (using Azure PowerShell 2 extension): |
I'm having the same issue.
The server is running in Japan and using a proxy to connect to the npm registry and the web. |
Same here, started today. Error on my local machine (windows) and a VM (linux). |
I'm having same issue.
|
Having the same issue on our build server:
|
Running into the same issue here, running into problems on both local and build server |
Same issue here. I'm behind a corporate proxy too. SSHed into my home computer over my phone, and installs went through just fine. |
Ditto, npm config get registry npm -v node -v npm install |
Yep, same problem here. |
I know the Internet loves being cute, but this error is unhelpful. |
We're having this issue on AWS, behind a corporate proxy. Unfortunately we don't have the chance to go around this proxy.
|
Corporate proxy - no option to bypass
|
My colleague tried to run
log:
I also tried that in an older version of npm and node.
Does NOT the issue reproduce in older versions of npm? |
Yeah, rolling back to Node 4.26 works. 8 still doesn't. This is dumb. |
👍 Me too. For those looking for a workaround, yarn still seems to be healthy. |
I have started experiencing this issue from just today. I am behind an organisational firewall. $ npm install Other people in my team have no issues running the same npm code from their workstation. Only me is having the problem. |
The body of the 418 is
|
yes, we are meeting the same issue now. |
Me too, npm ERR! code E418 node -v npm -v I'm behind a proxy too. |
Same issue here. We have a successful install without a proxy and a 418 error code when installing from inside a container hooked up to the proxy. |
I'm gonna lock this for now, because I'm sure it's gonna get plenty of traffic. You really don't need to respond to repeat what every other poster is saying. The registry team has been informed. |
We've fixed this -- we now accept the port appended to the host. @wgrant's comment was most helpful, thank you! |
I'm opening this issue because:
all of the above.
What's going wrong?
This afternoon all servers in our AWS EU-Frankfurt environment started throwing the error regardless of what package we are trying to install
npm ERR! code E418 npm ERR! 418 I'm a teapot: commander@~2.3.0
It then locks up and does not exit the process.
How can the CLI team reproduce the problem?
npm install
There is nothing being written to the npm-debug.log as the process does not do anything
supporting information:
npm -v
prints:5.6.0
node -v
prints:8.9.0
npm config get registry
prints:http://registry.npmjs.org/
Windows, OS X/macOS, or Linux?:
Amazon Linux AMI release 2017.09
Network issues:
AWS - EU
Container:
No container.
The text was updated successfully, but these errors were encountered: