Error:0308010C:digital envelope routines::unsupported #11708

Manuel-Suarez-Abascal · 2021-12-03T02:28:12Z

Describe the bug

I installed the latest Node version, currently, it's 17.2.0. When I try to start the project in development mode with the command npm run start, it throws an error & it's unable to start the project for development.

Pre-requisites:

Node's version 17.2.0.
NPM's version 8.1.41.
OS: Window 11
CLI: Windows PowerShell

Steps to reproduce:

run the command npx create-react-app hello-world
navigate to the project's root & run the command: npm run start

Expected results

It was expected to compile in dev mode & launch React's app in the browser like in the screenshot below: ( which it's using Node's version 16.13.1)

Actual results

It doesn't compile & it throws the following error instead:

Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:67:19)
    at Object.createHash (node:crypto:130:10)
    at module.exports (C:\Users\manue\Desktop\projects\hello-world\node_modules\webpack\lib\util\createHash.js:135:53)
    at NormalModule._initBuildHash (C:\Users\manue\Desktop\projects\hello-world\node_modules\webpack\lib\NormalModule.js:417:16)
    at handleParseError (C:\Users\manue\Desktop\projects\hello-world\node_modules\webpack\lib\NormalModule.js:471:10)
    at C:\Users\manue\Desktop\projects\hello-world\node_modules\webpack\lib\NormalModule.js:503:5
    at C:\Users\manue\Desktop\projects\hello-world\node_modules\webpack\lib\NormalModule.js:358:12
    at iterateNormalLoaders (C:\Users\manue\Desktop\projects\hello-world\node_modules\loader-runner\lib\LoaderRunner.js:214:10)
    at iterateNormalLoaders (C:\Users\manue\Desktop\projects\hello-world\node_modules\loader-runner\lib\LoaderRunner.js:221:10)
C:\Users\manue\Desktop\projects\hello-world\node_modules\react-scripts\scripts\start.js:19
  throw err;
  ^

Error: error:0308010C:digital envelope routines::unsupported
    at Object.createHash (node:crypto:130:10)
    at module.exports (C:\Users\manue\Desktop\projects\hello-world\node_modules\webpack\lib\util\createHash.js:135:53)
    at NormalModule._initBuildHash (C:\Users\manue\Desktop\projects\hello-world\node_modules\webpack\lib\NormalModule.js:417:16)
    at C:\Users\manue\Desktop\projects\hello-world\node_modules\webpack\lib\NormalModule.js:452:10
    at C:\Users\manue\Desktop\projects\hello-world\node_modules\webpack\lib\NormalModule.js:323:13
    at C:\Users\manue\Desktop\projects\hello-world\node_modules\loader-runner\lib\LoaderRunner.js:367:11
    at C:\Users\manue\Desktop\projects\hello-world\node_modules\loader-runner\lib\LoaderRunner.js:233:18
    at context.callback (C:\Users\manue\Desktop\projects\hello-world\node_modules\loader-runner\lib\LoaderRunner.js:111:13)
    at C:\Users\manue\Desktop\projects\hello-world\node_modules\babel-loader\lib\index.js:59:103 {
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

This is a screenshot of the issue:

Workaround

uninstall Node's version 17.2.0
install Node's version 16.13.1
run npm run start

The app should compile now.

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

Kurzdor · 2021-12-03T05:00:45Z

I am having the same issue with Windows 10 21H1 (19048.1348), WSL 2 (Ubuntu 20.04.3 LTS) and Node 17.0.1.

We have ~~two~~ three workarounds:

Use --openssl-legacy-provider argument in start script in package.json, but it is not recommended!
Downgrade Node to latest v16 like was mentioned in issue
Wait for CRA v5 or try CRA@next tag

nicholasrobertson · 2021-12-05T22:13:03Z

While you wait for a new CRA version, you can run Node version 16 without uninstalling version 17 using nvm

nvm install 16.13.0
nvm run 16.13.0

Have a look at creating a .nvmrc file in your projects root.
https://github.com/nvm-sh/nvm#nvmrc

I assume the issue is CRA using webpack-v4 and is resolved upgrading to v5 ( I haven’t actually validated this ) (#14532)
#11563
#11562

stale · 2022-01-08T22:59:50Z

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.

aaliya-shaikh · 2022-01-11T07:43:49Z

Came across the same bug.
OS: Ubuntu 20.0.4
node: v17.3.1
npm: 8.3.0

cryptiswap-admin · 2022-01-12T10:25:08Z

I'm also experiencing this problem with the latest version of nodejs and NPM:
node: v17.3.1
npm: 8.3.0

TadRodgers · 2022-01-13T14:00:34Z

I'm having the same issue within CentOs Stream Version 9:
node: v17.3.0
npm: 8.3.0

My work around was to down-grade Node:

$ npm install -g n
$ n 16.13.1

$ nvm install 16.13.1
$ nvm use 16.13.1

Then I was able to continue with the build process.

jmgtan · 2022-01-17T02:20:24Z

Running react build also triggers this problem. The only workaround right now is to use Node 16.x

Emekaony · 2022-01-21T18:39:00Z

Just as @TadRodgers and @Manuel-Suarez-Abascal mentioned: downgrading node is probably the best way to go. Did that and everything is working just fine now.

I used:

npm uninstall node to uninstall node
npm install node@16.13.1 to install node at that specific version
then source ./bash_profile to do some shell magic in order to register my current session with the current installation.

rhythmshandlya · 2022-01-29T08:00:29Z

While you wait for a new CRA version, you can run Node version 16 without uninstalling version 17 using nvm

nvm install 16.13.0 nvm run 16.13.0

Have a look at creating a .nvmrc file in your projects root. https://github.com/nvm-sh/nvm#nvmrc

I assume the issue is CRA using webpack-v4 and is resolved upgrading to v5 ( I haven’t actually validated this ) (#14532) #11563 #11562

workaround is not what I am looking for rn :(

nicholasrobertson · 2022-01-29T12:13:22Z

While you wait for a new CRA version, you can run Node version 16 without uninstalling version 17 using nvm
nvm install 16.13.0 nvm run 16.13.0
Have a look at creating a .nvmrc file in your projects root. https://github.com/nvm-sh/nvm#nvmrc
I assume the issue is CRA using webpack-v4 and is resolved upgrading to v5 ( I haven’t actually validated this ) (#14532) #11563 #11562

workaround is not what I am looking for rn :(

Haha, @rhythmshandlya You can try the Alpha release that supports webpack v5 and see if you get the same error. I'm sure the devs would appreciate the testing feedback.

npx create-react-app@next --scripts-version=@next --template=cra-template@next my-js-app

#11278
#9994

maulik-modi · 2022-02-14T06:19:44Z

I faced this error on Windows 10 as well as Ubuntu due to Node version 17.
Yes, I simply switched to nvm 16.13.0 and it started running. Thanks @nicholasrobertson , it worked like a charm!

RodrigoTomeES · 2022-03-06T19:54:36Z

Hi,

I am using CRA 5 and I am having the same error, Do you know when it will be fixed?

Thanks!

maulik-modi · 2022-03-08T10:45:43Z

@RodrigoTomeES , is there any reason to use Node V17 over Node 16 LTS?

RodrigoTomeES · 2022-03-08T11:07:48Z

@maulik-modi Hi, I am using this new feature from Node 17.

 import config from './sample.config.json' assert { type: 'json' };

ghost · 2022-03-10T10:47:19Z

I got this error while importing svg (import logo from './logo.svg';).
running npm update loader-utils solved it.

skulas · 2022-03-29T14:14:46Z

In our case, we didn't downgrade node and kept v17.x but we added this to the package.json build command:
--openssl-legacy-provider

ianw · 2022-08-18T23:51:02Z

Just for anyone finding this; it's not exclusively a v17.x issue, but depends on the system openssl version. For example I hit this on Fedora 36 with the packaged version of nodejs (16.14.0) -- this doesn't have the --openssl-legacy-provider tag. I ended up installing an alternative version with nvm --install lts

Tonya713MS · 2022-10-05T06:14:10Z

cd into your newly created app directory run the following
Run:
npm install -g npm-check-updates

Then:
ncu -u

Then:
npm install

Then:
npm start

filssavi · 2022-10-10T14:23:53Z

I am encountering this bug on a clean Ubuntu 22.04 machine with the lastest CRA (5.0.1).
Unfortunately I have neither the time, nor the capabilities to investigate this bug, any further.

Are there any news on when it should be fixed?

SOUMOJIT-CHAKRABORTY · 2022-10-20T21:32:07Z

nvm install 16.13.1

Thanks, it helped me to resolve my issue😊

JaffParker · 2022-10-26T16:37:05Z

Lol installing 16.13.1 and then reinstalling node_modules results in:

Internal Error: Unable to deserialize cloned data due to invalid or unsupported version.
    at Object.deserialize (node:v8:344:7)
    at Ke.restoreInstallState (/home/andrey/Code/cashflowio/.yarn/releases/yarn-3.1.1.cjs:447:965)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async LC.execute (/home/andrey/Code/cashflowio/.yarn/releases/yarn-3.1.1.cjs:561:1879)
    at async LC.validateAndExecute (/home/andrey/Code/cashflowio/.yarn/releases/yarn-3.1.1.cjs:337:620)
    at async oo.run (/home/andrey/Code/cashflowio/.yarn/releases/yarn-3.1.1.cjs:351:1846)
    at async oo.runExit (/home/andrey/Code/cashflowio/.yarn/releases/yarn-3.1.1.cjs:351:2013)
    at async i (/home/andrey/Code/cashflowio/.yarn/releases/yarn-3.1.1.cjs:448:12377)
    at async r (/home/andrey/Code/cashflowio/.yarn/releases/yarn-3.1.1.cjs:448:10617)

On the other hand, adding the --openssl-legacy-provider flag adds more errors. Now I've reinstalled my latest node so at least I'm done to one error and broken hot reloading, and instead I'm up to 52 errors, broken everything and can't work.

whyprax · 2022-11-04T17:15:16Z

Lol installing 16.13.1 and then reinstalling node_modules results in:

Internal Error: Unable to deserialize cloned data due to invalid or unsupported version.
    at Object.deserialize (node:v8:344:7)
    at Ke.restoreInstallState (/home/andrey/Code/cashflowio/.yarn/releases/yarn-3.1.1.cjs:447:965)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async LC.execute (/home/andrey/Code/cashflowio/.yarn/releases/yarn-3.1.1.cjs:561:1879)
    at async LC.validateAndExecute (/home/andrey/Code/cashflowio/.yarn/releases/yarn-3.1.1.cjs:337:620)
    at async oo.run (/home/andrey/Code/cashflowio/.yarn/releases/yarn-3.1.1.cjs:351:1846)
    at async oo.runExit (/home/andrey/Code/cashflowio/.yarn/releases/yarn-3.1.1.cjs:351:2013)
    at async i (/home/andrey/Code/cashflowio/.yarn/releases/yarn-3.1.1.cjs:448:12377)
    at async r (/home/andrey/Code/cashflowio/.yarn/releases/yarn-3.1.1.cjs:448:10617)

On the other hand, adding the --openssl-legacy-provider flag adds more errors. Now I've reinstalled my latest node so at least I'm done to one error and broken hot reloading, and instead I'm up to 52 errors, broken everything and can't work.

Adding the --openssl-legacy-provider worked for me.

Steps to resolve the issue using --openssl-legacy-provider :

update your start script in package.json to use react-scripts --openssl-legacy-provider start

It should look like this :
"start": "react-scripts --openssl-legacy-provider start",

kalpeshsuthar12 · 2022-11-06T09:09:33Z

first, check your local System version for npm ( npm -v ) and node ( node -v ) and add in your package.json
"engines": {
"node": "YOUR_SYSTEM_NODE_VERISON",
"npm": "YOUR_SYSTEM_NPM_VERISON"
}

KonstantinLukaschenko · 2022-11-06T11:33:26Z

Updating loader-utils from 2.0.0 to 2.0.1 or above in yarn.lock worked for me.

loader-utils added support for Node.js 17 in webpack/loader-utils#193

d3x0r · 2022-11-13T01:12:49Z

I find this works to just use node 18....
set NODE_OPTIONS=--openssl-legacy-provider

samjundi · 2022-11-30T06:37:38Z

**Tonya713MS ** commented Oct 5, 2022

it works with react projects. many thanks

naz-i-ya · 2023-01-09T06:30:17Z

I am struggling with this too....
- node v19.3.0
- npm v9.2.0
- yarn v1.22.17

I tried to run my @react app and got Error:0308010C:digital envelope routines::unsupported.
I've spent a few hours searching around and can't find a solid answer to the problem.
Is there any other solution without downgrading node version...?
Thanks..!!

julianD77 · 2023-01-10T07:57:18Z

Have you tried setting this ENV VAR?

NODE_OPTIONS=--openssl-legacy-provider

I haven't tried it against node v19 yet but it works for us on node 18.4.0 and on macos

Note however that for us this needs to be just a temporary solution until the issue is resolved in the underlying dependency since its likely we want to be able to use to non-legacy openssl provider in the long term

moedayraki · 2023-01-10T12:03:26Z

@julianD77 I've tried that and it's still the same problem for me.

mrfourking · 2023-01-12T09:29:59Z

I got this error while importing svg (import logo from './logo.svg';). running npm update loader-utils solved it.

It`s worked for me

smanrog-tekinforkom · 2023-03-07T15:43:18Z

when i start in termux app(android) it goes error like this too

Error: error:0308010C:digital envelope routines::unsupported at new Hash (node:internal/crypto/hash:71:19) at Object.createHash (node:crypto:140:10) at module.exports (/data/data/com.termux/files/home/react/web-chat-pingo/node_modules/webpack/lib/util/createHash.js:135:53) at NormalModule._initBuildHash (/data/data/com.termux/files/home/react/web-chat-pingo/node_modules/webpack/lib/NormalModule.js:417:16) at /data/data/com.termux/files/home/react/web-chat-pingo/node_modules/webpack/lib/NormalModule.js:452:10 at /data/data/com.termux/files/home/react/web-chat-pingo/node_modules/webpack/lib/NormalModule.js:323:13 at /data/data/com.termux/files/home/react/web-chat-pingo/node_modules/loader-runner/lib/LoaderRunner.js:367:11 at /data/data/com.termux/files/home/react/web-chat-pingo/node_modules/loader-runner/lib/LoaderRunner.js:233:18 at context.callback (/data/data/com.termux/files/home/react/web-chat-pingo/node_modules/loader-runner/lib/LoaderRunner.js:111:13) at /data/data/com.termux/files/home/react/web-chat-pingo/node_modules/babel-loader/lib/index.js:59:103 { opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ], library: 'digital envelope routines', reason: 'unsupported', code: 'ERR_OSSL_EVP_UNSUPPORTED' }

maybe it just unsupported on babel loader CMIIW

Desarrollos-Web-Urquiza · 2023-04-28T23:01:30Z

Lol installing 16.13.1 and then reinstalling node_modules results in:
Internal Error: Unable to deserialize cloned data due to invalid or unsupported version.
    at Object.deserialize (node:v8:344:7)
    at Ke.restoreInstallState (/home/andrey/Code/cashflowio/.yarn/releases/yarn-3.1.1.cjs:447:965)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async LC.execute (/home/andrey/Code/cashflowio/.yarn/releases/yarn-3.1.1.cjs:561:1879)
    at async LC.validateAndExecute (/home/andrey/Code/cashflowio/.yarn/releases/yarn-3.1.1.cjs:337:620)
    at async oo.run (/home/andrey/Code/cashflowio/.yarn/releases/yarn-3.1.1.cjs:351:1846)
    at async oo.runExit (/home/andrey/Code/cashflowio/.yarn/releases/yarn-3.1.1.cjs:351:2013)
    at async i (/home/andrey/Code/cashflowio/.yarn/releases/yarn-3.1.1.cjs:448:12377)
    at async r (/home/andrey/Code/cashflowio/.yarn/releases/yarn-3.1.1.cjs:448:10617)
On the other hand, adding the --openssl-legacy-provider flag adds more errors. Now I've reinstalled my latest node so at least I'm done to one error and broken hot reloading, and instead I'm up to 52 errors, broken everything and can't work.
Adding the --openssl-legacy-provider worked for me.

Steps to resolve the issue using --openssl-legacy-provider :

update your start script in package.json to use react-scripts --openssl-legacy-provider start

It should look like this : "start": "react-scripts --openssl-legacy-provider start",

This works for me!

rhiskey · 2023-05-03T05:29:54Z

cd into your newly created app directory run the following Run: npm install -g npm-check-updates

Then: ncu -u

Then: npm install

Then: npm start

This one works perfectly well!

I installed `npm install node@14.17.6 --save-exact`. I think subsequent `node install` should use exact node version because the former added `node: 14.17.6,` as a dependency in `package.json` For a more recent node version two things need to happen: - `node-sass` complained, so needs to be replaced with `sass` (e.g.^1.64.1) which is implemented with dart (pure-JavaScript package built from the Dart Sass) - node 17 needs openSSL dependency for crypto module (is used by webpack server or sth like that). I could consider moving to vite instead of webpack facebook/create-react-app#11708 https://stackoverflow.com/questions/73144960/error-error0308010cdigital-envelope-routinesunsupported-at-new-hash-nodei

baptooo · 2023-12-07T09:15:37Z

Hello, if this can help future people encountering this issue.
The problem seems to be at loader-utils library level and this was patched on version 2.0.1

Here is the fix:
webpack/loader-utils#193

On my project I specified a resolution for this dependency and it's working perfectly without the need for specifying Node's NODE_OPTIONS=--openssl-legacy-provider option.

Extract from package.json:

{
  "name": "My project",
  "version": "1.0.0",
  "dependencies": {
    "react-scripts": "^5.0.1",
    ...
  },
+  "resolutions": {
+    "loader-utils": "^2.0.1"
+  }
}

Manuel-Suarez-Abascal added issue: bug report needs triage labels Dec 3, 2021

stale bot added the stale label Jan 8, 2022

stale bot removed the stale label Jan 11, 2022

jkanche mentioned this issue Jan 12, 2022

Local instance fails to start, code: 'ERR_OSSL_EVP_UNSUPPORTED' kanaverse/kana#81

Closed

txk2048 mentioned this issue Jan 23, 2022

Error launching dev server preactjs/preact-cli#1643

Closed

aaliya-shaikh mentioned this issue Feb 14, 2022

npm start fails cometchat/cometchat-sample-app-react#66

Closed

romfrancois mentioned this issue Feb 14, 2022

[React Typescript] Problem initializing application tradingview/charting-library-examples#274

Closed

chinmaym07 mentioned this issue Feb 25, 2022

[UI] make build-ui gives error in Node.js v17.6.0 meshery/meshery#5125

Closed

michaelbromley mentioned this issue May 4, 2022

error:0308010C:digital envelope routines::unsupported vuestorefront-community/vendure#208

Closed

alexs-mparticle mentioned this issue Jun 21, 2022

fix: Update support for Node 17 mParticle/mparticle-web-sample-apps#152

Draft

peytondmurray mentioned this issue Aug 19, 2022

[Dashboard] Failure to build for node>=v17 ray-project/ray#28023

Closed

timroes mentioned this issue Dec 9, 2022

🪟🔧 Fix node version on CI airbytehq/airbyte#20287

Merged

salman90 mentioned this issue Mar 22, 2023

Error: error:0308010C:digital envelope routines::unsupported Azure-Samples/ms-identity-javascript-react-spa#37

Closed

striderkein mentioned this issue Sep 25, 2023

Dockerize striderkein/eaglys-web#11

Closed

hideokamoto-stripe mentioned this issue Jan 16, 2024

Stripe CLI setup Fixed Priced Subs with Node + React not working stripe-samples/subscription-use-cases#730

Open

This was referenced Jan 24, 2024

Upgrading react version to 18 in examples generated via cli as Stripe already supports its stripe-samples/accept-a-payment#1979

Open

Replace React example from CRA to Vite stripe-samples/accept-a-payment#2251

Open

Error:0308010C:digital envelope routines::unsupported #11708

Error:0308010C:digital envelope routines::unsupported #11708

Comments

Manuel-Suarez-Abascal commented Dec 3, 2021

Describe the bug

Pre-requisites:

Steps to reproduce:

Expected results

Actual results

Workaround

Kurzdor commented Dec 3, 2021 • edited

nicholasrobertson commented Dec 5, 2021 • edited

stale bot commented Jan 8, 2022

aaliya-shaikh commented Jan 11, 2022

cryptiswap-admin commented Jan 12, 2022

TadRodgers commented Jan 13, 2022 • edited

jmgtan commented Jan 17, 2022

Emekaony commented Jan 21, 2022 • edited

rhythmshandlya commented Jan 29, 2022

nicholasrobertson commented Jan 29, 2022 • edited

maulik-modi commented Feb 14, 2022 • edited

RodrigoTomeES commented Mar 6, 2022

maulik-modi commented Mar 8, 2022

RodrigoTomeES commented Mar 8, 2022

ghost commented Mar 10, 2022

skulas commented Mar 29, 2022 • edited

ianw commented Aug 18, 2022

Tonya713MS commented Oct 5, 2022

filssavi commented Oct 10, 2022

SOUMOJIT-CHAKRABORTY commented Oct 20, 2022

JaffParker commented Oct 26, 2022 • edited

whyprax commented Nov 4, 2022

kalpeshsuthar12 commented Nov 6, 2022

KonstantinLukaschenko commented Nov 6, 2022 • edited

d3x0r commented Nov 13, 2022

samjundi commented Nov 30, 2022

**Tonya713MS ** commented Oct 5, 2022

naz-i-ya commented Jan 9, 2023

julianD77 commented Jan 10, 2023 • edited

moedayraki commented Jan 10, 2023

mrfourking commented Jan 12, 2023

smanrog-tekinforkom commented Mar 7, 2023 • edited

Desarrollos-Web-Urquiza commented Apr 28, 2023

rhiskey commented May 3, 2023

baptooo commented Dec 7, 2023

Kurzdor commented Dec 3, 2021 •

edited

nicholasrobertson commented Dec 5, 2021 •

edited

TadRodgers commented Jan 13, 2022 •

edited

Emekaony commented Jan 21, 2022 •

edited

nicholasrobertson commented Jan 29, 2022 •

edited

maulik-modi commented Feb 14, 2022 •

edited

skulas commented Mar 29, 2022 •

edited

JaffParker commented Oct 26, 2022 •

edited

KonstantinLukaschenko commented Nov 6, 2022 •

edited

Tonya713MS commented Oct 5, 2022

julianD77 commented Jan 10, 2023 •

edited

smanrog-tekinforkom commented Mar 7, 2023 •

edited