Timeouts from https://registry.npmjs.org/

Not sure where to post this, so:

registry.npmjs.org is hosted by Fastly. When using HTTPS, this host gives us a lot of timeouts.

Examples:

$ curl -v https://registry.npmjs.org
* Rebuilt URL to: https://registry.npmjs.org/
*   Trying 199.27.76.162...
* connect to 199.27.76.162 port 443 failed: Operation timed out
* Failed to connect to registry.npmjs.org port 443: Operation timed out
* Closing connection 0
curl: (7) Failed to connect to registry.npmjs.org port 443: Operation timed out

$ curl -v https://registry.npmjs.org
* Rebuilt URL to: https://registry.npmjs.org/
*   Trying 23.235.46.162...
* connect to 23.235.46.162 port 443 failed: Operation timed out
* Failed to connect to registry.npmjs.org port 443: Operation timed out
* Closing connection 0
curl: (7) Failed to connect to registry.npmjs.org port 443: Operation timed out

If this was an origin error, I would have expected to see a 503 HTTP error, and not a timeout when setting up the connection.

Because npm talks to registry.npmjs.org about a gazillion times during a normal npm install run, this causes lots of issues for us. As a workaround we’ve had to set npm to use HTTP when connecting to the registry, but clearly this is not ideal.

Any ideas in this community? Is this a known issue at Fastly’s end, or is it actually an origin problem?

Chris Gonyea

March 03, 2016 17:56

Hello,

Can you go to http://www.fastly-debug.com/ from a location encountering this issue and send support@fastly.com the text block it output? This will help us begin narrowing down the issue here.

Martin_Melin

March 03, 2016 19:48

Thanks for the quick reply - just sent output via email.

Comments