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
Remote schema, forward headers issue #6847
Comments
I have similar issue:
It also connected to It worked as designed before, but now I get this exception.. reinit of remote schema does not help. 2.0.0-alpha.9 |
Would you be able to construct a small repro of the issue so we can take a look at debugging what the cause of your problem is? |
@martin-hasura How would I go about doing that? (Basically, I don't know what to do/where to start) |
In my case I figured out
It occurs when I add Auth plugin in Kong to secure Hasura. When I disabled security to Hasura it worked. But anyway - error message is not helpful. And debug level logs are also empty @martin-hasura can you advise best practice in my case, if I want to secure Hasura? |
Labeling this as a bug so that we can improve logging to capture these scenarios better. |
Hasura 2.0.0-alpha.9
If I select
Forward all headers from client
when setting up remote schemathen if I try to run any query in the console the end result is
and no requests goes through to the remote.
The text was updated successfully, but these errors were encountered: