Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] RequestError: 140476416780160:error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record #1600

Closed
numToStr opened this issue Jul 18, 2020 · 6 comments
Labels
bug Something isn't working stale Issues that didn't get attention

Comments

@numToStr
Copy link

Describe the bug
So today I upgrade a project from v1.22.4 to v2.1.1 and enabled the node_modules linker in the .yarnrc.yml which was autogenerated after the upgrade. After that, I ran yarn in the project folder and I got this issue. Also, It hangs in the end and I need to force quite by pressing
Ctrl+C.

❯ yarn          
➤ YN0000: ┌ Resolution step
➤ YN0001: │ RequestError: 140476416780160:error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac:../deps/openssl/openssl/ssl/record/ssl3_record.c:677:

    at ClientRequest.<anonymous> (/home/hello/Documents/code/cricuru/.yarn/releases/yarn-berry.js:23:51765)
    at Object.onceWrapper (events.js:422:26)
    at ClientRequest.emit (events.js:327:22)
    at ClientRequest.e.emit (/home/hello/Documents/code/cricuru/.yarn/releases/yarn-berry.js:2:468464)
    at TLSSocket.socketErrorListener (_http_client.js:426:9)
    at TLSSocket.emit (events.js:315:20)
    at TLSSocket._emitTLSError (_tls_wrap.js:892:10)
    at TLSWrap.onerror (_tls_wrap.js:413:11)
➤ YN0000: └ Completed in 14.06s
➤ YN0000: Failed with errors in 14.07s

To Reproduce

  1. Upgrade from 1.22.4 to 2.1.1
  2. Enable node_modules linker
  3. Run yarn

Screenshots
Screenshot_20200718_203440

Environment if relevant (please complete the following information):

  • OS: Linux
  • Node version: 12.18.2
  • Yarn version: 2.1.1
@numToStr numToStr added the bug Something isn't working label Jul 18, 2020
@merceyz
Copy link
Member

merceyz commented Jul 19, 2020

I'm afraid this isn't enough information to reproduce, please provide either a Sherlock reproduction or a GitHub repository we can test.

Based on the limited information i'd guess that this most likely is an issue with your machine and not Yarn, try testing on a different machine to check.

@kivervinicius
Copy link

kivervinicius commented Jul 22, 2020

same problem here

image

@merceyz
Copy link
Member

merceyz commented Jul 22, 2020

Please provide a reproduction.

As far as I can tell this seems to be sindresorhus/got#850, are you using a custom proxy or registry without specifying the protocol?

@kivervinicius
Copy link

@merceyz Well, I'm using nexus as a private repository, if I remove my dependency from the repository it works, when I come back, the error appears again.

My .yarnrc.yml

yarnPath: .yarn/releases/yarn-2.1.1.cjs
npmRegistryServer: https://192.168.5.90:8083/repository/npm-public/
npmAlwaysAuth: true
npmAuthIdent: ${AUTH_GITLAB_NEXUS}
unsafeHttpWhitelist: "*192.168.5.90*"

@kivervinicius
Copy link

In the same private repository I can't use yarn add after the error:
image
If I add directly to the package.json it works.

@yarnbot
Copy link
Collaborator

yarnbot commented Aug 22, 2020

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! 🌟

@yarnbot yarnbot added the stale Issues that didn't get attention label Aug 22, 2020
@yarnbot yarnbot closed this as completed Aug 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale Issues that didn't get attention
Projects
None yet
Development

No branches or pull requests

4 participants