I’m not using this package, I copied the code, updated it, and made it into its own module in my NestJS server. But the principles are basically the same. I’m using the latest dgraph-js package, for example.
It looks like I’m connecting to the GRPC endpoint just fine (the one you access through the settings page on Dgraph Cloud, ending in 443). I’m kind of a noob with this stuff so I’m just using “createInsecure()” for the credentials, with no options. Everything about the client setup looks like its working, but when I try to fire off a query I get this:
[Nest] 12580 - 07/25/2021, 6:18:15 PM ERROR [ExceptionsHandler] 13 INTERNAL: Received RST_STREAM with code 2 triggered by internal client error: Protocol error Error: 13 INTERNAL: Received RST_STREAM with code 2 triggered by internal client error: Protocol error
There must be something obvious I’m missing here. The reason I’m doing this is because I’m running an angular app that’s being rendered server-side through a NestJS server, which I also plan to use to generate JWTs and their claims, and get that all working with Dgraph Cloud. Having GRPC would just make the performance that much better.
(put “x” in the box to select)