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

Issue Description


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:closed
  • Created a year ago
  • Comments:8 (5 by maintainers)

github_iconTop GitHub Comments

AnWebercommented, Dec 20, 2021

@grpc/grpc-js is the successor of grpc. For grpc there is, which mentions prefix of url.

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: 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

AnWebercommented, Jan 10, 2022

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

Thanks for the feedback:-)

Read more comments on GitHub >

github_iconTop Results From Across the Web

python - grpc client dns resolution failed when trying to access ...
When running against localhost:5001 it works fine, but running against the actual IP of the machine from within the same network like 192.168....
Read more >
[gRPC] DNS resolution failed for service · Issue #1871 - GitHub
GRPC will report DNS resolution failed when with telepresence connect ed on macos. The error message is listed below: File "/Users/foo/bar/venv/ ...
Read more >
GRPC Core: gRPC Name Resolution
A fully qualified, self contained name used for gRPC channel construction uses URI syntax as defined in RFC 3986. The URI scheme indicates...
Read more >
It's Always DNS . . . Except When It's Not: A Deep Dive ...
If a connection is lost, the gRPC client will resolve the service's DNS name to re-establish a connection. It will continue to re-resolve...
Read more >
gRPC Name Resolution
gRPC Name Resolution. Overview. gRPC supports DNS as the default name-system. A number of alternative name-systems are used in various deployments.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found