-
Notifications
You must be signed in to change notification settings - Fork 859
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not get any response - Error: connect ECONNREFUSED #6205
Comments
Can you check your OS proxy settings or proxy settings in Postman? |
I was having the same issue on Mac Postman, Version 7.0.7 (7.0.7) Just add a extra slash, that trailing slash is important. i.e try "node4:9200/search/_search/ " Happy coding :) |
@shamasis Postman proxy settings are off @baibhavtripathi Trailing slash does not work. |
@camohub can you try making the same call using |
@camohub did you manage to recheck using curl? Another thing that interests me is that can you try enabling “use system proxy”? If your network has a proxy and is defined in OS, then this setting will enable postman to use the same. I’m stressing on proxy because the symptoms you mentioned gives me the feeling that localhost is excluded from proxy and hence is the only endpoint that’s working. |
I made a request in PHP. It works. It is curl request. Postman still does not work. Any suggestions? I am not familiar with proxy. Why I need it? PS: URL of the request looks like node4:9200/search/_search Is it correct? Its the same url as before when it worked. |
Still no solution. Any suggestions? |
am also having this same issue |
As I found out I am behind the proxy server. Is it related to this problem? |
@camohub Like I was guessing, proxy seems to be the likely culprit. But you never know! :-p In your proxy setting in Postman App, can you enable using system proxy and then in your system proxy, exclude the domain |
@Westernwells - is it "same" issue... by that I mean, "http://localhost/" works but nothing else on local works? If there is a major variation from that then please file a separate issue. |
I'm running into the same issue. Even if I try getting all my collections using the Postman API key (https://community.getpostman.com/t/where-do-you-see-your-own-uid-for-collection/3537) I generated I get a 'connection refused' response. Request: curl https://api.getpostman.com/collections?apikey=XXXXXXXXXXXXXXX/ -v Response: It may be a proxy issue - I did try specifying the proxy IP address and port in Settings and all tried with and without 'Use System Proxy I also tried to make the request outside the firewall - I get a more explicit error there: 'AuthenticationError'. I've copied the API key directly from the Postman Integrations, Existing API Keys page. It currently has a status of 'Enabled' and 'Last Accessed' of 'Never Used'. 'Date Created' is June 7, 2019. I've ran out of ideas for now. Any thoughts or suggestions are more than welcome! Thanks for your time :) |
Same happens where. Totally random. Sometime it works sometimes it doesn't. When it fails if I use curl, it just works. |
Same here - getting ECONNREFUSED from a server that otherwise works (another app is able to connect to the same endpoint). A Postman developer should address this issue! Edit: SSL verification and proxies are disabled in my Postman settings. |
I had the same issue. And I found a solution:
# Mac OS X 12 (Sierra) and later:
sudo killall -HUP mDNSResponder
sudo killall mDNSResponderHelper
sudo dscacheutil -flushcache
|
It's true that running that fixes the issue, but I have to do it over and over :/ |
same issue here |
Having same issues when icall localdb |
Hi All, we have addressed it in v7.25.0 of the application, and now give better messages to help you debug the issue. Please verify the same and reach out to us if the issue persists. |
i was testing Nest JS ,APIs on postman and i had the same problem,but you either check the proxy settings on postman or start:dev |
I tried ipconfig / flushdns and helped me |
Because I use https not http, you can use http to resolve it
Pada tanggal Sen, 13 Jun 2022 16.19, bhawna ***@***.***>
menulis:
… Error: connect ECONNREFUSED 127.0.0.1:443 Found this, I've seen the
console, and......well some scratch, but its just the name for the host [image:
Screen Shot 2022-02-25 at 10 16 17]
<https://user-images.githubusercontent.com/70548701/155647668-7bd10ec9-a3d1-46f2-88b6-1f8a491899a2.png>
i am getting same error how did you resolve it
—
Reply to this email directly, view it on GitHub
<#6205 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQ2HZXN3KJW65I6DEGGCTJLVO34IZANCNFSM4HC5MRCA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Hi, 3 days ago everything worked fine. Now I am getting an error Could not get any response like the screenshots show. Here are the error and settings screenshots.


Any public url is not able to connect. Only localhost works. I reinstalled the Postman to latest version but nothing happened.
Thank you for any help.
The text was updated successfully, but these errors were encountered: