Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpenSSL Dependency Conflict next.js upgrade #15

Open
robbyrob42 opened this issue Mar 24, 2024 — with Linear · 3 comments
Open

OpenSSL Dependency Conflict next.js upgrade #15

robbyrob42 opened this issue Mar 24, 2024 — with Linear · 3 comments
Assignees
Labels
bug Something isn't working

Comments

Copy link
Collaborator

robbyrob42 commented Mar 24, 2024

To resolve the OpenSSL error during Next.js site build on Netlify, update Node.js, install NSGL, set NODE_OPTIONS, and check … PostCSS environment variable

Error:

opensslErrorStack: [ "error:03000086:digital envelope routines::initialization error" ],
10:46:29 PM:   library: "digital envelope routines",
10:46:29 PM:   reason: "unsupported",
10:46:29 PM:   code: "ERR_OSSL_EVP_UNSUPPORTED"
10:46:29 PM: }
10:46:29 PM: Node.js v20.11.1

perplexity (online):

To resolve the error you're experiencing while building your Next.js site on Netlify, you should try the following steps:
	1.	Update Node.js: Make sure you are running the latest version of Node.js. This might involve updating your global installation or even checking if your project is configured correctly.
	2.	Install NSGL: Node Security Project - GL will help protect sensitive cryptographic data from being stored insecurely, avoiding the ERR_OSSL_EVP_UNSUPPORTED error. You can install it via npm by running npm install nsgl.
	3.	Set NODE_OPTIONS (the fth error): The suggested NODE_OPTIONS=--openssl-legacy-provider configuration seems to work assuming you haven't used mainstream ciphers before (same as in the accepted answer you linked). Network admin setting disables those methods intentionally for enhanced security due to triage done over several years. Please ensure you properly test it.
	4.	Check your PostCSS Environment Variable: Ensure that your PostCSS's path isn't causing any issues with regards to loading modules such as font files because of server retry behavior. Refer to the Chromium Source Repository for further details.
After performing these steps, ...
@robbyrob42 robbyrob42 added the bug Something isn't working label Mar 24, 2024 — with Linear
@robbyrob42 robbyrob42 self-assigned this Mar 24, 2024
@rob
Copy link

rob commented Mar 28, 2024

I did not!

@robbyrob42
Copy link
Collaborator Author

OMG sorry @rob I just copied this output and something (linear i think) at mentioned you! WTF. You definitely did not. apologies I'll try to prevent that from happening agaiin

@rob
Copy link

rob commented Mar 28, 2024

OMG sorry @rob I just copied this output and something (linear i think) at mentioned you! WTF. You definitely did not. apologies I'll try to prevent that from happening agaiin

Hahaha no problem @robbyrob42, happens all the time with this username, just happened to go through my notifications!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants