Could not get a response - Error: Client network socket disconnected before secure TLS connection was established

I have been trying to POST a test order to an API and have been getting the “Could not get any response” message. I have tried the solutions presented here to see if I could work around it but have had no luck. The console log is returning an error that the “Client network socket disconnected before secure TLS connection was established” I’m curious about where I can look to resolve that issue? Not sure if that is a Postman issue or a device issue in regards to accessibility?

Postman Version 7.11
Mac OS Mojave 10.14.6

Hi @spencer.dicaire,

Welcome to the community! :clap:

To get started, did you disable “SSL Certificate Validation” option in the General Settings?

If so, and you are seeing this error with that off, send a screenshot so I can get more familiar with the error you are seeing.

Regards,
Orest

Hi Odan, I did try turning off the SSL Certificate Validation. I have reconfirmed the Proxy settings with my teammates, and tried turning off and on a variety of settings to see if it would help. I have also tried to adjust my internet settings to see if it is simply an error with the Wifi I am on.

1 Like

Hi @spencer.dicaire,

Thanks for the detail. Even when seeing this, it does seem difficult to troubleshoot what the issue is even with what you’ve presented.

I can’t think of what the issue could be with what you have provided. The next step that I would do, or ask is to provide a pcap file of when you try to send the api request via the proxy. This network log should provide more detail on the error being encountered.

From the error, I am inclined to believe that for some reason, your machine cannot complete a TLS handshake with the server, and might have to do with the cipher suite available on your computer. Using wireshark to get a pcap should help to clear that up.

Hope that helps.

Regards,
Orest

1 Like

We are having the same issue how did you fix it?

1 Like

Hi @spencer.dicaire. Try removing the “s” in https.

5 Likes

Thank you, it worked for me.

Removing he s also worked for me. Thanks

removing s from https result on socket hang up

After removing s from https I’m getting Gateway timeout error

same, how did you resolve