-
-
Notifications
You must be signed in to change notification settings - Fork 35.1k
Description
- Version: 15
- Platform: Mac M1
- Subsystem: Elasticsearch over TLS
What steps will reproduce the bug?
Try to connect to an Elasticsearch cluster that is configured with a valid SSL certificate
How often does it reproduce? Is there a required condition?
This failure is constant the connection will fail with the following error:
=============== Error start ==============================
node:_tls_common:333
c.context.loadPKCS12(toBuf(pfx));
^
Error: Unable to load PFX certificate
at Object.createSecureContext (node:_tls_common:333:17)
at Object.connect (node:_tls_wrap:1614:48)
at HttpsAgent.createConnection (node:https:137:22)
at HttpsAgent.createSocket (/Users/xxxx/yyyy_projects/aaa-dev/zzzzz-service/node_modules/agentkeepalive/lib/_http_agent.js:265:26)
at HttpsAgent.createSocket (/Users/xxxx/yyyy_projects/aaa-dev/zzzzz-service/node_modules/agentkeepalive/lib/agent.js:77:11)
at HttpsAgent.addRequest (/Users/xxxx/yyyy_projects/aaa-dev/zzzzz-service/node_modules/agentkeepalive/lib/_http_agent.js:239:10)
at new ClientRequest (node:_http_client:309:16)
at Object.request (node:https:333:10)
at HttpConnector.request (/Users/xxxx/yyyy_projects/aaa-dev/zzzzz-service/node_modules/elasticsearch/src/lib/connectors/http.js:182:23)
at sendReqWithConnection (/Users/xxxx/yyyy_projects/aaa-dev/zzzzz-service/node_modules/elasticsearch/src/lib/transport.js:263:35)
at Object.utils.applyArgs (/Users/xxxx/yyyy_projects/aaa-dev/zzzzz-service/node_modules/elasticsearch/src/lib/utils.js:188:19)
at wrapper (/Users/xxxx/yyyy_projects/aaa-dev/zzzzz-service/node_modules/lodash/lodash.js:5255:19)
at processTicksAndRejections (node:internal/process/task_queues:76:11) {
code: 'ERR_CRYPTO_OPERATION_FAILED'
=============== Error end ===============================
What is the expected behavior?
That the connection will succeed
What do you see instead?
See above error message.