Debian SID例程更新结果:“错误:错误:0308010C:数字信封例程:: Uncpported;
在对服务器(Debian SID)进行例行更新之后,我将不再启动零UI开发(实际上我无法启动任何 note nodejs
开发服务器):
zero@zdev:~/zero-ui$ ZU_CONTROLLER_TOKEN=whatever yarnpkg dev
[1] [nodemon] 2.0.15
[1] [nodemon] to restart at any time, enter `rs`
[1] [nodemon] watching path(s): *.*
[1] [nodemon] watching extensions: js,mjs,json
[1] [nodemon] starting `node ./bin/www`
[0] ℹ 「wds」: Project is running at http://192.168.7.122/
[0] ℹ 「wds」: webpack output is served from /app
[0] ℹ 「wds」: Content not from webpack is served from /home/zero/zero-ui/frontend/public
[0] ℹ 「wds」: 404s will fallback to /app/
[0] Starting the development server...
[0]
[0] Error: error:0308010C:digital envelope routines::unsupported
[0] at new Hash (node:internal/crypto/hash:67:19)
[0] at Object.createHash (node:crypto:130:10)
[0] at module.exports (/home/zero/zero-ui/node_modules/webpack/lib/util/createHash.js:135:53)
[0] at NormalModule._initBuildHash (/home/zero/zero-ui/node_modules/webpack/lib/NormalModule.js:417:16)
[0] at handleParseError (/home/zero/zero-ui/node_modules/webpack/lib/NormalModule.js:471:10)
[0] at /home/zero/zero-ui/node_modules/webpack/lib/NormalModule.js:503:5
[0] at /home/zero/zero-ui/node_modules/webpack/lib/NormalModule.js:358:12
[0] at /home/zero/zero-ui/node_modules/loader-runner/lib/LoaderRunner.js:373:3
[0] at iterateNormalLoaders (/home/zero/zero-ui/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
[0] at iterateNormalLoaders (/home/zero/zero-ui/node_modules/loader-runner/lib/LoaderRunner.js:221:10)
[0] /home/zero/zero-ui/node_modules/react-scripts/scripts/start.js:19
[0] throw err;
[0] ^
[0]
[0] Error: error:0308010C:digital envelope routines::unsupported
[0] at new Hash (node:internal/crypto/hash:67:19)
[0] at Object.createHash (node:crypto:130:10)
[0] at module.exports (/home/zero/zero-ui/node_modules/webpack/lib/util/createHash.js:135:53)
[0] at NormalModule._initBuildHash (/home/zero/zero-ui/node_modules/webpack/lib/NormalModule.js:417:16)
[0] at /home/zero/zero-ui/node_modules/webpack/lib/NormalModule.js:452:10
[0] at /home/zero/zero-ui/node_modules/webpack/lib/NormalModule.js:323:13
[0] at /home/zero/zero-ui/node_modules/loader-runner/lib/LoaderRunner.js:367:11
[0] at /home/zero/zero-ui/node_modules/loader-runner/lib/LoaderRunner.js:233:18
[0] at context.callback (/home/zero/zero-ui/node_modules/loader-runner/lib/LoaderRunner.js:111:13)
[0] at /home/zero/zero-ui/node_modules/react-scripts/node_modules/babel-loader/lib/index.js:59:103 {
[0] opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
[0] library: 'digital envelope routines',
[0] reason: 'unsupported',
[0] code: 'ERR_OSSL_EVP_UNSUPPORTED'
[0] }
[0] cd frontend && cross-env FAST_REFRESH=true yarn start exited with code 1
注意这似乎与我在Internet上和其他地方讨论的问题似乎并不是相同的问题(node
v16-> v17中的破坏变化)与我当前有:
zero@zdev:~/zero-ui$ node --version
v16.15.0
注意:我尝试添加,但我尝试了node_options = - openssl-legacy-provider
给我的选项,但毫不奇怪,这不起作用(/usr/bin/bin/node:-openssl-legacy-provider in Node_options 我认为这意味着此选项是在V17中添加的,并且在破裂更改之前毫无用处)。
我强烈怀疑我的Debian SID负有责任,但我无法理解哪个。
还要注意,这是当前Debian SID的特定于:它在全新的安装(使用容器)上可重现,并且将在Debian Bookworm上进行完全相同的安装。
我该如何克服这一点? 蒂亚!
After routine update of my server (Debian Sid) I am no longer able to start zero-ui development (actually I'm unable to start any nodejs
development server):
zero@zdev:~/zero-ui$ ZU_CONTROLLER_TOKEN=whatever yarnpkg dev
[1] [nodemon] 2.0.15
[1] [nodemon] to restart at any time, enter `rs`
[1] [nodemon] watching path(s): *.*
[1] [nodemon] watching extensions: js,mjs,json
[1] [nodemon] starting `node ./bin/www`
[0] ℹ 「wds」: Project is running at http://192.168.7.122/
[0] ℹ 「wds」: webpack output is served from /app
[0] ℹ 「wds」: Content not from webpack is served from /home/zero/zero-ui/frontend/public
[0] ℹ 「wds」: 404s will fallback to /app/
[0] Starting the development server...
[0]
[0] Error: error:0308010C:digital envelope routines::unsupported
[0] at new Hash (node:internal/crypto/hash:67:19)
[0] at Object.createHash (node:crypto:130:10)
[0] at module.exports (/home/zero/zero-ui/node_modules/webpack/lib/util/createHash.js:135:53)
[0] at NormalModule._initBuildHash (/home/zero/zero-ui/node_modules/webpack/lib/NormalModule.js:417:16)
[0] at handleParseError (/home/zero/zero-ui/node_modules/webpack/lib/NormalModule.js:471:10)
[0] at /home/zero/zero-ui/node_modules/webpack/lib/NormalModule.js:503:5
[0] at /home/zero/zero-ui/node_modules/webpack/lib/NormalModule.js:358:12
[0] at /home/zero/zero-ui/node_modules/loader-runner/lib/LoaderRunner.js:373:3
[0] at iterateNormalLoaders (/home/zero/zero-ui/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
[0] at iterateNormalLoaders (/home/zero/zero-ui/node_modules/loader-runner/lib/LoaderRunner.js:221:10)
[0] /home/zero/zero-ui/node_modules/react-scripts/scripts/start.js:19
[0] throw err;
[0] ^
[0]
[0] Error: error:0308010C:digital envelope routines::unsupported
[0] at new Hash (node:internal/crypto/hash:67:19)
[0] at Object.createHash (node:crypto:130:10)
[0] at module.exports (/home/zero/zero-ui/node_modules/webpack/lib/util/createHash.js:135:53)
[0] at NormalModule._initBuildHash (/home/zero/zero-ui/node_modules/webpack/lib/NormalModule.js:417:16)
[0] at /home/zero/zero-ui/node_modules/webpack/lib/NormalModule.js:452:10
[0] at /home/zero/zero-ui/node_modules/webpack/lib/NormalModule.js:323:13
[0] at /home/zero/zero-ui/node_modules/loader-runner/lib/LoaderRunner.js:367:11
[0] at /home/zero/zero-ui/node_modules/loader-runner/lib/LoaderRunner.js:233:18
[0] at context.callback (/home/zero/zero-ui/node_modules/loader-runner/lib/LoaderRunner.js:111:13)
[0] at /home/zero/zero-ui/node_modules/react-scripts/node_modules/babel-loader/lib/index.js:59:103 {
[0] opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
[0] library: 'digital envelope routines',
[0] reason: 'unsupported',
[0] code: 'ERR_OSSL_EVP_UNSUPPORTED'
[0] }
[0] cd frontend && cross-env FAST_REFRESH=true yarn start exited with code 1
Note this does not seem to be the same problem I found discussed here and elsewhere on the internet (breaking change in node
v16->v17) as I currently have:
zero@zdev:~/zero-ui$ node --version
v16.15.0
Note: I tried nonetheless adding NODE_OPTIONS=--openssl-legacy-provider
to my options but this, rather unsurprisingly, does not work (/usr/bin/node: --openssl-legacy-provider is not allowed in NODE_OPTIONS
which I take it means this option was added in v17 and is useless before the breaking change).
I strongly suspect some update in my debian sid is responsible, but I'm unable to understand which.
Note also this is specific to current Debian Sid: It is reproducible on a brand new install (using containers) and will not appear doing the exact same install on Debian Bookworm.
How can I overcome this?
TiA!
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
我有山姆问题。我已经将Node.js升级到17.7.2,并遇到了此错误。然后升级到18.4,但仍然有错误。然后使用旧式选项 - 无成功。然后将Node.js降级至16.15.1,试图将WebPack上升和降级(4.46 => 5.63 => 4.46),但我仍然有错误。即使是卸载了node.js,删除了所有的缓存文件夹和new new node node.js也没有帮助。
我绝对不明白的是,错误消息后的最后一行是“ node.js v17.7.2”,这绝对不在我的系统上。
整个问题始于“ npx create-nuxt-app”,就像我尝试创建我的NUXT应用程序一样。真是一团糟。
I have the sam problem. I've upgraded node.js to 17.7.2 and run into this error. Then upgraded to 18.4 and still got the error. Then using the legacy option - without success. Then downgraded node.js to 16.15.1, tried to up- and downgrade the webpack (4.46 => 5.63 => 4.46) but I got still the error. Even an uninstallation of node.js, removing all the cache folders and a brand new installation of node.js hadn't helped.
What I absolutely don't understand is, that the last line after the error message is "Node.js v17.7.2" which is definitely NOT on my system.
This whole issue started with "npx create-nuxt-app", simply that - as I tried to create my nuxt application. What a mess.