[Bug] unable to get local issuer certificate

[gabor-s]

• I'd be willing to implement a fix

Describe the bug

I'm behind a corporate proxy, when I issue yarn install I get RequestError: unable to get local issuer certificate. caFilePath is set in .yarnrc.yml. If I set the NODE_EXTRA_CA_CERTS environment variable to the same path (set in caFilePath) then yarn install works perfectly.

To Reproduce

You can't reproduce it because of the corporate proxy.

Environment if relevant (please complete the following information):

• OS: Windows
• Node version: 14.15.3
• Yarn version: 2.4.0

[merceyz]

You can't reproduce it because of the corporate proxy.

You still need to show the config etc. (redact as needed) otherwise there isn't much we can do with this

[gabor-s]

.yarnrc.yml:

yarnPath: ".yarn/releases/yarn-berry.cjs"
enableTelemetry: false
defaultSemverRangePrefix: ""
httpProxy: "$$CORPORATE_HTTP_PROXY$$"
httpsProxy: "$$SAME_AS_ABOVE$$"
caFilePath: "$$PATH_TO_OUR_CORPORATE_CERT.PEM$$"

If I set NODE_EXTRA_CA_CERTS to $$PATH_TO_OUR_CORPORATE_CERT.PEM$$ then yarn install works.

[merceyz]

Ah, you need caFilePath to be applied to the proxy itself?

[gabor-s]

If the traffic goes through our corporate proxy then the root CA will be our corporate CA. Does it answer your question?

[yarnbot]

Hi! 👋

This issue looks stale, and doesn't feature the reproducible label - which implies that you didn't provide a working reproduction using Sherlock. As a result, it'll be closed in a few days unless a maintainer explicitly vouches for it or you edit your first post to include a formal reproduction (you can use the playground for that).

Note that we require Sherlock reproductions for long-lived issues (rather than standalone git repositories or similar) because we're a small team. Sherlock gives us the ability to check which bugs are still affecting the master branch at any given point, and decreases the amount of code we need to run on our own machines (thus leading to faster bug resolutions). It helps us help you! 😃

If you absolutely cannot reproduce a bug on Sherlock (for example because it's a Windows-only issue), a maintainer will have to manually add the upholded label. Thanks for helping us triaging our repository! 🌟

[eliw00d]

I recently upgraded to yarn berry 3.0.2 and suddenly get this error even though I had YARN_CA_FILE_PATH set. Once I set NODE_EXTRA_CA_CERTS it worked.

Other than the env vars, my config looks like:

defaultSemverRangePrefix: ""

nodeLinker: node-modules

npmRegistryServer: [REDACTED]

plugins:
  - path: .yarn/plugins/@yarnpkg/plugin-workspace-tools.cjs
    spec: "@yarnpkg/plugin-workspace-tools"
  - path: .yarn/plugins/@yarnpkg/plugin-interactive-tools.cjs
    spec: "@yarnpkg/plugin-interactive-tools"
  - path: .yarn/plugins/@yarnpkg/plugin-typescript.cjs
    spec: "@yarnpkg/plugin-typescript"
  - path: .yarn/plugins/@yarnpkg/plugin-version.cjs
    spec: "@yarnpkg/plugin-version"

yarnPath: .yarn/releases/yarn-3.0.2.cjs

where npmRegistryServer is corporate.