Postman can't reach localhost

Question

I am in a corporate env so I have to use a proxy to reach servers. This works well in postman and in browsers. What I can't reach is localhost in postman but I can reach localhost in the browser.

I am running Postman for Linux Version 6.0.9. I have tried reaching localhost:9082/rest/myapi.... and 127.0.0.1:9082/rest/myapi with both global proxy and system proxy turned on and with either turned on and with non turned on. In all cases I am not able to reach localhost.

What I get as an response is an error page from the proxy server! Someway the call gets out on the network instead of being kept on my machine.

The postman console:

My request headers are:

Cache-Control →no-cache
Connection →Keep-Alive
Content-Length →986
Content-Type →text/html; charset=utf-8
Pragma →no-cache
Proxy-Connection →Keep-Alive

My response headers are:

cache-control:"no-cache"
pragma:"no-cache"
content-type:"text/html; charset=utf-8"
proxy-connection:"Keep-Alive"
connection:"Keep-Alive"
content-length:"986"

My response body is an html page.

How can I make a call to localhost work with postman?

It seems this has been solved in v.7.0.9. For versions before that, [Nayak's answer](https://stackoverflow.com/a/54288710/5122657) below worked for me. — Leonard AB, May 10 '19 at 07:40
Postman 7.2.1 was working then started getting a 'Could not get any response' error connecting to localhost. Turned off 'Use System Proxy' in settings, and it started working again. We're not using a proxy as far as I know. — Kevin Hooke, Jun 21 '19 at 18:16

score 163 · Answer 1 · edited Dec 24 '22 at 20:44

163

I was having similar issue with HTTP calls to local ASP.NET Core Web API apps. Changing the proxy settings didn't fix it for me.

Finally fixed it by turning off File > Settings > General > SSL Certificate Verification

edited Dec 24 '22 at 20:44

starball

20,030
7
43
238

answered Dec 30 '18 at 00:49

Tonmoy

2,008
2
10
16

1

Postman will take the proxy settings from some environment variables (http_proxy, HTTPS_PROXY, etc) even if they are turned off from the UI – Rohit Gupta Feb 19 '19 at 11:58
This will work, but [Peter Matisko's answer below](https://stackoverflow.com/a/52853979/336648) is probably both simpler and better, even if it has racked up significantly fewer votes so far; it avoids messing with / disabling SSL verification. – Kjartan Jun 19 '20 at 07:06

Peter Matisko · Answer 2 · 2018-10-17T11:44:20.227

44

I have the same issue. What works for me is:

Open File -> Settings -> Proxy

Then, enable proxy and put 127.0.0.1 : 80, if your web server runs on 80.

In the git thread, they say it is a known issue, so hopefully it will get resolved soon.

edited Oct 17 '18 at 11:44

answered Oct 17 '18 at 11:37

Peter Matisko

2,113
1
24
47

1

This solution seems by far to be the easiest way around this problem. No need to mess with environment variables, no need to open possible security holes. – Eric Antoine Scuccimarra Aug 23 '19 at 06:24
Worked for me, but I wish I understood why. I noticed when I `ping localhost`, I get the IPv6 address `::1` not the IPv4 address `127.0.0.1`. Possibly related? – TBirkulosis Aug 28 '19 at 15:57
@TBirkulosis I am not sure, if the behaviour without the proxy isn't actually a bug. Postman probably reaches to a wrong place. I haven't found a proper answer either. – Peter Matisko Aug 28 '19 at 16:21

score 20 · Answer 3 · answered Jul 02 '19 at 14:02

20

I solved this by Turning off System proxy of Postman.

Open File -> Settings -> Proxy

Then Turn off Use System Proxy

answered Jul 02 '19 at 14:02

Menuka Ishan

5,164
3
50
66

1

How frustrating when I've tried every other answer up to this point before finding the one that works. It seems there's any number of ways for it not to work with very little indication of what the problem is. – DaveDev Jul 13 '20 at 04:10
@DaveDev closest thing I can give for you that it should be something with corporate proxies. You might need some networking wisdom too to find this out. But my friend I have backlogs to finish before I sleep :) – Menuka Ishan Jul 30 '20 at 18:02

score 12 · Answer 4 · answered Aug 17 '19 at 15:57

12

@Menuka Ishan Answer is correct. But in mac only if we change the turn off proxy won't work. You need to turn off the SSL Certificate verification also you need to disable.

answered Aug 17 '19 at 15:57

Aravindhan R

270
5
26

Please do not switch off SSL verification. This could be potentially a huge security risk. – Dharman Aug 17 '19 at 16:01
1

@Dharman. But if i didn't turn off SSL verification post man is not working. There is any other way? – Aravindhan R Aug 17 '19 at 17:47
The .NET Core Web API tutorial walks you thru turning off this option also: See => https://learn.microsoft.com/en-us/aspnet/core/tutorials/first-web-api?view=aspnetcore-3.1&tabs=visual-studio#install-postman It is helpful for localhost development – raddevus May 19 '20 at 18:00

score 11 · Accepted Answer · answered Mar 06 '18 at 12:38

I found a temporary solution:

In terminal, go to the directory where postman is installed and add:

machine@dev:~/Documents/Postman$ export NO_PROXY=localhost,127.0.0.1
machine@dev:~/Documents/Postman$ ./Postman

This will make calls to localhost work.

I found a similar problem on Windows machines here

score 7 · Answer 6 · answered Feb 12 '19 at 11:07

The problem mentioned as an issue here. You should just write a simple batch file like this:

set HTTP_PROXY=
set http_proxy=
set HTTPS_PROXY=
set https_proxy=
START %LOCALAPPDATA%\Postman\Update.exe --processStart "Postman.exe"

open a simple text file, save this as a ".bat" file, and just run it!

score 4 · Answer 7 · answered May 21 '20 at 08:07

I also faced the same issue, but the trick was I implemented both the methods that were stated earlier in the stack. First I turned off the postman proxy as shown in below image.

Click Settings -> Proxy

And then turned off the SSL certificate verification check button.

Click Settings -> General

And then tried to hit my local server and finally it worked.

score 3 · Answer 8 · answered May 19 '20 at 18:08

While attempting to Get https://localhost:5001/WeatherForecast via PostMan while developing a basic .NET Core (3.1) Web API (on Ubuntu Linux) I got the error:

Could not get any response There was an error connecting to https://localhost:5001/WeatherForecast.

I didn't notice the actual solution in the things to try at first, but if you check the highlighted text in the image you will see it.

You can see that the option is turned on in PostMan by default:

I turned the SSL Certificate Verification off and tried again and it worked.

score 2 · Answer 9 · answered Jan 21 '19 at 11:10

2

If you are under corporate proxy and you are deploying your webapplication in localhost then no need to set proxy configuration like

http://username:password@corporateProxyServer:ServerPort in postman (Global Proxy Configuration).

As the app is deployed in local machine just use the localhost configuration in setting -> Global Proxy Configuration as :

 proxy server : 127.0.0.1
 port : 8300 (this is the port where the web application is running )

answered Jan 21 '19 at 11:10

S Debasish Nayak

263
3
3

This one worked for me. But it seems the problem has been solved in v7.0.9 – Leonard AB May 10 '19 at 07:38

score 1 · Answer 10 · answered Feb 25 '20 at 13:45

My problem was that i was setting an invalid Header token and it gave me the error

Error: Header name must be a valid HTTP token ["Accept "] Warning: This request did not get sent completely and might not have all the required system headers

Just check your Headers.

score 1 · Answer 11 · answered Apr 08 '20 at 16:57

Adding another potential answer to this for people to check after they've tried the other ideas here.

I was able to solve my own problem by checking the Postman console (View -> Show Postman Console) and then examining the error from the request (in my case it was because I had a newline character on an auth token).

score 1 · Answer 12 · answered Apr 19 '20 at 15:43

1

In my case, I had to precede the localhost with https://

answered Apr 19 '20 at 15:43

Ali Bdeir

4,151
10
57
117

score 0 · Answer 13 · answered Apr 25 '19 at 16:08

These steps solved this issue after 1 whole day struggle: 1) HTTP_PROXY= proxy.company.com:port HTTPS_PROXY=proxy.company.com:port to user variables, not to System variables. Make sure the the case is all cap. 2) Updating newtwork driver, and turning on Windows Defender......Make sure you don't see no reds in here.

score 0 · Answer 14 · answered May 08 '19 at 06:59

I was not able to make any calls from postman to docker container running Couchbase Server. Very frustrating. Turns out I had proxy setting configured to some aws instance which has been long deleted.

Goto setting and remove the proxy setting and it worked like a charm on localhost/127.0.0.1/mac laptop eno IP addr or 0.0.0.0

score 0 · Answer 15 · answered Jun 10 '19 at 03:30

0

In my case, I was using django-tenants and had to add the domain for the tenant in etc/hosts to get it working on localhosts. My entry for 127.0.0.1 now looks like

127.0.0.1 localhost test.localhost

answered Jun 10 '19 at 03:30

theTypan

5,471
6
24
29

score 0 · Answer 16 · answered Aug 31 '19 at 14:51

0

My problem was forgetting to select Environment. From the drop down where you see No Environment in the image, select the name of your environment.

answered Aug 31 '19 at 14:51

7guyo

3,047
1
30
31

score 0 · Answer 17 · answered Sep 06 '19 at 13:48

Menuka Ishan's solution above saved my hours of pain! I left the Global Proxy Configuration switched ON and changed the Proxy Server to 127.0.0.1. Switched OFF the Use System Proxy. I already had the entry 127.0.0.1 localhost in my hosts file under the path C:\Windows\System32\drivers\etc.

Redar · Answer 18 · 2019-10-25T11:42:49.103

0

If you have active proxy in your system then make sure Global Proxy Configuration and Use System Proxy are turned off. To do this go to Postman preferences > Proxy. You can also try sending a request in postman without typing localhost (e.g. :8080/send)

edited Oct 25 '19 at 11:42

answered Oct 25 '19 at 11:10

Redar

83
10

score 0 · Answer 19 · answered Nov 18 '19 at 22:02

0

i think i also found a perfect fix. First you turn on global proxy configurations, add your local machine Ip which is 127.0.0.1,then also add localhost in the bypass. Also turn off SSL verification. It worked for me

answered Nov 18 '19 at 22:02

Soji

1

score 0 · Answer 20 · edited Feb 28 '23 at 21:23

0

This worked for me, I disable the parameter host in the header.

HOST Disabled

edited Feb 28 '23 at 21:23

marc_s

732,580
175
1,330
1,459

answered Jan 11 '22 at 00:41

EdoElric

1
1

score 0 · Answer 21 · answered Feb 17 '22 at 09:43

If anyone is looking for a solution to WooCommerce local install, here are the steps to make this work:

Go to Wordpress Admin > WooCommerce > Settings > Advanced
Create new API key, give it a name
Copy the Consumer Key & Consumer Secret to your text editor
Open Postman
Create new connection Set the URL for testing (GET) : http://mylocalsite/wp-json/wc/v3/orders (change "mylocalsite" to yours)
Click on Authorization tab
Now here is the main change: Although in WC Rest docs, it says to use the "Basic Auth" - IT WILL NOT WORK. Since usually your localhost is HTTP and not HTTPS. So "Basic Auth" is not relevant in our case.
You will need to change the Authorization to OAuth 1.0
Set Consumer Key & Consumer Secret respectively as it shows in Woocommerce
Click "Send" - it should work now

If still you have problems, try one by one the following:

File > Settings > Turn off SSL Verification
File > Settings > Turn off "Automatically follow redirects"

score 0 · Answer 22 · answered Jun 07 '23 at 03:06

0

I had the same problem that couldn't get response from localhost. I downloaded postman to my computer desktop version then I could get back response.

answered Jun 07 '23 at 03:06

sher

15
4

Postman can't reach localhost

22 Answers22

Linked