[Bug] Client certificates not working on 6.2.0
See original GitHub issue- Insomnia Version: 6.0.2, 6.2.0
- Operating System: macOS Mojave
Details
In version 6.0.2, when adding Client Certificates, they would be used correctly to authenticate against my server. However, when upgrading to 6.2.0, this no longer works, the only error I get is:
Error: Problem with the local SSL certificate
To reproduce:
- Open
Workspace Settings - Navigate to
Client Certificates - Add New
- Then fill in the host and add a
CRT FileandKey File - Perform a GET request to the specified host
Let me know if there’s any more info I can gather from my client, there were no errors in the Developer Console.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:16 (4 by maintainers)
Top Results From Across the Web
Resolved Issues - Fortinet Documentation Library
Resolved Issues. The following issues have been fixed in version 6.2.0. For inquires about a particular bug, please contact Customer Service & Support....
Read more >CSCvs42748 - DOC: Firepower SSL Decryption ... - Cisco Bug
Symptom: SSL sessions with mutual authentication required, meaning both server and client need to present a certificate to authenticate, ...
Read more >Skyhigh Security Cloud Release Notes 6.2.0 (November 2022)
Certificates with issues can be passed on to the end users' browsers now, so it is up to them how to handle these...
Read more >EJBCA 6.2 Release Notes - PrimeKey Documentation
Issues Resolved in 6.2.0. Released on 18 June 2014. Bug Fixes. [ECA-3216] - Return unsigned response "unauthorized" when no default responder configured, ...
Read more >The Transport Layer Security (TLS) Protocol Version 1.2
The protocol allows client/server applications to communicate in a way that is ... The differences between this protocol and SSL 3.0 are not...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@GrayedFox Here is the screenshot. The host part is redacted but it’s basically the hostname without any port numbers.
May I suggest to test with a key that requires a passphrase?
Yes here you go (note that I changed my local stack to be http instead of https to get around this, not sure if that info is pertinent)