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

DEPTH_ZERO_SELF_SIGNED_CERT #277

Open
PiemP opened this issue Apr 9, 2024 · 0 comments
Open

DEPTH_ZERO_SELF_SIGNED_CERT #277

PiemP opened this issue Apr 9, 2024 · 0 comments

Comments

@PiemP
Copy link

PiemP commented Apr 9, 2024

OS: Windows 11 22631.3296
Docker desktop 4.28

Lanciando spid-saml-check, come da istruzioni, non riesco più ad effettuare il "Download" del metadata dal mio applicativo che gira in locale sulla porta 5001 tramite l'indirizzo interno "https://host.docker.internal:5001/p1/metadata-spid/metadata3.xml".

I log che ho recuperato dal terminale docker riporta queste informazioni:

2024-04-09 11:23:24 >>> 2024-04-09 11:23:24 - POST [] /api/metadata-sp/download
2024-04-09 11:23:24 events.js:377
2024-04-09 11:23:24       throw er; // Unhandled 'error' event
2024-04-09 11:23:24       ^
2024-04-09 11:23:24 
2024-04-09 11:23:24 Error: self signed certificate
2024-04-09 11:23:24     at TLSSocket.onConnectSecure (_tls_wrap.js:1515:34)
2024-04-09 11:23:24     at TLSSocket.emit (events.js:400:28)
2024-04-09 11:23:24     at TLSSocket._finishInit (_tls_wrap.js:937:8)
2024-04-09 11:23:24     at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:709:12)
2024-04-09 11:23:24 Emitted 'error' event on ClientRequest instance at:
2024-04-09 11:23:24     at TLSSocket.socketErrorListener (_http_client.js:475:9)
2024-04-09 11:23:24     at TLSSocket.emit (events.js:400:28)
2024-04-09 11:23:24     at emitErrorNT (internal/streams/destroy.js:106:8)
2024-04-09 11:23:24     at emitErrorCloseNT (internal/streams/destroy.js:74:3)
2024-04-09 11:23:24     at processTicksAndRejections (internal/process/task_queues.js:82:21) {
2024-04-09 11:23:24   code: 'DEPTH_ZERO_SELF_SIGNED_CERT'
2024-04-09 11:23:24 }
2024-04-09 11:23:24 npm ERR! code ELIFECYCLE
2024-04-09 11:23:24 npm ERR! errno 1
2024-04-09 11:23:24 npm ERR! spid-validator@1.0.0 start-prod: `node server/spid-validator.js`
2024-04-09 11:23:24 npm ERR! Exit status 1
2024-04-09 11:23:24 npm ERR! 
2024-04-09 11:23:24 npm ERR! Failed at the spid-validator@1.0.0 start-prod script.
2024-04-09 11:23:24 npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2024-04-09 11:23:24 npm WARN Local package.json exists, but node_modules missing, did you mean to install?
2024-04-09 11:23:24 
2024-04-09 11:23:24 npm ERR! A complete log of this run can be found in:
2024-04-09 11:23:24 npm ERR!     /root/.npm/_logs/2024-04-09T09_23_24_199Z-debug.log
2024-04-09 11:23:24 2024-04-09T09:23:52.234474260Z 
2024-04-09 11:23:52 > spid-validator@1.0.0 start-prod /spid-saml-check/spid-validator
2024-04-09 11:23:52 > node server/spid-validator.js

Mentre dal file nel container recupero queste informazioni:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'start-prod' ]
2 info using npm@6.14.18
3 info using node@v14.21.3
4 verbose run-script [ 'prestart-prod', 'start-prod', 'poststart-prod' ]
5 info lifecycle spid-validator@1.0.0~prestart-prod: spid-validator@1.0.0
6 info lifecycle spid-validator@1.0.0~start-prod: spid-validator@1.0.0
7 verbose lifecycle spid-validator@1.0.0~start-prod: unsafe-perm in lifecycle true
8 verbose lifecycle spid-validator@1.0.0~start-prod: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/spid-saml-check/spid-validator/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
9 verbose lifecycle spid-validator@1.0.0~start-prod: CWD: /spid-saml-check/spid-validator
10 silly lifecycle spid-validator@1.0.0~start-prod: Args: [ '-c', 'node server/spid-validator.js' ]
11 silly lifecycle spid-validator@1.0.0~start-prod: Returned: code: 1  signal: null
12 info lifecycle spid-validator@1.0.0~start-prod: Failed to exec start-prod script
13 verbose stack Error: spid-validator@1.0.0 start-prod: `node server/spid-validator.js`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:400:28)
13 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:400:28)
13 verbose stack     at maybeClose (internal/child_process.js:1088:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:296:5)
14 verbose pkgid spid-validator@1.0.0
15 verbose cwd /spid-saml-check/spid-validator
16 verbose Linux 5.15.133.1-microsoft-standard-WSL2
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "start-prod"
18 verbose node v14.21.3
19 verbose npm  v6.14.18
20 error code ELIFECYCLE
21 error errno 1
22 error spid-validator@1.0.0 start-prod: `node server/spid-validator.js`
22 error Exit status 1
23 error Failed at the spid-validator@1.0.0 start-prod script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

In precedenza non avevo mai riscontrato problemi di questo tipo. Confermo che la problematica è presente sia sull'immagine pubblicata che creando un immagine dal codice presente nella repository.

In precedenza l'operazione non dava problemi.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant