You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a nodejs backend grpc-server (condor) that is up and running, but it seems the grpc-gateway is unable to establish connection to the backend(s). There are no information whatsoever about what goes wrong.
You can look at the configurations etc, but it would be sufficient if I can get some help making the gateway server more verbose for debugging as I have very limited go-experience.
PS
I've forked docker-grpc-gateway to make it useable in our workflow. There may be some obvious mistakes made by the config-generator script, but as far as I can see the config file generated is ok. Also manually creating the config files makes no difference.
Hi. There are some issues with the script that I haven't had time to work into,... not sure if they are related to the problem you are having. Just quickly looking, I would say that verify that you can connect to the backend from a regular client directly, for instance, I see you are connecting to 5100 port, while the default GRPC port is 50051. (If you are using that port is ok, I just want to make sure that it's not just a typo)....
Sorry not to provide more help now. I expect to have 2 busy months, but after that I expect to get some free time to work on improving the script. Thanks!
I have a nodejs backend grpc-server (condor) that is up and running, but it seems the grpc-gateway is unable to establish connection to the backend(s). There are no information whatsoever about what goes wrong.
You can look at the configurations etc, but it would be sufficient if I can get some help making the gateway server more verbose for debugging as I have very limited go-experience.
PS
I've forked docker-grpc-gateway to make it useable in our workflow. There may be some obvious mistakes made by the config-generator script, but as far as I can see the config file generated is ok. Also manually creating the config files makes no difference.
config generated / used
protofile:
protos/info/informer.proto
The text was updated successfully, but these errors were encountered: