Closed autonome closed 5 years ago
@autonome looks like the whole registry is broken/offline: any request to https://registry.js.ipfs.io/ is throwing 502 bad gateway errors.
Looks like it's back up now, thanks to @achingbrain
502 is gone, thanks y'all. Seeing a new error now, which I reported in #116.
Mac OS X 10.14.6 NPM 6.11.2 IPFS Desktop 0.9.1
Log:
twerkworker-5935:buttons dietrich$ ipfs-npm i hypersimple superagent: Enable experimental feature http2 👩🚀 Starting local proxy 🚀 Server running on port 55409 🎁 Installing dependencies with /Users/dietrich/.npm-packages/bin/npm 😈 Spawning an in-process IPFS node using repo at /Users/dietrich/.jsipfsf9cc0949 Swarm listening on /ip4/127.0.0.1/tcp/55413/ipfs/QmdUbfvZohU6F6e24MJU8R8NEhRFZPq1rGyP78uy8nsGw4 Swarm listening on /p2p-circuit/ipfs/QmdUbfvZohU6F6e24MJU8R8NEhRFZPq1rGyP78uy8nsGw4 Swarm listening on /p2p-circuit/ip4/127.0.0.1/tcp/55413/ipfs/QmdUbfvZohU6F6e24MJU8R8NEhRFZPq1rGyP78uy8nsGw4 🗂️ Loading registry index from https://registry.js.ipfs.iossion 554e45abf9cc0949 🚨 Request to GET https://registry.js.ipfs.io failed on attempt 1 - StatusCodeError: 502 - "\r\n502 Bad Gateway
502 Bad Gateway
502 Bad Gateway
502 Bad Gateway
502 Bad Gateway
502 Bad Gateway
502 Bad Gateway
502 Bad Gateway
502 Bad Gateway
502 Bad Gateway
502 Bad Gateway
502 Bad Gateway
502 Bad Gateway
502 Bad Gateway
502 Bad Gateway
502 Bad Gateway
502 Bad Gateway
502 Bad Gateway
502 Bad Gateway
502 Bad Gateway
502 Bad Gateway
502 Bad Gateway
502 Bad Gateway
502 Bad Gateway