node: --openssl-legacy-provider is not allowed in NODE_OPTIONS

Question

This problem appeared after an update sudo apt upgrade on Ubuntu 20.04. Previously, I worked on versions node v18.0.0 and npm 8.7.0, but after the update there was a problem, I ran command nvm install node --reinstall-packages-from=node, but it did not help. Now I use npm v8.12.1, node v18.4.0. When running the command npm start I recieve the message :

> mini-app@0.0.0 start
> cross-env PORT=10888 HTTPS=false react-scripts start --openssl-legacy-provider

node: --openssl-legacy-provider is not allowed in NODE_OPTIONS

part of a file package.json looks like this :

 "scripts": {
    "start": "cross-env PORT=10888 HTTPS=false react-scripts start --openssl-legacy-provider",
    "build": "react-scripts build",
    "predeploy": "npm run build",
    "deploy": "vk-miniapps-deploy",
    "tunnel": "vk-tunnel --insecure=1 --http-protocol=https --ws-protocol=wss --host=localhost --port=10888"
  },

I went back to version npm 8.7.0, npm install -g npm@8.7.0 but now even the output of node version shows the same error :

node -v
node: --openssl-legacy-provider is not allowed in NODE_OPTIONS

attempt to update :

nvm install 12.13.0
v12.13.0 is already installed.
Now using node v12.13.0 (npm v)

if someone ends up here who have `lerna` configuration then directly jumping on particular package setup, make sure you `install`, `prepare` and `build` all packages first. No need of any further changes required for `--openssl-legacy-provider` if it was already there — Sumit Ramteke, May 19 '23 at 02:08

score 62 · Answer 1 · answered Aug 28 '22 at 15:06

62

I ran into this on MacOS. From terminal, I ran export to check my environment variables and saw that NODE_OPTIONS=--openssl-legacy-provider had been set. I then simply ran unset NODE_OPTIONS and then was able to use node again.

answered Aug 28 '22 at 15:06

broox

3,538
33
25

score 23 · Answer 2 · answered Oct 17 '22 at 09:38

23

Just Run this command

unset NODE_OPTIONS

answered Oct 17 '22 at 09:38

Ayman Elshehawy

2,746
23
21

4

or in Windows: set NODE_OPTIONS= – Aadmaa Dec 24 '22 at 19:55

score 21 · Answer 3 · answered Jul 21 '22 at 10:41

21

On Linux, you need to edit your /etc/ssl/openssl.cnf to un-comment a few lines that will enable legacy provider support.

I am on Fedora 36; I had to change these lines:

##[provider_sect]
##default = default_sect
##legacy = legacy_sect
##
##[default_sect]
##activate = 1
##
##[legacy_sect]
##activate = 1

to:

[provider_sect]
default = default_sect
legacy = legacy_sect

[default_sect]
activate = 1

[legacy_sect]
activate = 1

answered Jul 21 '22 at 10:41

rimkashox

978
9
14

1

Time saver, got this problem on Fedora 36 too. Thanks mate! – Nicolas W. Aug 08 '22 at 15:33
1

Just complementing these lines did not yet do the trick, do I need to restart something? – white_gecko Aug 17 '22 at 09:10
4

ok, I had to uncomment the section, then delete the `node_modules` and run `npm install` again. Then it even worked without `--openssl-legacy-provider` since I'm still running on node v16.14.0 on Fedora 36. – white_gecko Aug 17 '22 at 10:03
didn't work for me at all, so the solution was to install the nvm and use it to install the latest v16. https://github.com/nvm-sh/nvm – Oleksii Donoha Nov 24 '22 at 17:07
1

didn't work any solution except every time exportin node_options with flag. It happens when change node version in nvm from 14.17 to 16. after then, event downgrading to 14.21 is not solution for me (using yarn, not npm) – Sinneren Jan 18 '23 at 09:14

score 21 · Answer 4 · answered Oct 25 '22 at 10:44

21

For me unsetting NODE_OPTIONS alone didn't solve the problem, had to use

nvm use v18

to solve the issue

answered Oct 25 '22 at 10:44

Nisha

311
2
3

2

Life saver. But I think I had to run `unset NODE_OPTIONS` before. – thodwris Nov 30 '22 at 21:23
on mac, this solved my problem – Kasi Feb 24 '23 at 19:45
On mac solved my problem as well – Hadrien Jaubert Jul 23 '23 at 16:52

score 11 · Answer 5 · answered May 03 '23 at 08:33

11

Simple way throught NPM.

We can set the SSL legacy option in the .npmrc file.

In my case NodeJS v18 with npm v9

Add or edit .npmrc file in your project folder and add the option:

node-options="--openssl-legacy-provider"

Advantages:

It can be manage per project
The .npmrc file in the project will remind us that the project needs to be updated.
If that appear on other project in the server we will still have the error.

answered May 03 '23 at 08:33

Michaël

141
1
7

I resorted to using yarn. Not a solution if you must use npm, but this allowed me to continue. > yarn install Done – Henk Kruger Jul 05 '23 at 18:22
1

This worked for me. Thanks a lot mate. – Thorin Jul 19 '23 at 05:28
Hi @HenkKruger, sorry I'm using NPM so I didn't search for yarn. – Michaël Jul 20 '23 at 12:14
1

Best solution for sure! – Jhony Spark Aug 05 '23 at 05:44

score 8 · Answer 6 · edited Jan 12 '23 at 10:56

I'm running macOS. I previously had Node Version 18, which had this issue in my NodeJs Project

Error message "error:0308010C:digital envelope routines::unsupported"

I downgraded the Node Version to 16 LTS, and then it had this error

node: --openssl-legacy-provider is not allowed in NODE_OPTIONS

The issue resolved by simply running the following command in the terminal.

unset NODE_OPTIONS

Hope this helps! :)

score 5 · Accepted Answer · edited Feb 05 '23 at 16:52

5

You can try to perform an unset on the NODE_OPTIONS production variable. It can be done from the command line.

Your Node version seems already up-to-date (version 18). A similar problem was already treated and solved according to the following Github link: https://github.com/microsoft/vscode/issues/136599

edited Feb 05 '23 at 16:52

E_net4

27,810
13
101
139

answered Jul 07 '22 at 20:33

Peter Minea

66
3

thanks, that helped! i also used the command `nvm install 10` to fix the error : `ERROR: npm is known not to run on Node.js v10.19.0 You'll need to upgrade to a newer Node.js version in order to use this version of npm. You can find the latest version at https://nodejs.org/` – milenao Jul 08 '22 at 07:26

score 5 · Answer 8 · edited Jul 23 '22 at 09:51

5

I installed a new version but not did use

nvm use node

edited Jul 23 '22 at 09:51

Tyler2P

2,324
26
22
31

answered Jul 22 '22 at 08:21

Aren Gevorgyan

49
1

score 5 · Answer 9 · answered May 05 '23 at 03:01

QUICK FIX

You can try downgrade the version. But as a quick fix you can do the below options.

On Unix-like (Linux, macOS, Git bash, etc.):

export NODE_OPTIONS=--openssl-legacy-provider

On Windows command prompt:

set NODE_OPTIONS=--openssl-legacy-provider

On PowerShell:

$env:NODE_OPTIONS = "--openssl-legacy-provider"

WAY 1

Try reseting NODE_OPTIONS by running following command

export NODE_OPTIONS=""

WAY 2

Upgrade to Node 18

nvm use v18

answered Apr 24 '23 at 06:19

Akul Srivastava

89
4

score 0 · Answer 11 · answered Mar 20 '23 at 03:27

0

update NVM to v18,

then unset NODE_OPTIONS

WILL BE OK!

answered Mar 20 '23 at 03:27

Jay

1

This answer appears to be a duplicate of one already provided [here](https://stackoverflow.com/a/74192831/6951294). – sloppypasta Mar 27 '23 at 23:59

Ronaldo Patterson · Answer 12 · 2023-03-21T18:03:17.123

0

The above were good suggestions. However, what worked for me was commenting the entry in the .npmrc file located in my project folder as shown here

edited Mar 21 '23 at 18:03

answered Mar 21 '23 at 18:01

Ronaldo Patterson

1
1

score 0 · Answer 13 · answered Jul 26 '23 at 12:48

I had the same issue with react-native ./gradlew assembleRelease.

Solved this by downgrading node version to v18.17.0 and setting node options as --openssl-legacy-provider

Commands

nvm install v18

nvm use v18

export NODE_OPTIONS=--openssl-legacy-provider

score 0 · Answer 14 · answered Aug 16 '23 at 07:01

This will happen when someone using/moving to an older version of node JS possibly by nvm.

Two possible solution

Change nvm to use node version 18 or above
Remove export NODE_OPTIONS=--openssl-legacy-provider from npmrc by following below steps a. open ~/.npmrc b. remove line export NODE_OPTIONS=--openssl-legacy-provider from it and save

score 0 · Answer 15 · answered Aug 17 '23 at 10:21

I was facing Error on yarn start. Error screenshot is attached below

Now I fixed this by following steps: open pakage.json and change script object

  "scripts": {
  "android": "react-native run-android",
  "build_debug": "react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle --assets-dest android/app/src/main/res",
  "ios": "react-native run-ios",
  "start": "cross-env NODE_OPTIONS= --openssl-legacy-provider start",
  "test": "jest",
  "lint": "eslint .",
  "android_apk": "npx react-native run-android --variant=release"
  
  },

with this

"scripts": {
    
        "android": "react-native run-android",
        "ios": "react-native run-ios",
        "build": "react-native run-android --mode=release",
        "lint": "eslint .",
        "start": "react-native start",
        "test": "jest"
      },

And second step I performed is that created a .env file in my React Native Project root directory and place the below code in it

NODE_OPTIONS="--openssl-legacy-provider"

And again run yarn start command

score -1 · Answer 16 · answered Jul 03 '23 at 23:50

-1

I had to run this also:

nvm install lts

answered Jul 03 '23 at 23:50

SauravBhattacharya

631
3
9
24

score -1 · Answer 17 · answered Jul 05 '23 at 18:18

-1

After trying everything suggested but still not working, I resorted to using yarn. Not a solution if you must use npm, but this allowed me to continue.

yarn install

Done

answered Jul 05 '23 at 18:18

Henk Kruger

177
1
4