Can any ory support staff help me out with some lo...
# ory-network
c
Can any ory support staff help me out with some logs please? I'm getting a
13 INTERNAL: Received RST_STREAM with code 0
when making calls to Keto (in ory Network) from node (over grpc, hence the non-http error code), and I would really like to know why 🙂
f
Is this a regression?
@narrow-van-43826 any ideas?
c
Not a regression I don't think, however it only happens to the node client, not the go one, so I suspect client misbehaviour, just not sure of what nature
f
a quick web search tells me it might be auth related
c
Ooh, alright
n
For authentication to work over gRPC you need to set the "authorization" metadata to the API key.
c
Yeah, I've done it in go, unfortunately I didn't write the node client, but I'll double check it's done correctly asap! Thanks! I'll get back to you if I get stuck
You were of course entirely right. Someone™ ripped out the original implementation and replaced it with one that doesen't auth. Thanks for your help and sorry about hogging your time ❤️
f
👍 glad to hear it works
c
So the actual culprit here, after a bit more debugging, was a 404. Not your fault, one of our devs had renamed the grpc service in the proto-file, so it didn't match the one actually served by ory network. Took a while to figure out, but in case you hear of a similar error again, it might be nice to know! So the typescript grpc client will actually fail with a conn reset rather than a "not found" error if the service (or maybe even method) does not exist on the server side 🙂. Good to know, right?