Replies: 1 comment 1 reply
-
Have you checked the network request that is being sent when using urql or apollo client? The invalid response could be due to the Authorization token being an empty string. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm getting this webhook error when I'm trying to connect from a urql client to hasura server which doesn't give me much information to go on. Any idea what might be causing this error?
(when using apollo client I get the same error)
error log hasura server
The webhook is working fine when I test with Postman or ThunderClient and is returning exactly what I'd expect
URQL CLIENT CONFIG (urql.js)
CLIENT CALL
The webhook is running in a node server on the same (host) server location (linux) as the hasura server (which runs in docker)
The node server uses npm package cors with default setting
app.use(cors())
Maybe the AUTH_HOOK is not correct? I believe you should use 172.17.0.1 in order to communicate from docker to host machine?
($ ip addr show docker0 will give me 172.17.0.1)
HASURA SERVER SETTINGS
Beta Was this translation helpful? Give feedback.
All reactions