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

Can't install plugins due to SSL routines:final_renegotiate:unsafe legacy renegotiation disabled error #2523

Closed
kogonows opened this issue Oct 11, 2023 · 2 comments
Labels
validated Version information for this issue has been validated wontfix We won't work on this issue

Comments

@kogonows
Copy link

kogonows commented Oct 11, 2023

Summary

Can't download @salesforce/plugin-packaging due to unsafe legacy renegotiation. I use VPN on my corporate PC.

Steps To Reproduce

sf plugins:install @salesforce/plugin-packaging

Expected result

plugin should be installed successfully

Actual result

$ sf plugins:install @salesforce/plugin-packaging
Polling for new version(s) to become available on npm... done
Successfully validated digital signature for @salesforce/plugin-packaging.
Finished digital signature check.
Installing plugin packaging... / [1/4] Resolving packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/@salesforce%2fplugin-packaging: write EPROTO 64700000:error:0A000152:SSL routines:final_renegotiate:unsafe legacy renegotiation disabled:c:\\ws\\deps\\openssl\\openssl\\ssl\\statem\\extensions.c:922:
Installing plugin packaging... failed
    Error: C:\Program Files\sf\client\node_modules\yarn\bin\yarn.js add @salesforce/plugin-packaging@latest --non-interactive --mutex=file:C:\Users\kamig\AppData\Local\sf\yarn.lock 
    --preferred-cache-folder=C:\Users\kamig\AppData\Local\sf\yarn --check-files exited with code 1

System Information

I use Git Bash git version 2.32.0.windows.2

{
  "cliVersion": "@salesforce/cli/2.11.8",
  "architecture": "win32-x64",
  "nodeVersion": "node-v18.15.0",
  "osVersion": "Windows_NT 10.0.19044",
  "shell": "C:\\Program Files\\Git\\usr\\bin\\bash.exe",
  "rootPath": "C:\\Users\\XXXXX\\AppData\\Local\\sf\\client\\2.11.8-c9872b8",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 2.3.8 (core)",
    "@oclif/plugin-commands 2.2.26 (core)",
    "@oclif/plugin-help 5.2.19 (core)",
    "@oclif/plugin-not-found 2.4.1 (core)",
    "@oclif/plugin-plugins 3.8.2 (core)",
    "@oclif/plugin-search 0.0.22 (core)",
    "@oclif/plugin-update 3.2.3 (core)",
    "@oclif/plugin-version 1.3.10 (core)",
    "@oclif/plugin-warn-if-update-available 2.1.0 (core)",
    "@oclif/plugin-which 2.2.32 (core)",
    "@salesforce/cli 2.11.8 (core)",
    "apex 2.3.15 (core)",
    "auth 2.8.17 (core)",
    "data 2.5.12 (core)",
    "deploy-retrieve 1.18.3 (core)",
    "info 2.6.45 (core)",
    "limits 2.3.35 (core)",
    "login 1.2.31 (core)",
    "marketplace 0.2.2 (core)",
    "org 2.10.8 (core)",
    "schema 2.3.28 (core)",
    "settings 1.4.30 (core)",
    "sobject 0.2.7 (core)",
    "source 2.10.36 (core)",
    "telemetry 2.3.4 (core)",
    "templates 55.5.13 (core)",
    "trust 2.6.15 (core)",
    "user 2.3.32 (core)"
  ]
}

Additional information

sf doctor output:

npm ERR! code SELF_SIGNED_CERT_IN_CHAIN
npm ERR! errno SELF_SIGNED_CERT_IN_CHAIN
npm ERR! request to https://registry.yarnpkg.com/@salesforce%2fcli failed, reason: self signed certificate in certificate chain

I would like to avoid downgrading to sfdx running npm 16 or put at risk security by enabling unsafe renegotiations.

@kogonows kogonows added the investigating We're actively investigating this issue label Oct 11, 2023
@github-actions
Copy link

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

@github-actions github-actions bot added the validated Version information for this issue has been validated label Oct 11, 2023
@iowillhoit
Copy link
Contributor

Hey @kogonows, this has come up a few times. You can view more discussion here.

As Shane mentioned in that issue, marking this as wontfix as there is nothing we can do about Node's internals.

@iowillhoit iowillhoit added wontfix We won't work on this issue and removed investigating We're actively investigating this issue labels Oct 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
validated Version information for this issue has been validated wontfix We won't work on this issue
Projects
None yet
Development

No branches or pull requests

2 participants