Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

GRPC name resolution problem

See original GitHub issue

Hello,

When trying to access GRPC that isn’t located in root (/) context it fails with error:

{
  "code": 14,
  "details": "Name resolution failed for target dns:host/ws",
  "metadata": {}
}

I’m trying to access method in /ws context. For example:

GRPC HOST/ws/com.some.pkg…

It resolves everyting until /com as host.

Issue Analytics

State:
Created 2 years ago
Comments:8 (5 by maintainers)

Top GitHub Comments

2reactions

AnWebercommented, Dec 20, 2021

@grpc/grpc-js is the successor of grpc. For grpc there is https://github.com/grpc/grpc/issues/14900, which mentions prefix of url. https://github.com/grpc/grpc/issues/14900#issuecomment-378071244:

The host used to create the channel does not go into the path used by gRPC (the channel builder arg should not include the “/foo” portion from your example). Instead, HTTP/2 paths are specified in a :path header field, and gRPC clients generate these from the proto service definition in the form protoPackage.serviceName.methodName (see here).

I also found the following issue: https://github.com/grpc/grpc-node/issues/980#issuecomment-517794622. grpc-js does not seem to support this feature.

I will extend httpyac so that the options can be set from outside (support channelFactoryOverride). And in addition, I will interpret the specification of the Path instead of to the server to the service

1reaction

AnWebercommented, Jan 10, 2022

It seems that grpc-js uses as default port 443 (used in line 83)

Thanks for the feedback:-)