-
Notifications
You must be signed in to change notification settings - Fork 6
Description
For an unknow reason, in some nev we see this issue:
curl --ssl-no-revoke --insecure -X POST https://blllllh.com -x 127.0.0.1:9092 -v --proxy-insecure
and the error is:
... CONNECT phase completed
- CONNECT tunnel established, response 200
- schannel: disabled automatic use of client certificate
- ALPN: curl offers http/1.1
- schannel: next InitializeSecurityContext failed: SEC_E_INTERNAL_ERROR (0x80090304) - The Local Security Authority cannot be contacted
The reason is unknown. However it might have connected to this: https://learn.microsoft.com/en-us/answers/questions/717219/https-client-and-server-app-results-in-sec-e-inter
Issue occurs when using Postman too, but with other message:
Error: write EPROTO 52238216:error:10000070:SSL routines:OPENSSL_internal:BAD_PACKET_LENGTH:../../../../src/third_party/boringssl/src/ssl/ssl_aead_ctx.cc:257: 52238216:error:1000008b:SSL routines:OPENSSL_internal:DECRYPTION_FAILED_OR_BAD_RECORD_MAC:../../../../src/third_party/boringssl/src/ssl/tls_record.cc:298:
Seems the target HTTPS server has some issues.