How To Fix ERR_OSSL_EVP_UNSUPPORTED Error

Web and app developers work with various programming languages, frameworks, and environments, each designed to improve their projects’ functionality and efficiency. Whether you’re building a website, developing an application, or managing server configurations, the right development tools are required to ensure everything runs smoothly.

However, as these tools evolve and become more sophisticated, they can also present new challenges. One such challenge that developers often face is the ERR_OSSL_EVP_UNSUPPORTED error, which can disturb your workflow and slow your progress if not addressed on time.

Several factors can trigger the code: ‘err_ossl_evp_unsupported’ error, but it usually happens when different software versions in your development stack are incompatible. Therefore, it’s relatively easy to resolve it. In this tutorial, you’ll learn about the ERR_OSSL_EVP_UNSUPPORTED error, why it occurs, and how to sort it.

KEY TAKEAWAYS

1. The ERR_OSSL_EVP_UNSUPPORTED error occurs due to incompatibility between outdated development tools and the updated OpenSSL library.
2. Upgrading Node.js, React.js, or Vue.js to their latest versions is a key step in resolving this error.
3. If you cannot upgrade your tools, enabling the OpenSSL legacy provider offers a temporary workaround to bypass the error.
4. Regularly updating your development tools ensures compatibility with the latest security protocols and prevents issues like the OSSL error.

What Is ERR_OSSL_EVP_UNSUPPORTED Error?

The ERR_OSSL_EVP_UNSUPPORTED error is a technical issue developers may encounter when working on web applications, particularly those involving secure communications.

To understand this error, let’s break it down. “ERR” indicates that there’s an error, “OSSL” stands for OpenSSL, which is a widely used cryptographic library, and “EVP_UNSUPPORTED” refers to a specific function within OpenSSL’s cryptographic processing that is no longer supported.

Now, what is OpenSSL? OpenSSL is a library that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, essential for encrypting data and securing communications within web development environments. Website owners install SSL certificates on their websites; similarly, you can use OpenSSL to install SSL files on your web server.>

The ERR OSSL EVP UNSUPPORTED error typically occurs in development environments when there’s a mismatch between the version of OpenSSL being used and the cryptographic requirements (cryptographic techniques involve various processes such as encryption, decryption, hashing, and digital signatures) of the application or tools in use.

For example, after updating OpenSSL to a newer version, you might find that certain encryption methods or algorithms your application relies on are no longer supported, leading to this error.

This is particularly problematic for projects that depend on SSL/TLS protocols for secure data transmission, as it can disrupt the normal functioning of these security measures, potentially exposing sensitive information or discontinuing development progress.

To fully understand how and why this error occurs, imagine you’re trying to unlock a door with an old-fashioned key. For years, this key worked perfectly. But when you replace the lock with an advanced, modern one, the old key no longer fits.

The key is outdated, and the lock won’t turn, leaving you unable to open the door. In this analogy, the ERR OSSL EVP UNSUPPORTED error is like the door refusing to open because the key (your encryption algorithm) is no longer supported by the new lock (OpenSSL library).

Now, the point is, which framework(s) can trigger the code: ‘err_ossl_evp_unsupported’ error? In practice, you might encounter the ERR_OSSL_EVP_UNSUPPORTED while working with frameworks like Node.js, React.js, or Vue.js, especially if these tools haven’t been updated to align with the latest OpenSSL standards.

Remember: taking this error for granted and not fixing it can prevent your application from running properly, so it’s mandatory to address it promptly and ensure all components of your development stack are compatible with the latest security protocols.

What Causes The ERR_OSSL_EVP_UNSUPPORTED Error?

The OSSL error can occur for the following reasons:

Incompatibility Issues

The ERR OSSL EVP UNSUPPORTED error often results from incompatibility issues between the OpenSSL library and the development tools or frameworks you are using. When developers update OpenSSL, they may find security protocols and cryptographic algorithms do not align with the older tools.

This inconsistency creates conflicts, especially if the development environment relies on outdated software that isn’t fully compatible with the latest OpenSSL updates. As a result, the error is triggered when the application tries to use an encryption method that OpenSSL no longer supports.

OpenSSL 3.0 Update

Another significant contributor to this issue is the OpenSSL 3.0 update, which introduced tighter security protocols and changes to hashing algorithms. These updates were created to enhance security by phasing out weaker, outdated encryption methods.

However, this led to an increase in the ERR_OSSL_EVP_UNSUPPORTED error, particularly for developers who have not yet updated their development tools to match the new standards. The transition to OpenSSL 3.0 means that any tool or framework relying on older cryptographic practices might suddenly become incompatible, causing this error to appear more frequently.

Outdated Software

OSSL errors are common when developers use outdated software such as older versions of Node.js, React.js, or Vue.js. These tools, which are integral to many web development projects, may not have been updated to support the latest OpenSSL standards.

When the development stack includes such outdated components, it increases the likelihood of encountering the ERR_OSSL_EVP_UNSUPPORTED error. Therefore, regularly updating your development tools and libraries is essential to prevent these types of compatibility issues and ensure that your projects run smoothly with the latest security enhancements.

Now you know what the OSSL error is and why it occurs, let’s look at different ways to fix it.

3 Methods To Fix ERR_OSSL_EVP_UNSUPPORTED Error

Facing the ERR OSSL EVP UNSUPPORTED error can be frustrating, but it’s often easy to resolve with the right approach. As we said earlier, this error typically arises due to compatibility issues between your development environment and the updated OpenSSL library.

So, to fix it, you’ll need to ensure that your development tools are updated and compatible with the latest cryptographic standards. However, if you don’t want to update your tools, you can enable the OpenSSL 3.0 legacy provider instead. For this, you only need to use the following command:

--openssl-legacy-provider

If you’ve decided to update your tools, then here are three common methods to help you fix this error:

Upgrade Node.js

Node.js is a runtime environment allowing developers to run JavaScript code outside a web browser, typically on a server. It is built on Chrome’s V8 JavaScript engine and creates fast, scalable, and real-time applications like web servers or APIs.

One key feature of Node.js is its ability to handle many requests simultaneously, making it highly efficient for server-side tasks. If you’re using Angular or Next.js, you may also face the ERR OSSL EVP UNSUPPORTED error because both frameworks rely on Node.js.

As a solution, you need to upgrade Node.js to resolve the ERR OSSL EVP UNSUPPORTED error, because this is often where the issue arises. Here’s how you can do it on Windows:

Update Node.js with Windows Installer

To update Node.js on a Windows machine using the official installer is a straightforward process. Follow these steps to ensure you have the latest version installed:

Open your command prompt and type node -v or node –version to check the version of Node.js currently installed. This will display your current Node.js version, which you can compare with the newest version available.

Then, visit the NodeJS Official Website to download it. This will download a .msi file.

Once the download is complete, navigate to the folder where the .msi file was saved (usually in the Downloads folder). Double click on the .msi file to run the installer. The Node.js setup wizard will open. Click Next to proceed.

Read the license agreement, select I accept the terms in the License Agreement, and click Next.

The installer will suggest a default installation path (e.g., C:\Program Files\nodejs\). You can leave this as it is or choose a different location. Click Next.

The installer will let you choose which components to install. It’s recommended you leave the default settings unless you have specific needs. Click Next.

You may check the checkbox to automatically install the necessary tools and click Next again.

Now, you’re ready to install Node.js, so click the Install button to begin the installation process. The installer will overwrite the old Node.js version with the new one.

Now, wait for the installation process to complete. Then, click Finish to close the wizard.

Now, you need to open a new command prompt window and run the node -v command to verify that Node.js has been updated. The version number displayed should match the version you downloaded.

node -v

Update Node.js Using nvm Package

Updating Node.js using the nvm (Node Version Manager, used to update Node easily) package allows you to switch easily between various versions of Node.js. Here’s a step-by-step guide on how to do it:

Open a command prompt and type nvm -v.  If nvm is already installed, it will display the version number. However, if it’s not, you need to install the nvm package. To do this, go to the nvm-windows GitHub page and download the nvm-setup.exe file.

nvm -v

Once the installer is downloaded, open it and accept the license agreement. Then click Next.

Browse the installation directory (you may keep the default if you don’t want to change it) and click Next.

You may leave all the default settings and click Install.

Important:

If you’re installing nvm after installing NodeJS, you may be asked if you want nvm to control the installed version. Click Yes to continue the installation.

After successfully installing nvm, write the nvm list available command in the command prompt to list the available versions of Node.js that you can install with nvm.

nvm list available

Choose the version of Node.js you want to install (e.g., 22.6.0; you can also specify it as 22) and run the nvm install 22 command. nvm will download and install the provided version. After installation, make the newly installed version active by running nvm use 22. This command sets the selected version as the current version of Node.js.

nvm install 22

Now, check that the version switch was successful by running node -v. The terminal should display the version number you just installed.

node -v

Important:

Here is what to do if the terminal or command prompt doesn’t display the version number you just installed: Delete the folder named nodejs, which is located at C:\Program Files\. Then run nvm use {version} again to recreate the nodejs folder with the correct node version. Why is this necessary? Sometimes the nvm has trouble deleting this folder due to permission issues.

nvm use {version}

Update Node.js with Chocolatey

Chocolatey is a package manager for the Windows operating system that simplifies installing, updating, and managing software on your computer. It functions similarly to package managers found on Linux distributions, like apt or yum, but is specifically designed for the Windows environment.

Chocolatey allows you to install and manage software directly from the command line, automating downloading and installing software packages, including dependencies, with simple commands.

Before updating NodeJS with Chocolatey, it’s a good idea to check if Chocolatey is updated. To ensure this, execute choco upgrade chocolatey in the Windows command prompt. If prompted, write y and hit Enter to upgrade Chocolatey.

choco upgrade chocolatey

Once Chocolatey is updated, write choco find nodejs.install to search for available Node.js packages.

choco find nodejs.install

Lastly, execute choco upgrade nodejs.install command to update NodeJS to the latest version. During the process, type y when prompted and press Enter to continue. 

choco upgrade nodejs.install

After upgrading Node.js, the ERR_OSSL_EVP_UNSUPPORTED error should be resolved if an incompatibility with the latest OpenSSL causes it. The updated Node.js version will be aligned with the current cryptographic standards, allowing your development environment to function smoothly without running into this error.

Upgrade React.js

React.js is another popular JavaScript library for building user interfaces, particularly for single-page applications. It allows web or app developers to create reusable UI components that efficiently update and render as data changes.

React uses a virtual Document Object Model (DOM, a JavaScript object) to optimize rendering performance, making web applications faster and more responsive. Due to its flexibility and efficiency, it is widely used for developing modern, dynamic web apps. As it’s useful to plenty of web applications, it’s essential to keep it updated. Let’s see how to upgrade ReactJS to version 18.

To update ReactJS, write npm install react react-dom in the command prompt.

npm install react react-dom

Then, execute the npm view react version command to check if react is upgraded.

npm view react version

If you’re using yarn, run the yarn add react react-dom command to update your ReactJS. Now, check if the ERR_OSSL_EVP_UNSUPPORTED error has disappeared on your website, whether it’s a WordPress website or a custom site. Otherwise, you may need to upgrade Vue.js.

yarn add react react-dom

Upgrade Vue.js

If upgrading the NodeJS and ReactJS didn’t resolve the issue, you might try updating the Vue.js to the latest version. To do so, execute the following command using npm:

npm update -g @vue/cli

If you’re using yarn, execute the following command:

yarn global upgrade --latest @vue/cli

Lastly, run the following command to check if the vue version is updated.

vue --version

Alternatively, you can verify the vue version under dependencies in the package.json file (located in the project’s root folder).

FAQs

Other Related Tutorials & Blogs:

– How To Fix ERR_UNKNOWN_URL_SCHEME Error

– How To Fix ERR_TUNNEL_CONNECTION_FAILED Error

– How To Fix SSL_ERROR_NO_CYPHER_OVERLAP Error

– How To Fix ERR_BAD_SSL_CLIENT_AUTH_CERT Error

– How To Fix ERR_HTTP2_PROTOCOL_ERROR