Skip to content
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

SSL Handshake error with new Postman for Windows Version 7.20.0 win32 #8184

Closed
mzarify opened this issue Mar 17, 2020 · 11 comments
Closed

SSL Handshake error with new Postman for Windows Version 7.20.0 win32 #8184

mzarify opened this issue Mar 17, 2020 · 11 comments

Comments

@mzarify
Copy link

mzarify commented Mar 17, 2020

Describe the bug
Since new update of Postman (Version 7.20.0 win32) we get SSL handshake error while hitting our APIs. CRT,KEY, PFX files and Passphrase are all good. So we have installed back the older version, and then we could hit our API again.

To Reproduce
Steps to reproduce the behavior:

  1. Try to hit a service behind SSL
  2. From Settings -->Certificates, add all required CRT,KEY, PFX files and Passphrase
  3. Hit the API
  4. You will get error: "Could not get any response
    There was an error connecting to http://{{url}}"

Expected behavior
To hit API and get a response.

Screenshots
Attached
image

App information (please complete the following information):

  • Native App
  • Postman for Windows Version 7.20.0 win32
  • Windows 10
@codenirvana
Copy link
Member

@mzarify What's the error message in the Postman Console (CTRL + ALT + C).

Also, does turning off the "SSL certificate verification" form the settings fixes this issue?

@mzarify
Copy link
Author

mzarify commented Mar 17, 2020

POST {{url}}/
Error: Invalid URI "http:///%7B%7Burl%7D%7D/..."
Warning: This request did not get sent completely and might not have all the required system headers

@mzarify
Copy link
Author

mzarify commented Mar 17, 2020

We also turned OFF/ON SSL certificate verification, and it didnt help

@codenirvana
Copy link
Member

@mzarify I see this is not an issue with the SSL certificate.

The problem here is, the variable {{url}} is unresolved.
Check if you have the required environment selected before making the request.

@mzarify
Copy link
Author

mzarify commented Mar 17, 2020

@codenirvana Sorry Retry now with correct URL :)
POST https://OUR URL
Error: Client network socket disconnected before secure TLS connection was established
Warning: This request did not get sent completely and might not have all the required system headers

@mzarify
Copy link
Author

mzarify commented Mar 17, 2020

image

@codenirvana
Copy link
Member

@mzarify This is probably because of the proxy setup.
Check if turning off the global and system proxy from settings fixes this issue?

@mzarify
Copy link
Author

mzarify commented Mar 20, 2020

@codenirvana Thanks for the reply. It didn't solve the issue.

@ronhks
Copy link

ronhks commented Mar 25, 2020

We experienced the same, with 7.21.1. It doesn't matter if we disable the SLL verification to off or not. We got SSL handshake error.
I works well with 6.7.4. So we downgraded to it:
https://dl.pstmn.io/download/version/6.7.4/osx64
https://dl.pstmn.io/download/version/6.7.4/win64

@amanrique1
Copy link

I had the same error, are you sure that this service use https? check that on the request

@DannyDainton
Copy link
Contributor

Hey 👋🏻

I'm going to close this issue due to inactivity - If you're still facing the issue in the latest version we can reopen this and investigate further.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants