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 lo
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
I solved this by Turning off System proxy of Postman.
Open File -> Settings -> Proxy
Then Turn off Use System Proxy
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 )
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.
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).
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)