Newest update throws: SSL peer certificate or SSH remote key was not OK

Describe the bug

I have updated CODE today and now no request is working anymore. It throws the following:

SSL peer certificate or SSH remote key was not OK

To Reproduce

Idk ^^ maybe try to request a self-signet cert endpoint.

Steps to reproduce the behavior:

Go to ‘…’
Click on ‘…’
Scroll down to ‘…’
See error

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):

OS: [e.g. macOS 10.15.1]
Installation Method: [e.g. homebrew]
App Version [e.g. v7.0.3]

Additional context

Idk what the prev. version was or if there is any logs I could paste here. Just tell me.

Issue Analytics

State:
Created 3 years ago
Reactions:24
Comments:15 (1 by maintainers)

Top GitHub Comments

179reactions

baleedscommented, Jun 10, 2020

I’m also hitting the same issue.

Edit: Fixed by unchecking “Validate certificates” in settings.

7reactions

sysarch-repocommented, Jul 18, 2021

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:

If not already included, add the CA cert PEM data into the ca-certs.pem file used by the Insomnia TLS client. Note, the file location is exposed in the timeline tab of the HTTPS response (adjust the userName and Insomnia version as needed).

* successfully set certificate verify locations:
*  CAfile: C:\Users\<userName>\AppData\Local\Temp\insomnia_2021.4.1\ca-certs.pem
*  CApath: none

For mTLS, create client certificate in the Insomnia Collection Settings for the host name of the TLS server and port (e.g. “server.example.com:8443”, and upload the client cert / key PEM data your TLS client wants to use with the HTTPS request.

Top Results From Across the Web

SSL peer certificate or SSH remote key was not OK

You are probably using self-signed SSL certifiacate, which will not pass when the CURLOPT_SSL_VERIFYPEER options is set. There are two solutions:.

SSL peer certificate or SSH remote key was not OK

For few API workflow is working completely fine but for some it throws this error. I found few article saying "Get a valid...

certificate has expired] when running "dnf update" - Ask Fedora

Curl error (60): SSL peer certificate or SSH remote key was not OK for https://rpm.torproject.org/fedora/35/x86_64/repodata/repomd.xml [SSL certificate ...

Why is the SSL peer certificate or SSH remote key not OK?

Rename the downloaded file to cert.pem and move it to the directory /etc/ssl . You will need elevated privileges to modify the contents...

SSL peer certificate or SSH remote key was not OK

The solution that works for me is to change the url from https to http. Repex (before changing to http) : library(shiny) library(jsonlite) ......