Impossible to serve with Node v17.0.1 #6770

Miguel-Bento-Github · 2021-10-21T08:07:15Z

Version

5.0.0-beta.6

Environment info

Environment Info:

  System:
    OS: macOS 11.5.2
    CPU: (8) arm64 Apple M1
  Binaries:
    Node: 17.0.1 - /usr/local/bin/node
    Yarn: 1.22.15 - /opt/homebrew/bin/yarn
    npm: 8.1.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 94.0.4606.81
    Edge: Not Found
    Firefox: 92.0
    Safari: 14.1.2
  npmPackages:
    @intlify/vue-devtools:  9.1.9 
    @intlify/vue-i18n-loader: 3.2.0 => 3.2.0 
    @storybook/vue3: 6.3.12 => 6.3.12 
    @vue/babel-helper-vue-jsx-merge-props:  1.2.1 
    @vue/babel-helper-vue-transform-on:  1.0.2 
    @vue/babel-plugin-jsx:  1.1.1 
    @vue/babel-plugin-transform-vue-jsx:  1.2.1 
    @vue/babel-preset-app:  5.0.0-beta.6 
    @vue/babel-preset-jsx:  1.2.4 
    @vue/babel-sugar-composition-api-inject-h:  1.2.1 
    @vue/babel-sugar-composition-api-render-instance:  1.2.4 
    @vue/babel-sugar-functional-vue:  1.2.2 
    @vue/babel-sugar-inject-h:  1.2.2 
    @vue/babel-sugar-v-model:  1.2.3 
    @vue/babel-sugar-v-on:  1.2.3 
    @vue/cli-overlay:  5.0.0-beta.6 
    @vue/cli-plugin-babel: 5.0.0-beta.6 => 5.0.0-beta.6 
    @vue/cli-plugin-e2e-cypress: 5.0.0-beta.6 => 5.0.0-beta.6 
    @vue/cli-plugin-eslint: 5.0.0-beta.6 => 5.0.0-beta.6 
    @vue/cli-plugin-router: 5.0.0-beta.6 => 5.0.0-beta.6 
    @vue/cli-plugin-typescript: 5.0.0-beta.6 => 5.0.0-beta.6 
    @vue/cli-plugin-unit-jest: 5.0.0-beta.6 => 5.0.0-beta.6 
    @vue/cli-plugin-vuex: 5.0.0-beta.6 => 5.0.0-beta.6 
    @vue/cli-service: 5.0.0-beta.6 => 5.0.0-beta.6 
    @vue/cli-shared-utils:  5.0.0-beta.6 
    @vue/compiler-core:  3.2.20 
    @vue/compiler-dom:  3.2.20 
    @vue/compiler-sfc: 3.2.20 => 3.2.20 
    @vue/compiler-ssr:  3.2.20 
    @vue/component-compiler-utils:  3.2.2 
    @vue/devtools-api:  6.0.0-beta.19 
    @vue/eslint-config-prettier: 6.0.0 => 6.0.0 
    @vue/eslint-config-typescript: 8.0.0 => 8.0.0 
    @vue/reactivity:  3.2.20 
    @vue/ref-transform:  3.2.20 
    @vue/runtime-core:  3.2.20 
    @vue/runtime-dom:  3.2.20 
    @vue/server-renderer:  3.2.20 
    @vue/shared:  3.2.20 
    @vue/test-utils: 2.0.0-rc.16 => 2.0.0-rc.16 
    @vue/vue3-jest: 27.0.0-alpha.1 => 27.0.0-alpha.1 
    @vue/web-component-wrapper:  1.3.0 
    eslint-plugin-vue: 7.20.0 => 7.20.0 
    jest-serializer-vue:  2.0.2 
    typescript: 4.4.4 => 4.4.4 
    vue: 3.2.20 => 3.2.20 (2.6.14)
    vue-cli-plugin-i18n: 2.3.1 => 2.3.1 
    vue-docgen-api:  4.41.2 
    vue-docgen-loader:  undefined (1.5.0)
    vue-eslint-parser:  7.11.0 
    vue-hot-reload-api:  2.3.4 
    vue-i18n: 9.1.9 => 9.1.9 (8.26.5)
    vue-i18n-extract:  1.0.2 
    vue-inbrowser-compiler-utils:  4.41.2 
    vue-loader: 16.8.1 => 16.8.1 (15.9.8)
    vue-router: 4.0.12 => 4.0.12 
    vue-style-loader:  4.1.3 
    vue-template-es2015-compiler:  1.9.1 
    vue3-click-away: 1.2.1 => 1.2.1 
    vuex: 4.0.2 => 4.0.2 
  npmGlobalPackages:
    @vue/cli: Not Found

Steps to reproduce

Update to Node v17.0.1
Create a new vue 3 app through the cli
run vue-cli-service serve script

What is expected?

Normal compilation of the app

What is actually happening?

Exit code 1

The following object appears in the console

{
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

From https://medium.com/the-node-js-collection/node-js-17-is-here-8dba1e14e382
we can see this issue is due to Open SSL 3.0

From the article:

"If you hit an ERR_OSSL_EVP_UNSUPPORTED error in your application with Node.js 17, it’s likely that your application or a module you’re using is attempting to use an algorithm or key size which is no longer allowed by default with OpenSSL 3.0. A new command-line option, --openssl-legacy-provider, has been added to revert to the legacy provider as a temporary workaround for these tightened restrictions."

The text was updated successfully, but these errors were encountered:

sodatea · 2021-10-21T11:52:42Z

Seems a webpack issue webpack/webpack#14532 (comment)

wunderdaz · 2021-10-21T12:27:04Z

Also running into this issue while trying to build a plugin:

npx vue-cli-service build --target lib --formats umd-min --no-clean --dest assets/ --name "XXXXXX.[chunkhash]" src/plugin/YYYYYY/ZZZZZ.vue
-  Building for production as library (umd-min)...
node:internal/crypto/hash:67
  this[kHandle] = new _Hash(algorithm, xofLen);
                  ^

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

sodatea · 2021-10-26T14:11:27Z

Fixed in v5.0.0-beta.7

mrichman · 2021-11-04T18:27:12Z

export NODE_OPTIONS=--openssl-legacy-provider fixes it for me.

cyber-netics · 2021-11-07T19:39:12Z

Downgrading to Node:16.13.0 worked for me

paulxtiseo · 2021-11-09T17:28:32Z

Fixed in v5.0.0-beta.7

I just uninstalled @vue/cli 4.5.15 and installed @vue/cli 5.0.0-rc.0 and am getting the error, under NodeJS 17.0.1. The solution presented by @mrichman worked for me, but I worry about making sure to remove this in timely way when webpack/openssl resolve this...

sergiocabral · 2021-11-16T16:42:54Z

export NODE_OPTIONS=--openssl-legacy-provider fixes it for me.

Works for me with:

Node v. 17.1.0
@vue/cli v. 4.5.15
PowerShell 7.2.0
Windows 10 v. 20H2

paulxtiseo · 2021-11-19T02:12:50Z

@sergiocabral, I have seen that solution, but I also thought it had been addressed in v5.0.0-beta.7 per @sodatea?

mhavid · 2021-11-30T14:01:23Z

@Miguel-Bento-Github
change script in pancake.json with
"serve": "SET NODE_OPTIONS=--openssl-legacy-provider && vue-cli-service serve", "build": "SET NODE_OPTIONS=--openssl-legacy-provider && vue-cli-service build"

Miguel-Bento-Github · 2021-11-30T14:30:49Z

@mhavid You are commenting on a closed issue that has already been fixed.

K4L231 · 2021-12-02T13:59:01Z

@Miguel-Bento-Github change script in pancake.json with "serve": "SET NODE_OPTIONS=--openssl-legacy-provider && vue-cli-service serve", "build": "SET NODE_OPTIONS=--openssl-legacy-provider && vue-cli-service build"

THIS IS LEGIT ONLY ONE THING THAT WORKED!!!!!! THANK YOU

jaredmeadowsLB · 2022-01-10T02:53:10Z

the SET NODE_OPTIONS strategy didn't work for me 😔, but what DID work was....
"serve": "export NODE_OPTIONS=--openssl-legacy-provider && vue-cli-service serve", "build": "export NODE_OPTIONS=--openssl-legacy-provider && vue-cli-service build",
(I just squished together @mrichman's fix and @mhavid, so credit to them!)

ffmit · 2022-01-17T11:06:15Z

On Windows who can do this on CMD using
set NODE_OPTIONS=--openssl-legacy-provider

raja-chaudhary · 2022-01-18T00:27:43Z

the SET NODE_OPTIONS strategy didn't work for me pensive, but what DID work was.... "serve": "export NODE_OPTIONS=--openssl-legacy-provider && vue-cli-service serve", "build": "export NODE_OPTIONS=--openssl-legacy-provider && vue-cli-service build", (I just squished together @mrichman's fix and @mhavid, so credit to them!)

I have updated this in my package.json but I have not pushed the package.json file to my heroku. I want to ask, will pushing this code to my heroku master break the website or is it safe to do so? I am asking because ever since I have upgraded to node v17.3.1 I have noticed a lot of dependencies have updated in my package-lock.json. I am not sure if updating and pushing both these files will build a functioning version on my live heroku server as well.

wunderdaz · 2022-01-18T05:58:39Z

@raja-chaudhary unfortunately that's a risk-weight analysis you need to do yourself, no one here can give you the answer to that. Just try on another test instance and see if it works.

It's easy if you have a staging environment ;)

Voucik · 2022-01-30T05:32:08Z

On Windows who can do this on CMD using set NODE_OPTIONS=--openssl-legacy-provider

It's not work in Windows cmd.
Thes help for me:

"scripts": {
    "serve": "SET NODE_OPTIONS=--openssl-legacy-provider && vue-cli-service serve", 
    "build": "SET NODE_OPTIONS=--openssl-legacy-provider && vue-cli-service build",
    "lint": "SET NODE_OPTIONS=--openssl-legacy-provider && vue-cli-service lint"
  },

Sazzad-Saju · 2022-02-03T08:34:23Z

Same issue with me, solved by doing this: unistall node.js. Install node v16.13.2 with additional components. Now again run npm run serve project will open on http://localhost:8080/

larodiel · 2022-02-15T02:54:29Z

SET NODE_OPTIONS=--openssl-legacy-provider

It worked, I just had to change SET to export on mac

avi9111 · 2022-04-30T08:29:37Z

Thanks, @Voucik, I used "SET NODE_OPTIONS "， it was Done for me

kamalud · 2022-11-26T04:59:16Z

not working yet

leolux · 2023-03-18T18:14:49Z

export NODE_OPTIONS=--openssl-legacy-provider

Where to add this line?

MarcelJurtz · 2023-03-19T19:32:13Z

export NODE_OPTIONS=--openssl-legacy-provider

Where to add this line?

@leolux in the package.json to the build scripts.

Gurushesh-Metapercept · 2023-06-14T07:40:16Z

how to add this environment variable in Firebase Hosting CICD ?

unset NODE_OPTIONS

Glideh · 2023-09-26T09:21:10Z

Using Docker, I had to add

ENV NODE_OPTIONS=--openssl-legacy-provider

in my Dockerfile

coreysyms · 2023-10-25T02:47:04Z

Nuxt / Node 18 being deployed on AWS Elastic BeanStalk. I needed to create a predeploy hook with the flag to get it to run. package.json scripts update did not work for me. But the below method did.

.platform > hooks > predeploy > 01_build.sh

#!/bin/bash
export NODE_OPTIONS=--openssl-legacy-provider
npm run build

vuejs/vue-cli#6770

ramrasu88 · 2024-01-17T02:18:12Z

what voucik has said helped me
we have to set the options mentioned by him/her in package.json file of vuejs

sodatea added bug priority: next labels Oct 21, 2021

sodatea closed this as completed Oct 26, 2021

Dadard29 mentioned this issue Dec 3, 2021

Override OpenSSL version PassiveDNS/PassiveDNS#24

Merged

gustav87 mentioned this issue Nov 22, 2022

Upgrade vue plugins w3champions/website#558

Merged

darrachequesne mentioned this issue Nov 30, 2022

private chat example code not working (part 1) socketio/socket.io#4532

Closed

becky2sawyer mentioned this issue Dec 6, 2022

ERR_OSSL_EVP_UNSUPPORTED resume-diginori/resume-diginori.github.io#1

Closed

solderq35 mentioned this issue Dec 20, 2022

Node 16 branch OSU-Sustainability-Office/energy-dashboard#194

Merged

vishnu-narayanan mentioned this issue Jan 12, 2023

chore: upgrade ruby to 3.1.3 chatwoot/chatwoot#5555

Merged

10 tasks

520-STB mentioned this issue Mar 17, 2023

Problème avec Vue quand Node.js > 17 supercinemarbre/supercinemarbre.github.io#61

Open

murisans mentioned this issue Jun 7, 2023

[compatibility] 兼容性问题 node.js v17 以上版本程序启动失败 kingdee/kdesign#423

Closed

Sangeetha-Bheeman mentioned this issue Oct 12, 2023

Added --openssl-legacy-provide to NODE_OPTIONS on serve and build scripts in package.json sanger/quanthub#265

Merged

theJsBegin added a commit to theJsBegin/AngularTest that referenced this issue Dec 4, 2023

Add files via upload

2c29832

vuejs/vue-cli#6770

mikaelsvensson mentioned this issue Dec 12, 2023

Fix ERR_OSSL_EVP_UNSUPPORTED issue tunnelbanejakten/tunnelbanejakten-web-app#157

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Impossible to serve with Node v17.0.1 #6770

Impossible to serve with Node v17.0.1 #6770

Miguel-Bento-Github commented Oct 21, 2021

sodatea commented Oct 21, 2021

wunderdaz commented Oct 21, 2021

sodatea commented Oct 26, 2021

mrichman commented Nov 4, 2021

cyber-netics commented Nov 7, 2021

paulxtiseo commented Nov 9, 2021 •

edited

sergiocabral commented Nov 16, 2021

paulxtiseo commented Nov 19, 2021

mhavid commented Nov 30, 2021

Miguel-Bento-Github commented Nov 30, 2021

K4L231 commented Dec 2, 2021

jaredmeadowsLB commented Jan 10, 2022

ffmit commented Jan 17, 2022

raja-chaudhary commented Jan 18, 2022

wunderdaz commented Jan 18, 2022

Voucik commented Jan 30, 2022

Sazzad-Saju commented Feb 3, 2022

larodiel commented Feb 15, 2022

avi9111 commented Apr 30, 2022

kamalud commented Nov 26, 2022

leolux commented Mar 18, 2023

MarcelJurtz commented Mar 19, 2023

Gurushesh-Metapercept commented Jun 14, 2023

Glideh commented Sep 26, 2023

coreysyms commented Oct 25, 2023 •

edited

ramrasu88 commented Jan 17, 2024

Impossible to serve with Node v17.0.1 #6770

Impossible to serve with Node v17.0.1 #6770

Comments

Miguel-Bento-Github commented Oct 21, 2021

Version

Environment info

Steps to reproduce

What is expected?

What is actually happening?

sodatea commented Oct 21, 2021

wunderdaz commented Oct 21, 2021

sodatea commented Oct 26, 2021

mrichman commented Nov 4, 2021

cyber-netics commented Nov 7, 2021

paulxtiseo commented Nov 9, 2021 • edited

sergiocabral commented Nov 16, 2021

paulxtiseo commented Nov 19, 2021

mhavid commented Nov 30, 2021

Miguel-Bento-Github commented Nov 30, 2021

K4L231 commented Dec 2, 2021

jaredmeadowsLB commented Jan 10, 2022

ffmit commented Jan 17, 2022

raja-chaudhary commented Jan 18, 2022

wunderdaz commented Jan 18, 2022

Voucik commented Jan 30, 2022

Sazzad-Saju commented Feb 3, 2022

larodiel commented Feb 15, 2022

avi9111 commented Apr 30, 2022

kamalud commented Nov 26, 2022

leolux commented Mar 18, 2023

MarcelJurtz commented Mar 19, 2023

Gurushesh-Metapercept commented Jun 14, 2023

Glideh commented Sep 26, 2023

coreysyms commented Oct 25, 2023 • edited

ramrasu88 commented Jan 17, 2024

paulxtiseo commented Nov 9, 2021 •

edited

coreysyms commented Oct 25, 2023 •

edited