Closed gnidan closed 1 year ago
Hey @gnidan, Node moved to OpenSSL 3.0 and there's an option to enable the legacy behavior.
If you hit an ERR_OSSL_EVP_UNSUPPORTED error in your application with Node.js 17, it’s likely that your application or a module you’re using is attempting to use an algorithm or key size which is no longer allowed by default with OpenSSL 3.0. A command-line option, --openssl-legacy-provider, has been added to revert to the legacy provider as a temporary workaround for these tightened restrictions.
Ah, thanks @cds-amal! I was going to start by upgrading the various devDeps, maybe that will fix the issue. Good to know there's this flag as a backup option.
(Probably should add the web-ui build to CI checks so this sorta thing can be caught sooner)
Fixed for now (without further investigation) by setting an explicit Node.js version
Getting this in CI e.g.:
(Will look into this soon, sorry all! In the meantime, please use the NPM package locally.)