Postman : socket hang up

Question

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?

nope. its not working. Im sending a file(an image with the size 20kb) — kenn_ross, Jun 16 '17 at 09:57
Have same issue. I run postman collection 100 times (with different variables) and 1-2 requests failed with socked hang up. — IliaEremin, Feb 06 '18 at 16:17
You can change the timeout 0 in the settings to eliminate the timeout. but Socket hang up is not a timeout error. I'm facing the same thing on a form post. — Aaron McMillin, Feb 23 '18 at 21:14
I am getting the error as well on a post request I have been executing all day, and that still works in SOAP-UI. No clue what is causing the issue... — Zoop, Apr 06 '18 at 18:53
late to add but this can help someone . In my case, i had kept debug pointers in my IDE for debugging purpose. First,i did one POST request to localhost API and was debugging, in parallel tried to do another POST request to different endpoints. In this case, Socket hang up occured. It was due to proxy setting. Check this thread for more information - https://community.postman.com/t/could-not-get-any-response-socket-hang-up/11603/4 Note: I was using a VPN — kaarthick raman, Jun 15 '20 at 10:43
adding http:// | https:// (depending on which is the case) to the endpoint url solved my problem. — Oluwadamilola Adegunwa, May 05 '21 at 17:24

score 35 · Answer 1 · answered Jun 20 '22 at 13:04

35

For me it was because my application was switched to https and my postman requests still had http in them. Changing postman to https fixed it.

answered Jun 20 '22 at 13:04

BrianK

2,357
3
32
41

How did you switch to `https` ? Do you mean in the request address bar ? Because I'm requesting `GET http://localhost:49153/api/stocks/get` with response `Error: socket hang up`. – BaltoStar Jan 02 '23 at 07:11
yes, try https on that get call – BrianK Jan 02 '23 at 13:14
Just tried that, my error changed to "Error: tunneling socket could not be established, statusCode=502" – MonneratRJ May 16 '23 at 17:11

score 17 · Answer 2 · answered May 07 '19 at 13:20

17

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.

answered May 07 '19 at 13:20

Love Chaudhary

302
2
13

For me , the server was in https and I was calling in http – Mostafa Feb 12 '23 at 08:12

Koby 27 · Answer 3 · 2020-07-05T12:08:59.277

9

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.

edited Jul 05 '20 at 12:08

answered May 09 '20 at 14:27

Koby 27

1,049
1
8
17

how can you return any code if the server hasn't yet finished its job? – arxakoulini Feb 02 '23 at 14:02
The first sentence in the attached link: "HTTP Status 202 indicates that the request has been accepted for processing, but the processing has not been completed." – Koby 27 Mar 14 '23 at 17:43

score 5 · Answer 4 · answered Aug 19 '20 at 14:45

5

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

answered Aug 19 '20 at 14:45

PAUL SSEMAKULA

507
5
4

thank you, it worked for me. I copied the request from some other source and then changed the payload data in my POST request. so, there was a mismatch in Content-Length. :) – Jawand Singh Feb 15 '21 at 12:55
7

And what length should that be? – Oliver Dixon Jun 13 '22 at 20:38
@OliverDixon, it should be automatically calculated (default option). Also, for me the issue was in disabling Host header – iOS Nov 23 '22 at 12:24
So for example, testing with postman, how do I calculate the length? – Oliver Dixon Nov 24 '22 at 09:04
It also works if you simply add `Content-Type` and I added `application/vnd.api+json` as the value. – Harrison O May 11 '23 at 16:05

score 2 · Answer 5 · answered Aug 06 '20 at 15:02

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

score 2 · Answer 6 · answered Sep 08 '20 at 02:11

2

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.

answered Sep 08 '20 at 02:11

wd6

29
1

Thank youuuu! I still often forget that VPNs are an all-source of problems! (when one works in IT) – Bob Jan 07 '22 at 23:12

score 2 · Answer 7 · answered Oct 04 '22 at 06:14

I defined Authenticate method to generate a token and mentioned its return type as nullable string as:

public string? Authenticate(string username, string password) 
{
  if(!users.Any(u => u.Key==username && u.Value == password))
    {
      return null;
    }
  var tokenHandler = new JwtSecurityTokenHandler();


  var tokenKey = Encoding.ASCII.GetBytes(key);
  var tokenDescriptor = new SecurityTokenDescriptor()
  {
    Subject = new ClaimsIdentity(new Claim[]
    {
       new Claim(ClaimTypes.Name, username)
    }),
    Expires = DateTime.UtcNow.AddHours(1),
    SigningCredentials = new SigningCredentials(new 
    SymmetricSecurityKey(tokenKey), 
    SecurityAlgorithms.HmacSha256Signature)
  };
   var token = tokenHandler.CreateToken(tokenDescriptor);
   return tokenHandler.WriteToken(token);
}

Changing nullable string to simply string fixed "Socket Hang Up" issue for me!

score 1 · Answer 8 · answered Jun 23 '20 at 11:27

1

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.

answered Jun 23 '20 at 11:27

Abrucius

101
6

score 1 · Answer 9 · answered Oct 21 '20 at 06:52

1

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

answered Oct 21 '20 at 06:52

kenan ismail

31
8

score 1 · Answer 10 · answered Nov 05 '20 at 03:41

1

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.

answered Nov 05 '20 at 03:41

Abhay Shekhar Yadav

103
1
4

Verify https URL or Http URL in variables of POSTMAN – HydPhani Aug 23 '23 at 13:06

score 1 · Answer 11 · answered Sep 22 '22 at 09:29

1

In my case, I had to provide --ssl-client-key and --ssl-client-cert files to overcome these errors.

answered Sep 22 '22 at 09:29

Abhishek Sharma

23
4

score 0 · Answer 12 · edited Aug 27 '19 at 13:47

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.

score 0 · Answer 13 · answered Jun 13 '20 at 06:45

0

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

answered Jun 13 '20 at 06:45

Kourosh

917
1
11
24

score 0 · Answer 14 · edited May 11 '21 at 12:11

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.

score 0 · Answer 15 · answered May 11 '21 at 12:25

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.

score 0 · Answer 16 · answered Dec 23 '21 at 14:10

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)

score 0 · Answer 17 · answered Mar 21 '22 at 11:12

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.

score 0 · Answer 18 · answered Aug 03 '22 at 10:19

0

For me it was giving Socket Hung Up error only while running Collection Runner not with single request. Adding a small delay (100-300ms) in the collection Runner solved issue for me.

answered Aug 03 '22 at 10:19

Shubham Jain

876
1
9
17

score 0 · Answer 19 · answered Sep 30 '22 at 17:51

Great error, it is so general that for everyone something different helps.

In my case I was not able to fix it and what is really funny is fact that I am expecting to get multipart file on one endpoint. When I prepare request in postman I get "Error: socket hang up". If I change for other endpoint(even not existing) is exactly that same error. But when I call any endpoint without body that request works and after that all subsequent attempts works perfectly.

In my case this is purely postman issue. Any request using curl is never giving that error.

score 0 · Answer 20 · answered Jan 01 '23 at 06:48

For me the issue was related to the mismatch of the http versions on the client and server.

Client was assuming http v2 while server (spring boot/ tomcat) in the case was http v1

When on the server I configured server to v2, the issue got resolved in a go.

In spring boot you can configure the http v2 as below:-

server.http2.enabled=true

Note - Also the scenario was related to using client auth mechanism (i.e. MTLS)

Without client auth/ MTLS it worked without issues but for client auth the version setting in spring boot was the important rescue point

score 0 · Answer 21 · answered Apr 20 '23 at 15:27

0

in my case, it was Web postman client issue,

when i request GET on same condition on Postman App (not Web), it resolved

answered Apr 20 '23 at 15:27

Implermine

323
3
8

Postman : socket hang up

21 Answers21