Skip to content
This repository has been archived by the owner. It is now read-only.

ERR! 418 I'm a teapot (this is not a joke) #20791

Closed
4 of 6 tasks
colebowl opened this issue May 28, 2018 · 22 comments
Closed
4 of 6 tasks

ERR! 418 I'm a teapot (this is not a joke) #20791

colebowl opened this issue May 28, 2018 · 22 comments

Comments

@colebowl
Copy link

@colebowl colebowl commented May 28, 2018

I'm opening this issue because:

  • npm is crashing.
  • npm is producing an incorrect install.
  • npm is doing something I don't understand.
  • npm is producing incorrect or undesirable behavior.

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:

    • Geographic location where npm was run:
      AWS - EU
    • [x ] I use a proxy to connect to the npm registry.
    • [x ] I use a proxy to connect to the web.
    • [x ] I use a proxy when downloading Git repos.
    • I access the npm registry via a VPN
    • I don't use a proxy, but have limited or unreliable internet access.
  • Container:
    No container.

@tolgabalci
Copy link

@tolgabalci tolgabalci commented May 29, 2018

I'm getting the same error, started today. Using Azure:

2018-05-28T23:54:24.4436370Z npm ERR! code E418
2018-05-28T23:54:24.4481896Z npm ERR! 418 I'm a teapot: @angular/cli@^1.6.5

command (using Azure PowerShell 2 extension):
npm install @angular/cli

@moriyas1984
Copy link

@moriyas1984 moriyas1984 commented May 29, 2018

I'm having the same issue.

$ npm install --save-dev express
npm ERR! code E418
npm ERR! 418 I'm a teapot: express@^4.16.3

$ npm -v
5.6.0

$ node -v
v8.11.2

$ npm config get registry
http://registry.npmjs.org/

$ $ cat /etc/os-release
NAME="Ubuntu"
VERSION="16.04.4 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.4 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

The server is running in Japan and using a proxy to connect to the npm registry and the web.

@AlpacaMyLunch
Copy link

@AlpacaMyLunch AlpacaMyLunch commented May 29, 2018

Same here, started today. Error on my local machine (windows) and a VM (linux).

@HenkWillcock
Copy link

@HenkWillcock HenkWillcock commented May 29, 2018

I'm having same issue.

citron: [Application] % npm install
npm ERR! code E418
npm ERR! 418 I'm a teapot: ember-test-selectors@^1.0.0

@roshan092
Copy link

@roshan092 roshan092 commented May 29, 2018

Having the same issue on our build server:

29-May-2018 10:07:56 | npm ERR! code E418 29-May-2018 10:07:56 | npm ERR! 418 I'm a teapot: source-map@0.5.7

@mattcreta
Copy link

@mattcreta mattcreta commented May 29, 2018

Running into the same issue here, running into problems on both local and build server
npm ERR! 418 I'm a teapot: express@^4.15.3

@brandonpittman
Copy link

@brandonpittman brandonpittman commented May 29, 2018

Same issue here.

I'm behind a corporate proxy too. SSHed into my home computer over my phone, and installs went through just fine.

@happyrobotstudio
Copy link

@happyrobotstudio happyrobotstudio commented May 29, 2018

Ditto,

npm config get registry
https://registry.npmjs.org/

npm -v
5.6.0

node -v
v8.9.4

npm install
npm ERR! code E418

@TomLingham
Copy link

@TomLingham TomLingham commented May 29, 2018

Yep, same problem here. npm install <package> returns 418 I'm a Teapot, and install stalls.
Related: https://github.com/npm/registry/issues/335

@brandonpittman
Copy link

@brandonpittman brandonpittman commented May 29, 2018

I know the Internet loves being cute, but this error is unhelpful.

@EmandM
Copy link

@EmandM EmandM commented May 29, 2018

We're having this issue on AWS, behind a corporate proxy. Unfortunately we don't have the chance to go around this proxy.

$ npm install
npm ERR! code E418
npm ERR! 418 I'm a teapot

$ npm -v
5.3.0

$ node -v
v8.4.0

@AlpacaMyLunch
Copy link

@AlpacaMyLunch AlpacaMyLunch commented May 29, 2018

Corporate proxy - no option to bypass

$ npm - v
5.6.0
$node -v
v9.6.1

@moriyas1984
Copy link

@moriyas1984 moriyas1984 commented May 29, 2018

My colleague tried to run npm install and he was succeeded.
His environment:

$ npm -v
3.5.2
$ node -v
v4.2.6
$ npm config get registry
https://registry.npmjs.org/

log:

$ npm install express
/home/username
tqq express@4.16.3
tqq thomash-node-audio-metadata@1.0.1  (git://github.com/osyo-manga/thomash-node-audio-metadata.git#c8af2b43ef97b2753f2ba712e828e0ff131976e8)
mqq xx@0.0.3

I also tried that in an older version of npm and node.

$ nvm install 4.2.6
Downloading and installing node v4.2.6...
Downloading https://nodejs.org/dist/v4.2.6/node-v4.2.6-linux-x64.tar.xz...
######################################################################## 100.0%
Computing checksum with sha256sum
Checksums matched!
Now using node v4.2.6 (npm v2.14.12)

$ npm -v
2.14.12

$ npm install express
npm WARN package.json rest-test@1.0.0 No description
npm WARN package.json rest-test@1.0.0 No repository field.
npm WARN package.json rest-test@1.0.0 No README data
express@4.16.3 node_modules/express

$ ls node_modules/ | grep express
express

Does NOT the issue reproduce in older versions of npm?

@brandonpittman
Copy link

@brandonpittman brandonpittman commented May 29, 2018

Yeah, rolling back to Node 4.26 works. 8 still doesn't. This is dumb.

@nickwb
Copy link

@nickwb nickwb commented May 29, 2018

👍 Me too.

For those looking for a workaround, yarn still seems to be healthy.

@ajithmjose
Copy link

@ajithmjose ajithmjose commented May 29, 2018

I have started experiencing this issue from just today. I am behind an organisational firewall.

$ npm install
npm ERR! code E418
npm ERR! 418 I'm a teapot: @react-ag-components/core@latest

Other people in my team have no issues running the same npm code from their workstation. Only me is having the problem.

@wgrant
Copy link

@wgrant wgrant commented May 29, 2018

The body of the 418 is {"error":"got unknown host (registry.npmjs.org:443)"}. Looks like some npm clients are appending the port to the Host header, but only when going through a proxy, and that's confusing the registry:

$ wget --header='Host: registry.npmjs.org:443' https://registry.npmjs.org/
--2018-05-29 01:22:08--  https://registry.npmjs.org/
Resolving registry.npmjs.org (registry.npmjs.org)... 104.18.95.96, 104.18.97.96, 104.18.94.96, ...
Connecting to registry.npmjs.org (registry.npmjs.org)|104.18.95.96|:443... connected.
HTTP request sent, awaiting response... 418 I'm a teapot
2018-05-29 01:22:08 ERROR 418: I'm a teapot.

@itbaby
Copy link

@itbaby itbaby commented May 29, 2018

yes, we are meeting the same issue now.

@semogflex
Copy link

@semogflex semogflex commented May 29, 2018

Me too,

npm ERR! code E418
npm ERR! 418 I'm a teapot: moment@latest

node -v
v8.2.1

npm -v
5.3.0

I'm behind a proxy too.

@marcus-crane
Copy link

@marcus-crane marcus-crane commented May 29, 2018

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.

@npm npm locked as too heated and limited conversation to collaborators May 29, 2018
@zkat
Copy link
Contributor

@zkat zkat commented May 29, 2018

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.

@ceejbot
Copy link
Contributor

@ceejbot ceejbot commented May 29, 2018

We've fixed this -- we now accept the port appended to the host. @wgrant's comment was most helpful, thank you!

@ceejbot ceejbot closed this May 29, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet