You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Server Version:
CLI Version (for CLI related issue): 2.37.0
Environment
OSS Docker image
What is the current behaviour?
I am running Hasura in a Docker compose stack running as a local dev environment. The command line is hasura-cli console --address 0.0.0.0 --no-browser --console-hge-endpoint http://local.somedomain.io/.
I can access and use the console on http://localhost:9695/console just fine. However, looking at the network inspector, there are multiple failing requests to bogus endpoint http://v1/graphql.
What is the expected behaviour?
These failing requests should succeed, using --console-hge-endpoint as the base URL.
How to reproduce the issue?
The HGE endpoint goes through an Nginx container which routes to HGE. The nginx config:
#!/bin/bash
function wait_for_port () {
local PORT=$1
echo Waiting for port $PORT
while ! nc -z localhost $PORT; do
sleep 0.1
done
echo Port $PORT is listening
}
graphql-engine serve &
wait_for_port 8080
cd /
hasura-cli console --address 0.0.0.0 --no-browser --console-hge-endpoint http://local.somedomain.io/
wait
Screenshots or Screencast
See above
Please provide any traces or logs that could help here.
N/A
Any possible solutions/workarounds you're aware of?
None I'm aware of
Keywords
The text was updated successfully, but these errors were encountered:
Version Information
Server Version:
CLI Version (for CLI related issue): 2.37.0
Environment
OSS Docker image
What is the current behaviour?
I am running Hasura in a Docker compose stack running as a local dev environment. The command line is
hasura-cli console --address 0.0.0.0 --no-browser --console-hge-endpoint http://local.somedomain.io/
.I can access and use the console on
http://localhost:9695/console
just fine. However, looking at the network inspector, there are multiple failing requests to bogus endpointhttp://v1/graphql
.What is the expected behaviour?
These failing requests should succeed, using
--console-hge-endpoint
as the base URL.How to reproduce the issue?
The HGE endpoint goes through an Nginx container which routes to HGE. The nginx config:
The compose services are:
hasura-finish-startup.sh:
Screenshots or Screencast
See above
Please provide any traces or logs that could help here.
N/A
Any possible solutions/workarounds you're aware of?
None I'm aware of
Keywords
The text was updated successfully, but these errors were encountered: