'Postman : socket hang up

I just started using Postman. I had this error "Error: socket hang up" when I was executing a collection runner. I've read a few post regarding socket hang up and it mention about sending a request and there's no response from the server side and probably timeout. How do I extend the length of time of the request in Postman Collection Runner?

Solution 1:^[1]

Socket hang up, error is port related error. I am sharing my experience. When you use same port for connecting database, which port is already in use for other service, then "Socket Hang up" error comes out.

eg:- port 6455 is dedicated port for some other service or connection. You cannot use same port (6455) for making a database connection on same server.

Solution 2:^[2]

Sometimes, this error rises when a client waits for a response for a very long time. This can be resolved using the 202 (Accepted) Http code. This basically means that you will tell the server to start the job you want it to do, and then, every some-time-period check if it has finished the job.

If you are the one who wrote the server, this is relatively easy to implement. If not, check the documentation of the server you're using.

Solution 3:^[3]

Postman was giving "Could not get response" "Error: socket hang up". I solved this problem by adding the Content-Length http header to my request

Solution 4:^[4]

I have just faced the same problem and I fixed it by close my VPN. So I guess that's a network agent problem. You can check if you have some network proxy is on.

Solution 5:^[5]

Are you using nodemon, or some other file-watcher? In my case, I was generating some local files, uploading them, then sending the URL back to my user. Unfortunately nodemon would see the "changes" to the project, and trigger a restart before a response was sent. I ignored the build directories from my file-watcher and solved this issue.

Here is the Nodemon readme on ignoring files: https://github.com/remy/nodemon#ignoring-files

Solution 6:^[6]

I solved this problem with disconnection my vpn. you should check if there is vpn connected.

Solution 7:^[7]

this happaned when client wait for response for long time try to sync your API requests from postman

then make login post and your are done

Solution 8:^[8]

"socket hang up" is proxy related issue. when we run same collection with the help of newman on jenkins then all test are passed. change the proxy setting https://docs.cloudfoundry.org/cf-cli/http-proxy.html

Solution 9:^[9]

If Postman doesn't get response within a specified time it will throw the error "socket hang up".

I was doing something like below to achieve 60 minutes of delay between each scenario in a collection:

get https://postman-echo.com/delay/10
pre request script :-
setTimeout(function(){}, [50000]);

I reduced time duration to 30 seconds:

setTimeout(function(){}, [20000]);

After that I stopped getting this error.

Solution 10:^[10]

Socket hang up error could be due to the wrong URL of the API you are trying to access in the postman. please check the URL once carefully.

Solution 11:^[11]

I had the same issue: "Error: socket hang up" when sending a request to store a file and backend logs mentioned a timeout as you described. In my case I was using mongoDB and the real problem was my collection’s array capacity was full. When I cleared the documents in that collection the error was dismissed. Hope this will help someone who faces a similar scenario.

Solution 12:^[12]

It's possible there are 2 things, happening at the same time.

The url contains a port which is not commonly used AND
you are using a VPN or proxy that does not support that port.

I had this problem. My server port was 45860 and I was using pSiphon anti-filter VPN. In that condition my Postman reported "connection hang-up" only when server's reply was an error with status codes bigger than 0. (It was fine when some text was returning from server with no error code.)

When I changed my web service port to 8080 on my server, WOW, it worked! even though pSiphon VPN was connected.

Solution 13:^[13]

Following on Abhay's answer: double check the scheme. A server that is secured may disconnect if you call an https endpoint with http.

This happened to me while debugging an ASP.NET Core API running on localhost using the local cert. Took me a while to figure out since it was inside a Postman environment and also it was a Monday.

Solution 14:^[14]

"Socket Hung Up" can be on-premise issue some time's, because, of bottle neck in %temp% folder, try to free up the "temp" folder and give a try

Solution 15:^[15]

I face the same issue in when calling a SOAP API with POSTMAN by adding the following data in the header my issue was fixed

Key:Content-Length
Value:<calculated when request is sent>

Solution 16:^[16]

In my case, adding in the header the "Content-length" parameter did the job.

My environment is

Mac: [Terminal command: sw_vers] ProductName: macOS ProductVersion: 12.0.1. (Monterey) BuildVersion: 21A559

mysql:
[Terminal command: mysql --version] Ver 8.0.27 for macos11.6 on x86_64 (Homebrew)

Apache: [Terminal command: httpd -v] Server version: Apache/2.4.48 (Unix) Server built: Oct 1 2021 20:08:18.

*Laravel [Terminal command: php artisan --version] Laravel Framework 8.76.2

Postman Version 9.1.5 (9.1.5)

Solution 17:^[17]

In my case, I was incorrectly using a port reserved for https version of my api.

For example, I was supposed to use https://localhost:6211, but I was using http://localhost:6211.

Solution 18:^[18]

socket hang up error can also occur due to backend API handling logic.

For example - I was trying to create an Nginx config file and restart the service by using the incoming API request body. This resulted in temporary disconnection of the Nginx service while handling the API request and resulted in socket hang up.

If you have tried all the steps mentioned in other comments, and still face the issue. I suggest you check the API handler code thoroughly.

I handled the above-mentioned example by calling the Nginx reset method with delay and a separate API to check the status of the prev reset request.

Solution 19:^[19]

if it helps to anybody... In my case, i just forgot to use json parser (const jsonParser = express.json();) to have access to json type of objects sending to the server from the client. Be careful, don't waste your time =)

Solution 20:^[20]

This happened to me while I was learning ASP.NET Web API.

In my case it was because the SSL certificate verification.

I was using VS Code so I oversee about SSL certificate verification and it came with https protocol.

I solved this with testing my endpoints with http protocol.

Another approach can be just disabling the SSL certificate Verification on Postman Settings.

Solution 21:^[21]

What helped for me was replacing 'localhost' in the url to http://127.0.0.1 or whatever other address your local machine has assigned localhost to.

Solution 22:^[22]

I fixed this issue by disabling Postman token header. Screenshot:

Solution 23:^[23]

It is port related error. I was trying to hit the API with an invalid port.

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution	Source
Solution 1	Love Chaudhary
Solution 2
Solution 3	PAUL SSEMAKULA
Solution 4	wd6
Solution 5	Mike Carbone
Solution 6	moslem
Solution 7	kenan ismail
Solution 8	akanshu
Solution 9	Druckles
Solution 10	Abhay Shekhar Yadav
Solution 11	Sri Darshana
Solution 12	Marc L.
Solution 13	Marc L.
Solution 14	user16044585
Solution 15	Kemal AL GAZZAH
Solution 16	Dominique Delcourt
Solution 17	Sateesh Pagolu
Solution 18	KIRAN KUMAR B
Solution 19	EgorS
Solution 20	Ensar
Solution 21	Abrucius
Solution 22	Mark Ch
Solution 23	Hamdhan Azeez T

'Postman : socket hang up

Solution 1:[1]

Solution 2:[2]

Solution 3:[3]

Solution 4:[4]

Solution 5:[5]

Solution 6:[6]

Solution 7:[7]

Solution 8:[8]

Solution 9:[9]

Solution 10:[10]

Solution 11:[11]

Solution 12:[12]

Solution 13:[13]

Solution 14:[14]

Solution 15:[15]

Solution 16:[16]

Solution 17:[17]

Solution 18:[18]

Solution 19:[19]

Solution 20:[20]

Solution 21:[21]

Solution 22:[22]

Solution 23:[23]