Error socket hang up postman ошибка

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.

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

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.

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!

answered Oct 4, 2022 at 6:14

answered Jun 23, 2020 at 11:27

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, 2020 at 6:52

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 Sep 22, 2022 at 9:29

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.

answered Jun 13, 2020 at 6:45

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

1. The url contains a port which is not commonly used AND
2. 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.

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.

answered May 11, 2021 at 12:25

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)

answered Dec 23, 2021 at 14:10

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.

answered Mar 21, 2022 at 11:12

answered Aug 3, 2022 at 10:19

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.

answered Sep 30, 2022 at 17:51

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

answered Jan 1 at 6:48

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 at 15:27

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.

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

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.

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!

answered Oct 4, 2022 at 6:14

answered Jun 23, 2020 at 11:27

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, 2020 at 6:52

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 Sep 22, 2022 at 9:29

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.

answered Jun 13, 2020 at 6:45

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

1. The url contains a port which is not commonly used AND
2. 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.

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.

answered May 11, 2021 at 12:25

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)

answered Dec 23, 2021 at 14:10

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.

answered Mar 21, 2022 at 11:12

answered Aug 3, 2022 at 10:19

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.

answered Sep 30, 2022 at 17:51

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

answered Jan 1 at 6:48

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 at 15:27