Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Grpc.Core.RpcException":"Grpc.Core.RpcException: Status(StatusCode="Cancelled", Detail="No grpc-status found on response.") #2492

Open
shuowpro opened this issue Jul 23, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@shuowpro
Copy link

shuowpro commented Jul 23, 2024

What version of gRPC and what language are you using?

Grpc.Net.Client: 2.55.0

What operating system (Linux, Windows,...) and version?

Microsoft Windows NT 10.0.20348.0

What runtime / compiler are you using (e.g. .NET Core SDK version dotnet --info)

Net 8.0.7

What did you do?

If possible, provide a recipe for reproducing the error. Try being specific and include code snippets if helpful.

What did you expect to see?

We should not have No grpc-status found on response error

What did you see instead?

We have the following error

Grpc.Core.RpcException":"Grpc.Core.RpcException: Status(StatusCode="Cancelled", Detail="No grpc-status found on response.")

This looks like to be a problem similar to #1164. but this problem seems to only happened on .net framework. But in our case, it is running on Net 8, which should not have this problem.

we are using the subdirectory handler as suggested here: https://learn.microsoft.com/en-us/aspnet/core/grpc/troubleshoot?view=aspnetcore-8.0#calling-grpc-services-hosted-in-a-sub-directory

@shuowpro shuowpro added the bug Something isn't working label Jul 23, 2024
@vladislav-prishchepa
Copy link

We had similar errors (same message) with .NET 8 + 2.62.0 (both client and server) in one of our production environments. The reason was header alt-svc h3=":433"; ma=86400 in first RPC response, with following upgrade to HTTP/3 which led to the channel's inoperability .

I'm not sure which infrastructure level was a problem (we use Cloudflare + k8s), but disabling HTTP/3 support for our gRPC domains in Cloudflare fixed it. I suppose configuring SocketsHttpHandler to use only HTTP/2 also can fix this case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants