403 error page from CloudFlare on https://registry.yarnpkg.com

[schneidmaster]

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

yarn add <anything> returns 403, which makes sense because https://registry.yarnpkg.com shows an error from CloudFlare:

This article suggests it's caused by a DNS misconfiguration?

What is the expected behavior?

Package successfully installs.

Please mention your node.js, yarn and operating system version.

node 8.9, yarn 1.6, macOS 10.13.4 (though I doubt any of that is relevant 🙂)

[codymikol]

@ktalebian You're right, I must have just been pulling from a cache, my CI still fails to pull down dependencies

[miguelmota]

@judge2020 thanks for the clarification. A records were blank earlier too but now it's up

[cromatikap]

yarn add echarts error Received malformed response from registry for undefined. The registry may be down.

Is it supposed to be fixed ?

[coltonmercurio]

Maybe a use a staging environment to test the deployment next time /s

[ktalebian]

@ceejbot can npmjs rollback going behind cloudflare?

[schneidmaster]

Looks like yarn is back up! They've also updated the status page to indicate that it's back.

[Daniel15]

This should be resolved now. Please let us know if you still experience any issues!

[afuno]

Not really.

error sending request or no backends responded in time. Error: no backends responded in time

Or:

$ yarn
yarn install v1.7.0
info No lockfile found.
[1/5] 🔍  Validating package.json...
[2/5] 🔍  Resolving packages...
error Received malformed response from registry for undefined. The registry may be down.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

[Daniel15]

OK, I'll leave this open for a bit. Seems like there's an issue on npm's end. @ceejbot @isaacs does that error come from npm's backend?

error sending request or no backends responded in time. Error: no backends responded in time

[Daniel15]

@waltonseymour Sounds like it's working for you :) A JSON response is expected from that endpoint.

[transitive-bullshit]

If this was a DNS change, it'll likely take a variable amount of time to propagate for different peeps.

[ktalebian]

I still cannot install

[MarshallOfSound]

I'm now just getting a whole bunch of

error sending request or no backends responded in time. Error: no backends responded in time

[eGust]

> yarn add lodash --verbose
yarn add v1.7.0
...
verbose 0.266 current time: 2018-05-26T00:59:34.218Z
[1/4] 🔍  Resolving packages...
verbose 0.721 Performing "GET" request to "https://registry.yarnpkg.com/lodash".
verbose 15.821 Request "https://registry.yarnpkg.com/lodash" finished with status code 503.
verbose 15.823 Error: Received malformed response from registry for undefined. The registry may be down.
    at MessageError.ExtendableBuiltin (/usr/local/Cellar/yarn/1.7.0/libexec/lib/cli.js:243:66)
    at new MessageError (/usr/local/Cellar/yarn/1.7.0/libexec/lib/cli.js:272:123)
    at Function.<anonymous> (/usr/local/Cellar/yarn/1.7.0/libexec/lib/cli.js:52175:15)
    at Generator.next (<anonymous>)
    at step (/usr/local/Cellar/yarn/1.7.0/libexec/lib/cli.js:98:30)
    at /usr/local/Cellar/yarn/1.7.0/libexec/lib/cli.js:116:14
    at new Promise (<anonymous>)
    at new F (/usr/local/Cellar/yarn/1.7.0/libexec/lib/cli.js:23451:28)
    at Function.<anonymous> (/usr/local/Cellar/yarn/1.7.0/libexec/lib/cli.js:95:12)
    at Function.findVersionInRegistryResponse (/usr/local/Cellar/yarn/1.7.0/libexec/lib/cli.js:52217:19)
error Received malformed response from registry for undefined. The registry may be down.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

> curl https://registry.yarnpkg.com/lodash
error sending request or no backends responded in time. Error: no backends responded in time

[haocse]

Setting registry "https://registry.npmjs.org" seems work better, but still got status code 503 sometimes?

[tayler-king]

Also not working for GitHub. I assume yarn just directs all queries to NPM to resolve packages.

Edit: Seems as though it might be back up now?

[leonardfactory]

On development machine (macOS), flushing dns with sudo killall -HUP mDNSResponder did the trick. Not sure if this, or yarn fixed my issue right while typing it 😄

[afuno]

Now everything works.

[rheilgm]

seems good now!

[germmand]

Everything is working flawlessly now. Yass! :beer: :beer:

[transitive-bullshit]

Agreed with @leonardfactory, flushing my dns cache resolved the issue locally.

[ceejbot]

We've worked with Cloudflare & the yarn team to set up a temporary workaround-- it's now a cname to yarn.npmjs.org, which we set up outside of Cloudflare. We'll have to come up with another solution soon, however, but this unblocks you all.

[haocse]

3 hours panicking and now it works haha :joy: Thanks.

[Kangaroux]

Thanks for being so responsive.

[kevryan2]

@ceejbot does that mean for now that everyone who utilizes the registry will either need to work directly with npm to fix their cname or just continue to be down until further notice?

[Daniel15]

OK I'm going to close this out now that it seems to be fully fixed. Happy Friday everyone (at least in US timezones). Go out and enjoy your weekend :)

[arcanis]

Glad to see everything working again! 😌

Thanks to Cloudflare and the npm team for being reactive about this issue! Seeing cooperation in practice feels great 🙂

[schneidmaster]

@KevRyan2 No, yarn is back up as of 30-45 minutes ago. @ceejbot was describing the temporary workaround that they implemented to fix yarn.

[schneidmaster]

cheers to @arcanis @Daniel15 @ceejbot et al for the responsiveness! have a great weekend 🙂

[coltonmercurio]

Thanks, all working now. Appreciate the effort

[shashidhargm]

Still same issue!

[SupremeTechnopriest]

Error: Received malformed response from registry for undefined. The registry may be down.

As of a few minutes ago. Was working fine all afternoon.

[elixiao]

yarn add @angular/material
yarn add v1.7.0
[1/4] 🔍  Resolving packages...
error Received malformed response from registry for undefined. The registry may be down.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

[rdsedmundo]

Not sure if it's related, but I'm receiving 429 - Too Many Requests error while running the yarn install command.

+ yarn install --pure-lockfile --prefer-offline --cache-folder yarn-cache
yarn install v1.6.0
(node:33) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/json5/-/json5-0.4.0.tgz: Request failed \"429 Too Many Requests\"".
info If you think this is a bug, please open a bug report with the information provided in "/opt/atlassian/pipelines/agent/build/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

[arcanis]

I think those issues are coming directly from the npm registry, unfortunately 🙁