-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
console errors #10286
Comments
I'm getting the same error. I've tried it with and without |
The problem was it couldn't connect to the DB mentioned in the metadata. Very bizarre errors from Hasura though in this case. |
Getting the same error, can connect to db. v hasura/graphql-engine:v2.40.2.cli-migrations-v3 |
I've been seeing similar problems running I think there are at least two problems. I'm noticing that the I've noticed that the Font Awesome CSS is NOT zipped but simply minified. (See: It should be noted that I'm running a pretty custom CLI command too: echo "version: 3" > config.yaml
hasura-cli console \
--no-browser \
--address ${CONSOLE_DOMAIN} \
--api-port 80 \
--api-host http://${CONSOLE_DOMAIN} \
--console-port 9695 \
--endpoint http://hasura:8080 \
--static-dir /srv/console-assets \
--console-hge-endpoint http://${CONSOLE_DOMAIN} With Caddy proxying everything through port 80 :80 {
root /usr/share/caddy
encode gzip
file_server
route /console* {
reverse_proxy hasura:9695
}
route /console/assets/* {
reverse_proxy hasura:8080
}
route /v1/version {
reverse_proxy hasura:8080
}
route /v1/graphql {
reverse_proxy hasura:8080
}
route /v1/metadata {
reverse_proxy hasura:8080
}
route /v1/* {
rewrite /v1/* /api/rest/*
reverse_proxy hasura:8080
}
route /v1alpha1/config {
reverse_proxy hasura:8080
}
route /v2/query {
reverse_proxy hasura:8080
}
route /api/* {
reverse_proxy hasura:8080
}
route /apis/migrate* {
reverse_proxy hasura:9695
}
} I should also note that if I try to sever the assets over 9695 it just gives me the Console homepage no matter what URL. So that looks like yet another bug. Ultimately this configuration is usable but with a few silent scripting errors in the console. |
gql.assist.si-1718097838971.log
https://v1/graphql
i have problem with hasura console api, slow behaviour
The text was updated successfully, but these errors were encountered: