Error:0308010C:digital envelope routines::unsupported

[Manuel-Suarez-Abascal]

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.

[Kurzdor]

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:

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

[nicholasrobertson]

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]

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]

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

[cryptiswap-admin]

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

[TadRodgers]

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]

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

[Emekaony]

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]

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 :(