Remote schema error when used for local dev - document that remote schema URLs should use docker host based URLs esp for local dev

Hi guys, I wanted to try the remote schema feature but it seems that it doesnt work for local development. First I thought it was an issue with my graphql server written in golang but then I tried with your nodejs boilerplate. When I add a remote schema in the UI I get this error back :

HttpExceptionRequest Request { host = "localhost" port = 4000 secure = False requestHeaders = [("Content-Type","application/json"),("User-Agent","hasura-graphql-engine/v1.0.0-alpha38")] path = "/graphql" queryString = "" method = "POST" proxy = Nothing rawBody = False redirectCount = 10 responseTimeout = ResponseTimeoutDefault requestVersion = HTTP/1.1 } (ConnectionFailure Network.Socket.connect: <socket: 13>: does not exist (Connection refused))

even though I can do an introspection query … I tried with path “/graphql?” too and with 0.0.0.0 instead of localhost but without success. I guess that hasura remote schema only accepts https. Would it possible to add support for http too for (development purpose)? Is there a workaround that doesn’t involve deploy my app? Thank’s for the great work guys

[coco98]

@Sach97 This seems like the docker container not being able to connect to the server running on localhost. Can you try using host.docker.internal if you’re on a mac or the docker host IP basically?

That should work!

[tirumaraiselvan]

We should also document it in the README here: https://github.com/hasura/graphql-engine/tree/master/install-manifests/docker-compose