-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Build on Fedora 36 (aka without "--openssl-legacy-provider" ) #4595
Comments
Fedora 36 uses openssl 3.0, so it won't work with stock nodejs. Install nvm as your user and install nodejs LTS with it: |
Thanks @shacky. It works! |
Thanks @shacky In fact, seem that Fedora 36 (which come with openssl3) use nodejs v16.14.0 I found this pull request from nodejs project which backport --openssl-legacy-provider flags into node v16.x.
This generate some new RPMS, So I update my build fs (mock in my case)
I also need to edit /etc/ssl/openssl.cnf (openssl configuration) to enable legacy provider (was disabled by default)
After that, I'm able to build again without errors !!!
Now, the main question is:
I do not know which one you are using , but maybe something to replace ? |
Thanks @shacky, this fixed the issue for me as well. Is this issue still active? Can it be resolved using @shacky's answer? |
For me, @shacky 's answer solved the issue. Thanks again |
Issue is now understand, BUT question still there for OpenSSL3 usage....
And second point, even if @shacky workarround is working, it's still "better" to rely on the distro component.... I have a (personnal) repo for armv7 which provide AdGuardHome with patched NodeJS (Fedora 35 & 36) You can recompile these package for other arch if you want |
@Blakhard @waby38b Bumping this issue as it still persists. Seems like this is related to the use of an old |
Currently compilation fails because of: ``` opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ], library: 'digital envelope routines', reason: 'unsupported', code: 'ERR_OSSL_EVP_UNSUPPORTED' ``` What's interesting package gets built but when trying to access UI there's `404: page not found` error. It has been reported in multiple places: * AdguardTeam/AdGuardHome#5559 * AdguardTeam/AdGuardHome#4595 Signed-off-by: Dobroslaw Kijowski <[email protected]>
Currently compilation fails because of: ``` opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ], library: 'digital envelope routines', reason: 'unsupported', code: 'ERR_OSSL_EVP_UNSUPPORTED' ``` What's interesting package gets built but when trying to access UI there's `404: page not found` error. It has been reported in multiple places: * AdguardTeam/AdGuardHome#5559 * AdguardTeam/AdGuardHome#4595 Signed-off-by: Dobroslaw Kijowski <[email protected]>
Currently compilation fails because of: ``` opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ], library: 'digital envelope routines', reason: 'unsupported', code: 'ERR_OSSL_EVP_UNSUPPORTED' ``` What's interesting package gets built but when trying to access UI there's `404: page not found` error. It has been reported in multiple places: * AdguardTeam/AdGuardHome#5559 * AdguardTeam/AdGuardHome#4595 Signed-off-by: Dobroslaw Kijowski <[email protected]>
Currently compilation fails because of: ``` opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ], library: 'digital envelope routines', reason: 'unsupported', code: 'ERR_OSSL_EVP_UNSUPPORTED' ``` What's interesting package gets built but when trying to access UI there's `404: page not found` error. It has been reported in multiple places: * AdguardTeam/AdGuardHome#5559 * AdguardTeam/AdGuardHome#4595 Signed-off-by: Dobroslaw Kijowski <[email protected]>
Currently compilation fails because of: ``` opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ], library: 'digital envelope routines', reason: 'unsupported', code: 'ERR_OSSL_EVP_UNSUPPORTED' ``` What's interesting package gets built but when trying to access UI there's `404: page not found` error. It has been reported in multiple places: * AdguardTeam/AdGuardHome#5559 * AdguardTeam/AdGuardHome#4595 Signed-off-by: Dobroslaw Kijowski <[email protected]>
@waby38b, we've recently updated the frontend build, including switching to Node.JS 16. Is this issue still occurring? |
Hi, and thx to back to this topic ! In fact I (for now) alway use workarround with "NODE_OPTIONS=--openssl-legacy-provider"... And many peoples (like WRT) on the web seem to do the same.... Anyway, I just try to build again latest branch "release-v0.107.39" on my Fedora 38 Enabling legacy in /etc/ssl/openssl.cnf & build with NODE_OPTIONS=--openssl-legacy-provider still fix the issue.... Fedora 38 components: Edit: Another point Enabling legacy in /etc/ssl/openssl.cnf is just requiered during build, but not for execution... |
Currently compilation fails because of: ``` opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ], library: 'digital envelope routines', reason: 'unsupported', code: 'ERR_OSSL_EVP_UNSUPPORTED' ``` What's interesting package gets built but when trying to access UI there's `404: page not found` error. It has been reported in multiple places: * AdguardTeam/AdGuardHome#5559 * AdguardTeam/AdGuardHome#4595 Signed-off-by: Dobroslaw Kijowski <[email protected]>
Currently compilation fails because of: ``` opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ], library: 'digital envelope routines', reason: 'unsupported', code: 'ERR_OSSL_EVP_UNSUPPORTED' ``` What's interesting package gets built but when trying to access UI there's `404: page not found` error. It has been reported in multiple places: * AdguardTeam/AdGuardHome#5559 * AdguardTeam/AdGuardHome#4595 Signed-off-by: Dobroslaw Kijowski <[email protected]>
Currently compilation fails because of: ``` opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ], library: 'digital envelope routines', reason: 'unsupported', code: 'ERR_OSSL_EVP_UNSUPPORTED' ``` What's interesting package gets built but when trying to access UI there's `404: page not found` error. It has been reported in multiple places: * AdguardTeam/AdGuardHome#5559 * AdguardTeam/AdGuardHome#4595 Signed-off-by: Dobroslaw Kijowski <[email protected]>
Currently compilation fails because of: ``` opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ], library: 'digital envelope routines', reason: 'unsupported', code: 'ERR_OSSL_EVP_UNSUPPORTED' ``` What's interesting package gets built but when trying to access UI there's `404: page not found` error. It has been reported in multiple places: * AdguardTeam/AdGuardHome#5559 * AdguardTeam/AdGuardHome#4595 Signed-off-by: Dobroslaw Kijowski <[email protected]>
Currently compilation fails because of: ``` opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ], library: 'digital envelope routines', reason: 'unsupported', code: 'ERR_OSSL_EVP_UNSUPPORTED' ``` What's interesting package gets built but when trying to access UI there's `404: page not found` error. It has been reported in multiple places: * AdguardTeam/AdGuardHome#5559 * AdguardTeam/AdGuardHome#4595 Signed-off-by: Dobroslaw Kijowski <[email protected]>
I've just try to build AdGuardHome with latest release ( v0.108.0-b.7 or master as of today) of Fedora 36 on x86_64
and it seem to failed due to OpenSSL compatibility issue(?)
Prerequisites
Fedora 36 / x86_64 up-to-date as of today
nodejs v16.14.0
golang v1.18.2
openssl v3.0.2
npm v8.3.1
yarn v1.22.17
(...) <= feel free to ask more!
Issue Details
Expected Behavior
build without failureActual Behavior
failed to build due to openssl issue(?)as a workarround describe here, I've try to force --openssl-legacy-provider NODE_OPTION flags
but, seem not supported / disabled by Fedora ....
Any tips to fix this issue?
The text was updated successfully, but these errors were encountered: