postman-app-support icon indicating copy to clipboard operation
postman-app-support copied to clipboard

Published 20 hours ago • verified publisher icon postmanlabs

WSL2 `ECONNREFUSED` on GraphQL Request

Open kliakos opened this issue 2 years ago • 5 comments

Is there an existing issue for this?

  • [X] I have searched the tracker for existing similar issues and I know that duplicates will be closed

Describe the Issue

While schema fetch and queries work fine with standard HTTP request and Body=GraphQL, the same doesn't work with the new GraphQL Request request type. The localhost domain should resolve to the WSL ip but it doesn't. Strangely, sometimes it works but can't reproduce it on a steady base.

Working:

image

Not working:

image

Steps To Reproduce

  1. Open a new GraphQL Request
  2. Add a GraphQL URL backed by a service running on WSL2
  3. Try to get schema from introspection

Screenshots or Videos

No response

Operating System

Windows 10

Postman Version

10.12.4

Postman Platform

Postman App

User Account Type

Signed In User

Additional Context?

No response

kliakos avatar Mar 21 '23 12:03 kliakos

@kliakos Thanks for reporting this issue.

Strangely, sometimes it works but can't reproduce it on a steady base.

🤔 That's weird since both use the same request-sending library.

codenirvana avatar Mar 21 '23 13:03 codenirvana

@kliakos Thanks for reporting this issue.

Strangely, sometimes it works but can't reproduce it on a steady base.

🤔 That's weird since both use the same request-sending library.

The case that I have seen it to work is when I first do the schema fetch from the standard HTTP request tab, and then I try the same (get schema from instrospection) from the GraphQL Request tab. Seems like some kind of dns caching happens which is persisted for some time, but it doesn't last long. But this "trick" doesn't work all the time.

The temp workaround is to use the WSL ip directly instead of localhost, but of course I would expect this issue to be addressed at some time soon.

kliakos avatar Mar 21 '23 13:03 kliakos

This seems to also affect Websocket Request. The WSL IP address workaround seems to work as well.

douglaswth avatar Apr 26 '23 20:04 douglaswth

related to #11204

akshaysangma avatar Sep 25 '23 19:09 akshaysangma

related to #11204

to save others time here is the simplest solution that fixes this in the other issue: replace local host with wsl IP retrieved from wsl hostname -I

credit: https://github.com/postmanlabs/postman-app-support/issues/11204#issuecomment-1751987249

ColeStansbury avatar Sep 10 '24 20:09 ColeStansbury

Guys, this has worked for me:

  • Type ifconfig in your WSL terminal
  • Grab the eth0 IP and replace it in your postman url, ex: http://192.168.212.235:3000/graphql

No more errors, the schema will be fetched as expected.

Dezainer avatar Sep 27 '24 18:09 Dezainer