Error 0308010c digital envelope routines unsupported что делать

If you are facing this error and you do not want to change your main configuration, an easy fix would be to use the following approach. I am not sure if it is recommended as a good practice, though.

Feel free to correct it.

Initially, let’s say this is the scripts section of my package.json file:

...
"version": "1.0.0",
  "scripts": {
    ...
    "build": "npm run build:test-app:testing",
    "build:test-app:testing": "ng build test-app --deploy-url  https://test-app.com/ --configuration=test-config",
    ...
  },
  "private": true,
...

In order to use this export NODE_OPTIONS=--openssl-legacy-provider you can do the following:

"version": "1.0.0",
  "scripts": {
....
    "build": "NODE_OPTIONS=--openssl-legacy-provider npm run build:test-app:testing”,
    "build:test-app:testing": "NODE_OPTIONS=--openssl-legacy-provider ng build test-app --deploy-url  https://test-app.com/ --configuration=test-config"
...
  },
  "private": true,

Take note of the build scripts. I have added an option: NODE_OPTIONS=--openssl-legacy-provider

This helps solve this error in Node.js version 17.

For those with the flexibility of changing the build system’s Node.js version, just switch to a version lower that 17, e.g., version 16.

For Docker, the use case of using this initially, which always pulls the latest version:

...
FROM node:alpine
...

You can switch to something like:

...
FROM node:16-alpine3.12
...

How To Fix Error – “Digital Envelope Routines::Unsupported” in Node.js or React ?

How To Fix Error – “Digital Envelope Routines::Unsupported” in Node.js or React ?

In this post, we will see How To Fix Error – “Digital Envelope Routines::Unsupported” in Node.js, React.js, Angular.js, Vue.js, Docker etc. Various facets of the error –

The common reason for such issue is Version conflict issue or Version not in-sync with other entities in the system. Sometimes using latest Node.js might throw such error. Lot of projects still depend on Webpack 4 but the latest Node.js might not be compatible with that. Majorly this is caused by the latest Node.js Version compatible issues with OpenSSL.

Check you node version

We will try out the below two options to see if that helps to fix the issue.

Option 1:

If you want to stick to your existing Node.js without down-grading it, then try the below steps –

• Use openssl-legacy-provider by setting it as an environment variable

• • Windows – Set below as environment variable

• • MacLinux – Set below in

    /.bashrc so that it stays even after you logoutlogin back.

• • For Docker – add the Highlighted bit in Dockekrfile

• The openssl-legacy-provider parameter should be placed inside your package.json. Add the part highlighted in Red.

• • For Angular, use the below and then use npm start

• • For React, use the below in the package.json file.

• For Vue.js, use the below in the package.json file.

• Also add something like the below Highlighted –

Option 2:

At this point, I am assuming Option 1 somehow did not work out to fix the issue. The next option we can try is to roll-back to an older version of Node.js (STABLE) which is compatible with Webpack and doesn’t render this issue.

• The version that you are using might not be compatible with some Webpack components.

• Remove the current Node.js version and go-back i.e. Downgrade to an older Stable version. e.g. From Node.js 17+ go back to Node.js version 16+.
  • Windows – Uninstall node from the “Add or remove programs”. Alternatively use https://docs.microsoft.com/en-us/windows/dev-environment/javascript/nodejs-on-windows to setup nvm and control Node version through it

• • LinuxMac –

• Once done, cross check if node version is downgraded

• Delete the folder “node_modules” .

Источник

Сообщение об ошибке «ошибка: 0308010C: подпрограммы цифрового конверта :: не поддерживаются»

Я создал проект IntelliJ IDEA React по умолчанию и получил следующее:

34 ответа

В вашем package.json: измените эту строку

Если мы используем текущую LTS-версию Node.js, то этой ошибки не будет. Понизьте версию Node.js до текущей версии LTS (16.13.0).

Установить требуемую версию можно несколькими способами. Один из них использует nvm (менеджер версий Node.js).

Шаг 2: nvm install 16.13.0 (или lts)

Это версия для Node.js.

У меня есть эта ошибка на Node.js 17, но это нормально, когда я переключаю свою версию Node.js на более старую версию (16) с помощью nvm .

Некоторые популярные ответы не помогли.

И некоторые популярные ответы были неприменимы, изменяя файл package.json :

Это вызвано последними проблемами совместимости node.js V17 с OpenSSL , см. this и эту проблему на GitHub.

Самый простой способ — просто перейти с node.js V17 на node.js V16 . См. этот пост о том, как перейти на более раннюю версию node.js .

Я нашел следующие команды на GitHub:

Для Windows используйте следующую команду в cmd:

Для Unix используйте:

Опасность

На этот вопрос есть более 30 ответов, большинство из которых предлагают либо понизить версию Node.js до предыдущей версии 17, либо использовать устаревшего поставщика SSL. Оба эти решения представляют собой взломы, которые оставляют ваши сборки открытыми для угроз безопасности.

Причина ошибки

В Node.js v17 разработчики Node.js закрыли дыру в безопасности поставщика SSL. Это исправление было критическим изменением, которое соответствовало аналогичным критическим изменениям в пакетах SSL в NPM. Когда вы пытаетесь использовать SSL в Node.js v17 или более поздней версии без обновления этих пакетов SSL в вашем package.json , вы увидите эту ошибку.

Правильное (безопасное) решение

Используйте последнюю версию Node.js, а также пакеты с последними исправлениями безопасности.

Для многих людей следующая команда решит проблему:

Однако имейте в виду, что для сложных сборок приведенная выше команда будет использовать критические исправления безопасности, которые могут потенциально нарушить вашу сборку.

Если вы используете react-scripts , теперь вы можете просто обновиться до версии 5.0.0 (или выше), которая, похоже, устранила эту проблему (включает более новую версию веб-пакета).

Это распространенная ошибка, когда пакеты в проекте не обновляются и версия React, которую вы используете, не является последней.

Чтобы решить эту проблему, вам нужно изменить файл package.json следующим образом: изменить это 👇

Я столкнулся с той же проблемой с Node.js 17.0.1. Я решил это, выполнив следующие действия:

Откройте Панель управления → Программа и компоненты → Node.js и удалите Node.js, щелкнув правой кнопкой мыши

Перейдите на веб-сайт https://nodejs.org/en/ и загрузите версия и установка.

И загрузите рекомендованную версию для большинства пользователей.

Затем удалите Node.js со своего ПК и установите рекомендуемую версию.

Насколько я понимаю, это проблема команды разработчиков. Они исправят это как можно скорее, но пока используйте рекомендованную версию, и все будет в порядке.

Если вы получаете эту ошибку при использовании GatsbyJs, все, что вам нужно сделать, это понизить версию node до долгосрочной поддержки. Нет другого спасения

Это не может быть ответом на вопрос для всех. Но для тех, кто использует узел 17 и выше в докере, понижение версии, как все говорили, будет полезно. Нет необходимости в open-legacy-sslprovider. Простой переключатель в вашем Dockerfile от использования

Исправляет эту проблему в докере.

Для угловых приложений:

Вы также можете отредактировать скрипт npm start в package.json. Вместо

Когда вы запускаете npm run start в терминале/командной строке, он сначала установит NODE_OPTIONS , чтобы избежать проблемы.

Он работал с Node.js v18.7.0.

Сегодня я столкнулся с этой проблемой и решил ее, переключив версию Node.js с помощью nvm.

Я работал над парой личных проектов, используя Node.js, Next.js и React. Со мной часто случается то, что я не помню точно, какая версия Node .js я использую для какого проекта.

И поэтому обычно я пытался использовать Node.js 16 для проекта, который в настоящее время использует Node.js 14 (сейчас я использую Node.js 17).

Я не придумал лучшего способа запомнить версию Node.js для каждого проекта, поэтому обычно я просто сохранял все команды, которые мне нужно было запустить для запуска приложения, в readme.MD.

Если вы столкнулись с этой ошибкой и не хотите изменять свою основную конфигурацию, простым решением будет использование следующего подхода. Однако я не уверен, рекомендуется ли это в качестве хорошей практики.

Не стесняйтесь исправлять.

Сначала предположим, что это раздел сценариев моего файла package.json :

Чтобы использовать этот export NODE_OPTIONS=—openssl-legacy-provider , вы можете сделать следующее:

Обратите внимание на сценарии сборки. Я добавил вариант: NODE_OPTIONS=—openssl-legacy-provider

Это помогает решить эту ошибку в Node.js версии 17.

Для тех, у кого есть возможность изменить версию системы сборки Node.js, просто переключитесь на версию ниже 17, например, версию 16.

Для Docker вариант использования изначально, который всегда извлекает последнюю версию:

Вы можете переключиться на что-то вроде:

Та же ошибка с версией узла v18.0.0 и версии nuxt framework 2.15 при запуске сервера разработки и будет исправлено:

Я столкнулся с теми же ошибками при сборке hoppscotch с помощью Node.js v18.4.0, и set NODE_OPTIONS=—openssl-legacy-provider спас меня!

Это сработало для меня в моем приложении expo (переход с Node.js 17 на Node.js 12 или 14).

Если у вас установлен nvm, вы можете изменить версию узла:

Сначала проверьте версии Node.js в nvm:

Во-вторых, установите версию 12 или 14:

Не удалось построить преобразователь: ошибка: ошибка: 0308010C: подпрограммы цифрового конверта :: неподдерживаемый

Самым простым и легким решением указанной выше ошибки является понижение версии Node.js до версии 14.18.1. А затем просто удалите папку node_modules и попробуйте перестроить свой проект, и ваша ошибка должна быть решена.

Это сработало для меня (переход с Node.js 17 на Node.js 16):

Затем откатитесь к узлу —lts (узел v16.13.2 (npm v8.1.2)) для этого используйте nvm

Для оболочки bash

Для оболочки зш

После установки нвм

Это решение сработало для меня.

Эта ошибка возникает в Node.js версии 17+, поэтому попробуйте понизить версию Node.js.

1. Удалите Node.js с компьютера.
2. Загрузите Node.js версии 16 и установите его снова с https://nodejs.org/. скачать/релиз/v16.13.0/

Эта ошибка связана с тем, что node.js 17 использует OpenSSL3, который изменил код для контекста инициализации семейства md (включая md4), и это критическое изменение. Ошибка также может возникнуть, если вы создаете приложение с помощью сборки докеров, поскольку по умолчанию он загружает последнюю версию Node.JS.

Установите диспетчер версий узла nvm:

Установите последнюю LTS-версию:

Я столкнулся с этой проблемой в сборке Docker, и я добавил эту строку в файл Docker:

Для локальной разработки добавьте переключатель в файл package.json .

Запуск аудита решил проблему для меня

Была эта проблема при использовании VueJS.

Недостатком использования -openssl-legacy-provider является то, что оно не поддерживается более старыми версиями Node. Старые версии Node просто не запускаются, когда указан этот флаг.
Но я по-прежнему хочу обеспечить совместимость с Node v16 и более ранними версиями.

VueJS использует алгоритм md4 для генерации хэшей (на самом деле это WebPack под капотом). md4 можно легко заменить на md5 для таких целей. Тип используемого алгоритма в большинстве случаев жестко запрограммирован, поэтому нет возможности настроить другой алгоритм.

Поэтому я придумал другой обходной путь. Функция, которая перехватывает исходный вызов createHash() из модуля crypto и заменяет его модифицированной версией. Это начало моего файла vue.config.js :

Вот два варианта сейчас —

1. Попробуйте удалить Node.js версии 17+ и переустановить Node.js версии 16+.

Вы можете переустановить текущую версию js узла LTS с их официального сайта. или более конкретные загрузки из здесь;

Вы можете использовать NVM (Диспетчер версий узла)

• Пользователи Linux и Mac могут использовать этот пакет nvm — https://github.com/nvm-sh/. нвм
• Пользователи Windows могут использовать этот пакет nvm — https://github.com/coreybutler/nvm-windows

2. Откройте терминал и вставьте их, как описано:

Источник

Error 0308010c digital envelope routines unsupported что делать

Reading time В· 4 min

error:0308010C:digital envelope routines::unsupported [Fixed] #

The «error:0308010C:digital envelope routines::unsupported» occurs because Node.js v17 and later use OpenSSL v3.0 which has had breaking changes. To resolve the error, set the NODE_OPTIONS environment variable to —openssl-legacy-provider when running your development server.

Open your terminal and run the specific command for your shell type.

The —openssl-legacy-provider option is needed when using the latest version of Node.js, because Node.js 17 and later uses OpenSSL 3.0 which has had some breaking changes.

If the error persists, try using the —openssl-legacy-provider flag when issuing the command in your package.json file.

Here is an example of how you would do that with create-react-app .

Simply add —openssl-legacy-provider at the end of your command.

If you get an error that «node: —openssl-legacy-provider is not allowed in NODE_OPTIONS», unset the NODE_OPTIONS environment variable and rerun the command.

Try to rerun your script after deleting the environment variable.

If that doesn’t help, try to set the NODE_OPTIONS environment variable right before issuing the command.

Install the cross-env package to resolve the error.

And prefix the environment variable and the command with cross-env .

We simply prefixed the command in the package.json script with NODE_OPTIONS=—openssl-legacy-provider , e.g. NODE_OPTIONS=—openssl-legacy-provider YOUR_COMMAND_HERE .

For example, for an Angular app, your package.json script would look similar to the following.

If you use create-react-app , update your react-scripts version because the package introduced some fixes regarding its Webpack config in version 5.0.0 .

Update your react-scripts version if you use create-react-app #

The «error:0308010C:digital envelope routines::unsupported» also occurs if you have an outdated version of react-scripts in your create-react-app project.

Open your terminal and run the following command to update your version of react-scripts .

If the error persists, try to delete your node_modules and package-lock.json (not package.json ) files, rerun the npm install and restart your dev server.

Try to restart your development server after updating your react-scripts version.

You can install a specific version using the following command.

The version of Webpack in react-scripts version 5.0.0+ has been updated which should resolve the issue in your create-react-app project.

Try updating your NPM packages #

The following command installs major updates to top-level dependencies, which might introduce breaking changes to your project if you rely on older package versions.

Updating the versions of your packages might solve the error because the maintainers might have introduced security patches in more recent versions.

If the error persists, try running the npm update command.

If you still get an error, try to delete your node_modules and package-lock.json , rerun the npm install command and restart your development server.

Try to restart your development server after running the npm audit fix —force command.

If none of the suggestions helped, you can downgrade your Node.js version to 16.13.0 to resolve the error.

Downgrade to Node.js version 16 #

You can issue the following command to downgrade your Node.js version to 16.13.0 if you use NVM.

The error often occurs when installing Node.js version 17+. Rolling back to version 16.X.X solves it.

The —openssl-legacy-provider option is needed when using the latest version of Node.js, because Node.js 17 and later uses OpenSSL 3.0 which has had some breaking changes.

If you still get the error after downgrading to Node version 16, try to delete your node_modules and package-lock.json , rerun the npm install command and restart your development server.

Restart your development server after issuing the npm install command.

Источник

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 (/Users/user/Programming Documents/WebServer/untitled/node_modules/webpack/lib/util/createHash.js:135:53)
    at NormalModule._initBuildHash (/Users/user/Programming Documents/WebServer/untitled/node_modules/webpack/lib/NormalModule.js:417:16)
    at handleParseError (/Users/user/Programming Documents/WebServer/untitled/node_modules/webpack/lib/NormalModule.js:471:10)
    at /Users/user/Programming Documents/WebServer/untitled/node_modules/webpack/lib/NormalModule.js:503:5
    at /Users/user/Programming Documents/WebServer/untitled/node_modules/webpack/lib/NormalModule.js:358:12
    at /Users/user/Programming Documents/WebServer/untitled/node_modules/loader-runner/lib/LoaderRunner.js:373:3
    at iterateNormalLoaders (/Users/user/Programming Documents/WebServer/untitled/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
    at iterateNormalLoaders (/Users/user/Programming Documents/WebServer/untitled/node_modules/loader-runner/lib/LoaderRunner.js:221:10)
/Users/user/Programming Documents/WebServer/untitled/node_modules/react-scripts/scripts/start.js:19
  throw err;
  ^

34 ответа

Лучший ответ

"start": "react-scripts start"

"start": "react-scripts --openssl-legacy-provider start"

export NODE_OPTIONS=--openssl-legacy-provider

"start": "react-scripts --openssl-legacy-provider start"

set NODE_OPTIONS=--openssl-legacy-provider

export NODE_OPTIONS=--openssl-legacy-provider

npm audit fix --force

"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "react-scripts test",
"eject": "react-scripts eject"

"scripts": {
"start": "react-scripts --openssl-legacy-provider start",
"build": "react-scripts --openssl-legacy-provider build",
"test": "react-scripts test",
"eject": "react-scripts eject"

From node

From node:16.* 

"start": "ng serve -o"

"start": "set NODE_OPTIONS=--openssl-legacy-provider && ng serve -o"

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

...
"version": "1.0.0",
  "scripts": {
    ...
    "build": "npm run build:test-app:testing",
    "build:test-app:testing": "ng build test-app --deploy-url  https://test-app.com/ --configuration=test-config",
    ...
  },
  "private": true,
...

"version": "1.0.0",
  "scripts": {
....
    "build": "NODE_OPTIONS=--openssl-legacy-provider npm run build:test-app:testing”,
    "build:test-app:testing": "NODE_OPTIONS=--openssl-legacy-provider ng build test-app --deploy-url  https://test-app.com/ --configuration=test-config"
...
  },
  "private": true,

...
FROM node:alpine
...

...
FROM node:16-alpine3.12
...

"scripts": {
  "dev": "NODE_OPTIONS=--openssl-legacy-provider nuxt"
}

D:coderusthoppscotch-apphoppscotch>pnpm install && pnpm run generate
Scope: all 5 workspace projects
Lockfile is up-to-date, resolution step is skipped
Already up-to-date
packages/codemirror-lang-graphql prepare$ rollup -c
│ Browserslist: caniuse-lite is outdated. Please run:
│   npx browserslist@latest --update-db
│   Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
│
│ src/index.js → dist/index.cjs, ./dist...
│ created dist/index.cjs, ./dist in 2.8s
└─ Done in 4.8s
packages/hoppscotch-data prepare$ tsup src --dts
[20 lines collapsed]
│ CJS distchunk-LZ75CAKS.js     13.00 B
│ DTS Build start
│ DTS ⚡️ Build success in 2261ms
│ DTS distindex.d.ts              714.00 B
│ DTS distrestindex.d.ts         2.18 KB
│ DTS distgraphqlindex.d.ts      589.00 B
│ DTS distcollectionindex.d.ts   1.30 KB
│ DTS distrestcontent-types.d.ts 473.00 B
│ DTS distrestHoppRESTAuth.d.ts  882.00 B
│ DTS disttype-utils.d.d.ts       1.00 B
└─ Done in 3.8s
packages/hoppscotch-js-sandbox postinstall$ pnpm run build
│ > @hoppscotch/js-sandbox@1.0.0 build D:coderusthoppscotch-apphoppscotchpackageshoppscotch-js-sandbox
│ > npx tsc
└─ Done in 8.7s
. prepare$ husky install
│ husky - Git hooks installed
└─ Done in 300ms
packages/hoppscotch-app postinstall$ pnpm run gql-codegen
[12 lines collapsed]
│ [14:58:01] Load GraphQL documents [started]
│ [14:58:01] Load GraphQL documents [completed]
│ [14:58:01] Generate [started]
│ [14:58:01] Generate [completed]
│ [14:58:01] Generate helpers/backend/backend-schema.json [completed]
│ [14:58:02] Load GraphQL documents [completed]
│ [14:58:02] Generate [started]
│ [14:58:02] Generate [completed]
│ [14:58:02] Generate helpers/backend/graphql.ts [completed]
│ [14:58:02] Generate outputs [completed]
└─ Done in 4s

> hoppscotch-app@2.2.1 generate D:coderusthoppscotch-apphoppscotch
> pnpm -r do-build-prod

Scope: 4 of 5 workspace projects
packages/hoppscotch-js-sandbox do-build-prod$ pnpm run build
│ > @hoppscotch/js-sandbox@1.0.0 build D:coderusthoppscotch-apphoppscotchpackageshoppscotch-js-sandbox
│ > npx tsc
└─ Done in 7.5s
packages/hoppscotch-app do-build-prod$ pnpm run generate
│ > hoppscotch-app@2.2.1 generate D:coderusthoppscotch-apphoppscotchpackageshoppscotch-app
│ > nuxt generate --modern
│ i Sentry reporting is disabled (no DSN has been provided)
│ i Production build
│ i Bundling only for client side
│ i Target: static
│ i Using components loader to optimize imports
│ i Discovered Components: node_modules/.cache/nuxt/components/readme.md
│ √ Builder initialized
│ √ Nuxt files generated
│ i Compiling Client
│  ERROR  Error: error:0308010C:digital envelope routines::unsupported
│     at new Hash (node:internal/crypto/hash:67:19)
│     at Object.createHash (node:crypto:133:10)
│     at module.exports (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_moduleswebpacklib
│     at NormalModule._initBuildHash (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_module
│     at handleParseError (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_moduleswebpackl
│     at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_moduleswebpacklibNormalModule.js
│     at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_moduleswebpacklibNormalModule.js
│     at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modulesloader-runnerlibLoad
│     at iterateNormalLoaders (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modules
│     at iterateNormalLoaders (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modules
│     at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modulesloader-runnerlibLoad
│     at runSyncOrAsync (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modulesloader
│     at iterateNormalLoaders (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modules
│     at Array.<anonymous> (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modulesloa
│     at Storage.finished (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmenhanced-resolve@4.5.0node_modulese
│     at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmenhanced-resolve@4.5.0node_modulesenhanced-resolveli
│  WARN  Browserslist: caniuse-lite is outdated. Please run:
│   npx browserslist@latest --update-db
│   Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
│  ERROR  error:0308010C:digital envelope routines::unsupported
│   at new Hash (node:internal/crypto/hash:67:19)
│   at Object.createHash (node:crypto:133:10)
│   at module.exports (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_moduleswebpacklibu
│   at NormalModule._initBuildHash (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_modules
│   at handleParseError (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_moduleswebpacklib
│   at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_moduleswebpacklibNormalModule.js:5
│   at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_moduleswebpacklibNormalModule.js:3
│   at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modulesloader-runnerlibLoader
│   at iterateNormalLoaders (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_moduleslo
│   at iterateNormalLoaders (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_moduleslo
│   at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modulesloader-runnerlibLoader
│   at context.callback (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modulesloader
│   at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmbabel-loader@8.2.3_@babel+core@7.16.12node_modulesbabel
│ D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modulesloader-runnerlibLoaderRunne
│                       throw e;
│                       ^
│ Error: error:0308010C:digital envelope routines::unsupported
│     at new Hash (node:internal/crypto/hash:67:19)
│     at Object.createHash (node:crypto:133:10)
│     at module.exports (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_moduleswebpacklib
│     at NormalModule._initBuildHash (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_module
│     at handleParseError (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_moduleswebpackl
│     at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_moduleswebpacklibNormalModule.js
│     at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_moduleswebpacklibNormalModule.js
│     at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modulesloader-runnerlibLoad
│     at iterateNormalLoaders (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modules
│     at iterateNormalLoaders (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modules
│     at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modulesloader-runnerlibLoad
│     at context.callback (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modulesload
│     at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmcache-loader@4.1.0_webpack@4.46.0node_modulescache-lo
│     at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmgraceful-fs@4.2.8node_modulesgraceful-fsgraceful-fs.
│     at FSReqCallback.oncomplete (node:fs:201:23) {
│   opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
│   library: 'digital envelope routines',
│   reason: 'unsupported',
│   code: 'ERR_OSSL_EVP_UNSUPPORTED'
│ }
│ Node.js v18.4.0
│  ELIFECYCLE  Command failed with exit code 1.
└─ Failed in 8.3s
D:coderusthoppscotch-apphoppscotchpackageshoppscotch-app:
 ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL  hoppscotch-app@2.2.1 do-build-prod: `pnpm run generate`
Exit status 1
 ELIFECYCLE  Command failed with exit code 1.

D:coderusthoppscotch-apphoppscotch>npx browserslist@latest --update-db
Need to install the following packages:
  browserslist@4.20.4
Ok to proceed? (y) y
Latest version:     1.0.30001357
Updating caniuse-lite version
$ pnpm up caniuse-lite
caniuse-lite has been successfully updated

No target browser changes

D:coderusthoppscotch-apphoppscotch>pnpm install && pnpm run generate
Scope: all 5 workspace projects
Lockfile is up-to-date, resolution step is skipped
Already up-to-date
packages/codemirror-lang-graphql prepare$ rollup -c
│ Browserslist: caniuse-lite is outdated. Please run:
│   npx browserslist@latest --update-db
│   Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
│
│ src/index.js → dist/index.cjs, ./dist...
│ created dist/index.cjs, ./dist in 2.8s
└─ Done in 4.8s
packages/hoppscotch-data prepare$ tsup src --dts
[20 lines collapsed]
│ CJS distchunk-JUWXSDKJ.js     1010.00 B
│ DTS Build start
│ DTS ⚡️ Build success in 2250ms
│ DTS distindex.d.ts              714.00 B
│ DTS distrestindex.d.ts         2.18 KB
│ DTS distgraphqlindex.d.ts      589.00 B
│ DTS distcollectionindex.d.ts   1.30 KB
│ DTS distrestcontent-types.d.ts 473.00 B
│ DTS distrestHoppRESTAuth.d.ts  882.00 B
│ DTS disttype-utils.d.d.ts       1.00 B
└─ Done in 3.7s
packages/hoppscotch-js-sandbox postinstall$ pnpm run build
│ > @hoppscotch/js-sandbox@1.0.0 build D:coderusthoppscotch-apphoppscotchpackageshoppscotch-js-sandbox
│ > npx tsc
└─ Done in 8.5s
. prepare$ husky install
│ husky - Git hooks installed
└─ Done in 335ms
packages/hoppscotch-app postinstall$ pnpm run gql-codegen
[12 lines collapsed]
│ [15:02:37] Load GraphQL documents [started]
│ [15:02:37] Load GraphQL documents [completed]
│ [15:02:37] Generate [started]
│ [15:02:37] Generate [completed]
│ [15:02:37] Generate helpers/backend/backend-schema.json [completed]
│ [15:02:38] Load GraphQL documents [completed]
│ [15:02:38] Generate [started]
│ [15:02:38] Generate [completed]
│ [15:02:38] Generate helpers/backend/graphql.ts [completed]
│ [15:02:38] Generate outputs [completed]
└─ Done in 3.8s

> hoppscotch-app@2.2.1 generate D:coderusthoppscotch-apphoppscotch
> pnpm -r do-build-prod

Scope: 4 of 5 workspace projects
packages/hoppscotch-js-sandbox do-build-prod$ pnpm run build
│ > @hoppscotch/js-sandbox@1.0.0 build D:coderusthoppscotch-apphoppscotchpackageshoppscotch-js-sandbox
│ > npx tsc
└─ Done in 6.9s
packages/hoppscotch-app do-build-prod$ pnpm run generate
│ > hoppscotch-app@2.2.1 generate D:coderusthoppscotch-apphoppscotchpackageshoppscotch-app
│ > nuxt generate --modern
│ i Sentry reporting is disabled (no DSN has been provided)
│ i Production build
│ i Bundling only for client side
│ i Target: static
│ i Using components loader to optimize imports
│ i Discovered Components: node_modules/.cache/nuxt/components/readme.md
│ √ Builder initialized
│ √ Nuxt files generated
│ i Compiling Client
│  ERROR  Error: error:0308010C:digital envelope routines::unsupported
│     at new Hash (node:internal/crypto/hash:67:19)
│     at Object.createHash (node:crypto:133:10)
│     at module.exports (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_moduleswebpacklib
│     at NormalModule._initBuildHash (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_module
│     at handleParseError (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_moduleswebpackl
│     at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_moduleswebpacklibNormalModule.js
│     at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_moduleswebpacklibNormalModule.js
│     at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modulesloader-runnerlibLoad
│     at iterateNormalLoaders (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modules
│     at iterateNormalLoaders (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modules
│     at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modulesloader-runnerlibLoad
│     at runSyncOrAsync (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modulesloader
│     at iterateNormalLoaders (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modules
│     at Array.<anonymous> (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modulesloa
│     at Storage.finished (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmenhanced-resolve@4.5.0node_modulese
│     at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmenhanced-resolve@4.5.0node_modulesenhanced-resolveli
│  WARN  Browserslist: caniuse-lite is outdated. Please run:
│   npx browserslist@latest --update-db
│   Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
│  ERROR  error:0308010C:digital envelope routines::unsupported
│   at new Hash (node:internal/crypto/hash:67:19)
│   at Object.createHash (node:crypto:133:10)
│   at module.exports (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_moduleswebpacklibu
│   at NormalModule._initBuildHash (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_modules
│   at handleParseError (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_moduleswebpacklib
│   at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_moduleswebpacklibNormalModule.js:5
│   at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_moduleswebpacklibNormalModule.js:3
│   at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modulesloader-runnerlibLoader
│   at iterateNormalLoaders (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_moduleslo
│   at iterateNormalLoaders (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_moduleslo
│   at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modulesloader-runnerlibLoader
│   at context.callback (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modulesloader
│   at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmbabel-loader@8.2.3_@babel+core@7.16.12node_modulesbabel
│ D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modulesloader-runnerlibLoaderRunne
│                       throw e;
│                       ^
│ Error: error:0308010C:digital envelope routines::unsupported
│     at new Hash (node:internal/crypto/hash:67:19)
│     at Object.createHash (node:crypto:133:10)
│     at module.exports (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_moduleswebpacklib
│     at NormalModule._initBuildHash (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_module
│     at handleParseError (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_moduleswebpackl
│     at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_moduleswebpacklibNormalModule.js
│     at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmwebpack@4.46.0node_moduleswebpacklibNormalModule.js
│     at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modulesloader-runnerlibLoad
│     at iterateNormalLoaders (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modules
│     at iterateNormalLoaders (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modules
│     at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modulesloader-runnerlibLoad
│     at context.callback (D:coderusthoppscotch-apphoppscotchnode_modules.pnpmloader-runner@2.4.0node_modulesload
│     at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmcache-loader@4.1.0_webpack@4.46.0node_modulescache-lo
│     at D:coderusthoppscotch-apphoppscotchnode_modules.pnpmgraceful-fs@4.2.8node_modulesgraceful-fsgraceful-fs.
│     at FSReqCallback.oncomplete (node:fs:201:23) {
│   opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
│   library: 'digital envelope routines',
│   reason: 'unsupported',
│   code: 'ERR_OSSL_EVP_UNSUPPORTED'
│ }
│ Node.js v18.4.0
│  ELIFECYCLE  Command failed with exit code 1.
└─ Failed in 8.2s
D:coderusthoppscotch-apphoppscotchpackageshoppscotch-app:
 ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL  hoppscotch-app@2.2.1 do-build-prod: `pnpm run generate`
Exit status 1
 ELIFECYCLE  Command failed with exit code 1.

D:coderusthoppscotch-apphoppscotch>echo %NODE_OPTIONS%
%NODE_OPTIONS%

D:coderusthoppscotch-apphoppscotch>set NODE_OPTIONS=--openssl-legacy-provider

D:coderusthoppscotch-apphoppscotch>echo %NODE_OPTIONS%
--openssl-legacy-provider

D:coderusthoppscotch-apphoppscotch>pnpm run generate

> hoppscotch-app@2.2.1 generate D:coderusthoppscotch-apphoppscotch
> pnpm -r do-build-prod

Scope: 4 of 5 workspace projects
packages/hoppscotch-js-sandbox do-build-prod$ pnpm run build
│ > @hoppscotch/js-sandbox@1.0.0 build D:coderusthoppscotch-apphoppscotchpackageshoppscotch-js-sandbox
│ > npx tsc
└─ Done in 7.1s
packages/hoppscotch-app do-build-prod$ pnpm run generate
[732 lines collapsed]
│ √ Generated route "/vi/enter"
│ √ Generated route "/vi/graphql"
│ √ Generated route "/vi/join-team"
│ √ Generated route "/vi/profile"
│ √ Generated route "/vi/realtime"
│ √ Generated route "/vi/settings"
│ √ Generated route "/"
│ √ Client-side fallback created: 404.html
│ i Generating sitemaps
│ √ Generated /sitemap.xml
└─ Done in 6m 37.1s

D:coderusthoppscotch-apphoppscotch>

nvm list

nvm install v12.22.8

nvm install --lts
nvm use --lts

node -v
v17.4.0

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.1/install.sh | bash

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.1/install.sh | zsh

nvm install --lts

 node -v 

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.1/install.sh | bash

nvm install --lts

nvm use --lts

RUN export NODE_OPTIONS=--openssl-legacy-provider && yarn build && yarn install --production --ignore-scripts --prefer-offline

npm audit fix --force

const crypto = require('crypto');

/**
 * md4 algorithm is not available anymore in NodeJS 17+ (because of lib SSL 3).
 * In that case, silently replace md4 by md5 algorithm.
 */
try {
  crypto.createHash('md4');
} catch (e) {
  console.warn('Crypto "md4" is not supported anymore by this Node version');
  const origCreateHash = crypto.createHash;
  crypto.createHash = (alg, opts) => {
    return origCreateHash(alg === 'md4' ? 'md5' : alg, opts);
  };
}

sudo n 16.13.0

ENV NODE_OPTIONS=--openssl-legacy-provider

Sign Up for Our Newsletters

Subscribe to get notified of the latest articles. We will never spam you. Be a part of our ever-growing community.

By checking this box, you confirm that you have read and are agreeing to our terms of use regarding the storage of the data submitted through this form.

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:UsersmanueDesktopprojectshello-worldnode_moduleswebpacklibutilcreateHash.js:135:53)
    at NormalModule._initBuildHash (C:UsersmanueDesktopprojectshello-worldnode_moduleswebpacklibNormalModule.js:417:16)
    at handleParseError (C:UsersmanueDesktopprojectshello-worldnode_moduleswebpacklibNormalModule.js:471:10)
    at C:UsersmanueDesktopprojectshello-worldnode_moduleswebpacklibNormalModule.js:503:5
    at C:UsersmanueDesktopprojectshello-worldnode_moduleswebpacklibNormalModule.js:358:12
    at iterateNormalLoaders (C:UsersmanueDesktopprojectshello-worldnode_modulesloader-runnerlibLoaderRunner.js:214:10)
    at iterateNormalLoaders (C:UsersmanueDesktopprojectshello-worldnode_modulesloader-runnerlibLoaderRunner.js:221:10)
C:UsersmanueDesktopprojectshello-worldnode_modulesreact-scriptsscriptsstart.js:19
  throw err;
  ^

Error: error:0308010C:digital envelope routines::unsupported
    at Object.createHash (node:crypto:130:10)
    at module.exports (C:UsersmanueDesktopprojectshello-worldnode_moduleswebpacklibutilcreateHash.js:135:53)
    at NormalModule._initBuildHash (C:UsersmanueDesktopprojectshello-worldnode_moduleswebpacklibNormalModule.js:417:16)
    at C:UsersmanueDesktopprojectshello-worldnode_moduleswebpacklibNormalModule.js:452:10
    at C:UsersmanueDesktopprojectshello-worldnode_moduleswebpacklibNormalModule.js:323:13
    at C:UsersmanueDesktopprojectshello-worldnode_modulesloader-runnerlibLoaderRunner.js:367:11
    at C:UsersmanueDesktopprojectshello-worldnode_modulesloader-runnerlibLoaderRunner.js:233:18
    at context.callback (C:UsersmanueDesktopprojectshello-worldnode_modulesloader-runnerlibLoaderRunner.js:111:13)
    at C:UsersmanueDesktopprojectshello-worldnode_modulesbabel-loaderlibindex.js:59:103 {
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

In this post, we will see How To Fix Error – “Digital Envelope Routines::Unsupported” in Node.js, React.js, Angular.js, Vue.js, Docker etc. Various facets of the error –

Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:67:19)

Error: digital envelope routines::unsupported
opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
library: 'digital envelope routines',

Failed to construct transformer: Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:67:19)

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

The common reason for such issue is Version conflict issue or Version not in-sync with other entities in the system. Sometimes using latest Node.js might throw such error. Lot of projects still depend on Webpack 4 but the latest Node.js might not be compatible with that. Majorly this is caused by the latest Node.js Version compatible issues with OpenSSL.

Check you node version

node -v

We will try out the below two options to see if that helps to fix the issue.

Option 1:

If you want to stick to your existing Node.js without down-grading it, then try the below steps –

• Use openssl-legacy-provider by setting it as an environment variable

• • Windows – Set below as environment variable

set NODE_OPTIONS=--openssl-legacy-provider

• • MacLinux – Set below in ~/.bash_profile or ~/.bashrc so that it stays even after you logoutlogin back.

export NODE_OPTIONS=--openssl-legacy-provider

• • For Docker – add the Highlighted bit in Dockekrfile

ENV NODE_OPTIONS=--openssl-legacy-provider

OR

RUN export NODE_OPTIONS=--openssl-legacy-provider && yarn build && yarn install

• The openssl-legacy-provider parameter should be placed inside your package.json. Add the part highlighted in Red.

• • For Angular, use the below and then use npm start

"start": "set NODE_OPTIONS=--openssl-legacy-provider && ng serve -o"

• • For React, use the below in the package.json file.

"scripts": {
"start": "react-scripts --openssl-legacy-provider start",
"build": "react-scripts --openssl-legacy-provider build",
}

OR

"scripts": {
"start": "export SET NODE_OPTIONS=--openssl-legacy-provider && react-scripts start",
"build": "export SET NODE_OPTIONS=--openssl-legacy-provider && react-scripts build"
}

• For Vue.js, use the below in the package.json file.

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

OR

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

• Also add something like the below Highlighted –

 "scripts": {

       "build": "NODE_OPTIONS=--openssl-legacy-provider npm run build:your-app:testing”,
       "build:your-app:testing": "NODE_OPTIONS=--openssl-legacy-provider ng build your-app 
                        --deploy-url https://your-app.com/ --configuration=test-config"

Another example –

"scripts": {
    "dev": "NODE_OPTIONS=--openssl-legacy-provider nuxt"
}

Option 2:

At this point, I am assuming Option 1 somehow did not work out to fix the issue. The next option we can try is to roll-back to an older version of Node.js (STABLE) which is compatible with Webpack and doesn’t render this issue.

• The version that you are using might not be compatible with some Webpack components.

• Remove the current Node.js version and go-back i.e. Downgrade to an older Stable version. e.g. From Node.js 17+ go back to Node.js version 16+.
  • Windows – Uninstall node from the “Add or remove programs”. Alternatively use https://docs.microsoft.com/en-us/windows/dev-environment/javascript/nodejs-on-windows to setup nvm and control Node version through it

nvm use <version>

• • LinuxMac –

sudo n lts <------ To demote to the last LTS

OR

$ npm install -g n
$ n <VERSION_NO>

• Once done, cross check if node version is downgraded

$ node -v

•  Delete the folder “node_modules” .

• Re-install Node.js
  • Re-install the latest LTS node.js version from – https://nodejs.org/en/download/releases/
  • Alternatively use NVM package –
    • LinuxMac – https://github.com/nvm-sh/nvm
    • Windows – https://github.com/coreybutler/nvm-windows

nvm instal lts

OR

nvm use lts

• Rebuild your project.

Hope this helps to solve the error.

Other Interesting Reads –

• How to Update or Upgrade Gradle version in Android Studio?

• How To Fix – “app:processDebugResources FAILED” in Android Studio ?

• How To Fix – “Error: No Toolchains Found in the NDK Toolchains Folder” in Android ?

• How To Fix – Error “ENOSPC: System Limit for Number of File Watchers Reached” ?

• How To Fix – “Error: Unable To Find Utility “Instruments”, Not A Developer Tool or In PATH” ?

• How to Fix – Uncaught TypeError: a.indexOf is Not a Function ?

• How To Fix – Error “SDK location not found” in Android, React Native or Flutter ?

• How to Send Large Messages in Kafka ?

• Fix Spark Error – “org.apache.spark.SparkException: Failed to get broadcast_0_piece0 of broadcast_0”

• How to Handle Bad or Corrupt records in Apache Spark ?

• How to use Broadcast Variable in Spark ?

• How to log an error in Python ?

 error:0308010c:digital envelope routines::unsupported vue ,failed to construct transformer: error: error:0308010c:digital envelope routines::unsupported ,library: 'digital envelope routines', reason: 'unsupported', code: 'err_ossl_evp_unsupported' ,ganache cli digital envelope routines::unsupported ,opensslerrorstack: [ 'error:03000086:digital envelope routines::initialization error' ], ,error hh604: error running json-rpc server: error:0308010c:digital envelope routines::unsupported ,openssl digital envelope routines:inner_evp_generic_fetch:unsupported ,openssl error digital envelope routines ,digital envelope routines::unsupported angular ,error:0308010c:digital envelope routines::unsupported vue ,failed to construct transformer: error: error:0308010c:digital envelope routines::unsupported ,library: 'digital envelope routines', reason: 'unsupported', code: 'err_ossl_evp_unsupported' ,opensslerrorstack: [ 'error:03000086:digital envelope routines::initialization error' ], ,openssl digital envelope routines:inner_evp_generic_fetch:unsupported ,this[khandle] = new _hash(algorithm, xoflen); , , ,library 'digital envelope routines' ,library 'digital envelope routines' reason 'unsupported' code 'err_ossl_evp_unsupported' ,ng serve digital envelope routines unsupported ,node digital envelope routines ,node js digital envelope routines ,nodejs digital envelope routines unsupported ,npm digital envelope routines ,npm digital envelope routines unsupported ,npm run build digital envelope routines unsupported ,ntlm digital envelope routines evp_digestinit_ex disabled for fips ,openssl bad decrypt digital envelope routines ,openssl digital envelope routines evp_decryptfinal_ex bad decrypt ,digital envelope routines unsupported ,digital envelope routines ,digital envelope routines unsupported angular ,digital envelope routines initialization error ,digital envelope routines' reason 'unsupported' ,digital envelope routines evp_decryptfinal_ex bad decrypt ,digital envelope routines evp_digestinit_ex disabled for fips ,digital envelope routines unsupported webpack ,digital envelope routines err_ossl_evp_unsupported ,openssl digital envelope routines unsupported ,openssl error outputting keys and certificates digital envelope routines ,openssl error stack digital envelope routines ,openssl unable to load private key digital envelope routines ,paramiko valueerror digital envelope routines evp_digestinit_ex disabled for fips ,penpal envelope ideas ,python digital envelope routines evp_digestinit_ex disabled for fips ,python valueerror digital envelope routines evp_digestinit_ex disabled for fips ,react digital envelope routines unsupported ,storybook digital envelope routines unsupported ,unable to load private key digital envelope routines ,unsupported digital envelope routines ,valueerror digital envelope routines evp_digestinit_ex disabled for fips ,vue digital envelope routines unsupported ,webpack digital envelope routines unsupported ,what is digital envelope ,what is the envelope method ,yarn digital envelope routines unsupported ,yarn start digital envelope routines unsupported ,advantages of digital envelope ,angular digital envelope routines unsupported ,ansible digital envelope routines evp_digestinit_ex disabled for fips ,bad decrypt digital envelope routines ,config error digital envelope routines evp_digestinit_ex disabled for fips ,digital envelope routines ,digital envelope routines angular ,digital envelope routines bad decrypt ,digital envelope routines disabled for fips ,digital envelope routines err_ossl_evp_unsupported ,digital envelope routines error ,digital envelope routines evp decrypt final bad decrypt ,digital envelope routines evp_decryptfinal_ex bad decrypt ,digital envelope routines evp_decryptfinal_ex bad decrypt teraterm ,digital envelope routines evp_decryptfinal_ex wrong final block length ,digital envelope routines evp_digestinit_ex disabled for fips ,digital envelope routines evp_digestinit_ex disabled for fips paramiko ,digital envelope routines evp_pkey ,digital envelope routines initialization error ,digital envelope routines initialization error angular ,digital envelope routines inner_evp_generic_fetch ,digital envelope routines meaning ,digital envelope routines node js ,digital envelope routines not supported ,digital envelope routines openssl ,digital envelope routines questions ,digital envelope routines questions and answers ,digital envelope routines questions and answers pdf ,digital envelope routines quora ,digital envelope routines quotes ,digital envelope routines unsupported ,digital envelope routines unsupported angular ,digital envelope routines unsupported at new hash ,digital envelope routines unsupported err_ossl_evp_unsupported ,digital envelope routines unsupported in angular ,digital envelope routines unsupported nextjs ,digital envelope routines unsupported react ,digital envelope routines unsupported vue ,digital envelope routines unsupported webpack ,digital envelope routines unsupported windows ,digital envelope routines wrong final block length ,digital envelope routines xerox ,digital envelope routines xls ,digital envelope routines xlsx ,digital envelope routines xpath ,digital envelope routines zerodha ,digital envelope routines zerodha kite ,digital envelope routines zoho ,digital envelope routines zomato ,digital envelope routines' ,digital envelope routines' reason 'unsupported' ,digital envelope routines' reason 'unsupported' code 'err_ossl_evp_unsupported' ,digital organizer job description ,digital organizing ideas ,digital photo organization ideas ,digital transformation activities ,docker digital envelope routines unsupported ,err_ossl_evp_unsupported digital envelope routines ,error digital envelope routines evp_decryptfinal ,error digital envelope routines unsupported ,failed to construct transformer digital envelope routines ,how to create digital envelope ,ideas for cash envelope system ,j&t envelope size ,

Web development has come a long way from basic HTML and CSS pages and PHP backends. These days we have a lot of web development frameworks to work with and quickly deploy web apps and sites. 

That said, it’s also gotten a lot more complex than simple HTML websites. In this article, we’re looking at the “Error: error:0308010c:digital envelope routines::unsupported” error, its reasons and what you can do to fix the problem. 

Also read: How to fix ‘React-scripts: Command not found’ error?

What causes this error?

The error is caused when trying to run a React project on Nodejs version 17 or above. The error can also trigger if you’re building the project using Docker, as it pulls the latest available version of Node.js by default.

The problem here is Node.js 17’s push to use OpenSSL 3, changing the code required for the initialisation context of the md family. 

How to fix this?

Here are two fixes you can try out.

Enable legacy OpenSSL support

You can circumvent the error by enabling support for legacy OpenSSL versions. There are two ways to do this using either the terminal or changing the package.json file. 

Using the terminal

Use this command if you’re on macOS, Linux, or Windows Git Bash.

export NODE_OPTIONS=--openssl-legacy-provider

If you’re on Windows, use this command instead.

set NODE_OPTIONS=--openssl-legacy-provider

Using the package.json file (recommended)

You can also change the package.json file to let React know that you’re supporting legacy OpenSSL features. Just head over to the file and locate this line.

"start": "react-scripts start"

Change this to

"start": "react-scripts --openssl-legacy-provider start"

By downgrading the Node.js version

Another way to quickly get around the problem is by downgrading to the latest stable release version of Node.js (16.15.1 at the time of writing). Just open a terminal, and run the following command.

nvm install 16.15.1

Now try running the project, and it should build without any errors. Try forcing the LTS version using this command if you’re still getting the error.

nvm use --lts

Also read: How to fix ‘Collect2.exe: error: ld returned 1 exit status’ error?