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
Newest update throws: SSL peer certificate or SSH remote key was not OK #2255
Comments
This works: curl --request POST \
--url https://api.m8finder.lcl/auth/login \
--header 'content-type: application/json' \
--data '{
"email": "Xxxxx",
"password": "123456"
}' Directly exported from Insomnia |
I'm also hitting the same issue. Edit: Fixed by unchecking "Validate certificates" in settings. |
Works, but this is a security vulnerability. We have not found a way to get this working with validation aside from downgrading insomnia. Best I can tell is it is some weird incompatibility with how my company's cert authority issues certs and insomnia. Would really like to see a fix for this so we can upgrade to latest versions. |
This is required to login to Insomnia accounts as well (fresh install) |
I can confirm that downgrading to v7.1.0 solves this and certificate validation works as intended. |
Im using v 7.1.1 and im experimenting the same issue when i test my deployed api, wich it's over a ( from Let's Encrypt ) valid SSL cert. |
running into this when i'm running a secure site on localhost and a self signed cert (setup with
|
Same issue.. All of a sudden I keep getting
|
Any plans on addressing this? We are stuck using a version of Insomnia that is well over a year old... |
I have experienced the "SSL certificate problem: unable to get local issuer certificate" problem on my Win10 laptop and have solved it as follows for Insomnia 2021.4.1:
|
just a clarification on prevous response by @richardjudgeman the "CAfile" is just a text file with a list of base64 encoded certificates. i think insomnia needs a more apparent way of adding custom CAs. Many people use it corporate environment and probably just turn off the SSL valdation, which is not good. |
@ubeogesh what is the path of the CAFile ? |
I am using an application API locally with an invalid ssl certificate and insomnia is not able to call it, it gives me a Error: SSL peer certificate or SSH remote key was not OK error I went to the General settings and unchecked validate certificates checkbox, but it still shows me the same error.. The request works on my browser well.. It seems like a bug in insomnia where it is not disabling ssl validation. The request even works fine on postman after disabling ssl validation. |
@MB175 i don't think this is a viable approach anymore - i cannot find the CAfile anymore. Previously it could be found from the log on the "Timeline" tab. So apparently now the only way is to turn off certificate validation |
Okay i see, thanks for replying. Some day there will be a way I guess |
I'm getting the same issue when I run the request in Insomnia CLI. "[network] Response failed req=req_9ea8430a7dd04ae8a495b9cd5af8d9b6 err=Error: SSL peer certificate or SSH remote key was not OK". |
I added custom CA and still getting same |
Any updates? This is not even working for me in a production environment. |
We are actively working on a resolution for this issue, we will link this issue to the PRs once they come out. |
We were able to determine the cause of this issue and we will try to get it merged for our December release next week. It was a tricky one, thanks @notjaywu for the contribution. |
This issue should be finally fixed in the recently released v8.5. |
We switched to using Using
Using other solutions like OpenSSL, allows us to support TLS 1.3 and client certificates in the app, but we lose access to the macOS Keychain. But macOS Keychain certificates could be imported into Insomnia if we use OpenSSL (you would have them in two places, Insomnia + Keychain). So we will revert to using OpenSSL on macOS in the next |
Describe the bug
I have updated CODE today and now no request is working anymore. It throws the following:
To Reproduce
Idk ^^ maybe try to request a self-signet cert endpoint.
Steps to reproduce the behavior:
Expected behavior
No browser or my App is throwing this so I expect it to just work.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Idk what the prev. version was or if there is any logs I could paste here. Just tell me.
The text was updated successfully, but these errors were encountered: