Postman can't reach localhost

问题:

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?

回答1:

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

Hope that helps someone out there.

回答2:

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.

回答3:

I solved this by Turning off System proxy of Postman.

Open File -> Settings -> Proxy

Then Turn off Use System Proxy

回答4:

@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.

回答5:

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

回答6:

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!

回答7:

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 )

回答8:

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.

回答9:

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

回答10:

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

回答11:

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.

回答12:

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.

回答13:

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)

回答14:

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

回答15:

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.

回答16:

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).

回答17:

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