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

user_12485499 0
Viewed 11999

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)
node-modules npm node.js
4 Answers

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
user_25930630

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.

user_4466040

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

Hope the hints in the above resource help! Kind regards, Peter

user_146857950

I installed a new version but not did use

nvm use node
user_194999140
Related