How to fix OpenSSL error 0308010C in Webpack/Next.js builds – WP Newsify

Ever deep in one Web package or Next.js project, humming along, building your awesome app, when suddenly…

BOOM 💥

You’ll see a scary error like this staring back at you:

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

Yes, that’s the dreaded thing OpenSSL error 0308010C. Don’t panic! It is common and there are simple solutions.

This error started popping up more often after Node.js 17+ versions were released. Fortunately, you are not the first to have to deal with it. Let’s take a look at what’s going on, why it’s happening and how exactly we can fix it.

🔍 What’s causing the problem?

This error is caused by the interaction between Node.js, Webpack and OpenSSL. Node.js 17 and newer have switched from using OpenSSL 1.1.1 to OpenSSL 3.0.

The crypto behavior in OpenSSL 3.0 is more secure, but also stricter. If you are using Webpack (especially an older version), it may depend on algorithms that are now no longer supported. Therefore you get:

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

Translation: Your build tools tried to do something crypto-related, and OpenSSL said, “No, that’s not allowed anymore.”

🚑 Fix the error — Your Toolbox

Let’s see some simple ways to solve this problem.

👉 Option 1: use node 16

The fastest solution? Switch to Node.js 16where this error does not appear so easily.

Here’s how:

1. If you use NVM (Node Versioning):

nvm install 16
nvm use 16

2. Or if you don’t use it NVMinstall node 16 from the official site: nodejs.org

Why it works: Node 16 still uses OpenSSL 1.1.1, which is smoother. It won’t give you random crypto errors during builds.

👉 Option 2: Set an environment variable

If you are using Node.js 17 or 18 and don’t want to downgrade, try this solution.

Before running your build or dev server, set this environment variable:

export NODE_OPTIONS=--openssl-legacy-provider

Or on Windows (PowerShell):

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

Then run:

npm run build

This tells Node to allow older crypto algorithms to pass through. It’s like giving him a ‘get out of jail free’ card.

👉 Option 3: Update webpack

If your project uses an older version of Webpack (especially v4), that could be the real problem.

Webpack 5 is better adapted to work with the newer Node.js and OpenSSL versions.

Update Webpack with:

npm install webpack@latest --save-dev

And if you are using Next.js, make sure it is using a version that supports Webpack 5+.

Remark: If you are using other packages that depend on Webpack, update those as well.

⚙️ Bonus: Check which versions you are using

Wondering which Node.js version you are using? Walk:

node -v

To check your Webpack version:

npx webpack --version

And for Next.js:

npm list next

🤖 If you are using a CI/CD pipeline

Sometimes this error only appears during builds on platforms like:

• GitHub Actions
• Vercel
• Netlify

If this happens, you can:

• Set the NODE_OPTIONS env var in the build settings.
• Force the CI pipeline to use Node.js 16 instead of 18.

For example, indoors GitHub Actions:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/setup-node@v3
        with:
          node-version: 16

And for Verceljust open your project settings and set the following:

NODE_OPTIONS = --openssl-legacy-provider

Or change the Node version via the Environment tab.

🧼 Summary: Your repair checklist

Quick overview of your toolkit:

• ✔️ Use Node.js 16 – Most reliable solution.
• ✔️ Set NODE_OPTIONS – Quick solution.
• ✔️ Upgrade web package – More future-proof.
• ✔️ Adjust CI settings — For consistent builds.

Choose the solution that works best for your installation. You don’t have to use them all.

😂 Nice developer tip

When you see this error, whisper to yourself:

“It’s not me. It’s OpenSSL.” 🎭

Even experts still stumble over these things. So don’t feel bad. Just fix it, laugh a bit… then have another cup of coffee and keep coding!

🎉 You’re all set!

No more cryptic OpenSSL errors. The next time Webpack throws a tantrum, you’ll be ready with your ninja tools. 💻🕶️

Have fun building!

Latest messages from Editorial Staff (see all)