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

failed to open grpc channel to app for ASP.NET Core gRPC service #1883

Closed
heavenwing opened this issue Aug 10, 2020 · 3 comments · Fixed by #2254
Closed

failed to open grpc channel to app for ASP.NET Core gRPC service #1883

heavenwing opened this issue Aug 10, 2020 · 3 comments · Fixed by #2254

Comments

@heavenwing
Copy link

heavenwing commented Aug 10, 2020

In what area(s)?

/area runtime

/area operator
/area placement
/area docs
/area test-and-release

What version of Dapr?

version 0.9.0 commit 6babe85-dirty

Expected Behavior

Dapr runtime should connect app which be developed by ASP.NET Core gRPC service

Actual Behavior

Got error: level=warning msg="failed to open grpc channel to app: error establishing connection to app grpc on port 5001: context deadline exceeded"

And client report "app channel is not initialized"

Steps to Reproduce the Problem

I added a grpc sample into dotnet-sdk in here (https://github.com/heavenwing/dapr-dotnet-sdk/tree/grpcsample)

My sample project is "GrpcServiceSample" which use ASP.NET Core gRPC service to host grpc server.

The GrpcClient can connect this grpc sample (run with "dotnet run"), and invoke method.

But when I run GrpcServiceSample in Dapr with this command "dapr run --app-id grpcsample --app-port 5001 --protocol grpc -- dotnet run", I got above error.

And I modified DaprClient to invoke my grpc sample, it also reports error when run in Dapr with this command "dapr run --app-id client -- dotnet run"

whole log info in this log file
dapr grpc sample.log

Release Note

RELEASE NOTE: Added ability for Dapr to use a non-secure SSL connection when communicating with the app

@heavenwing heavenwing added the kind/bug Something isn't working label Aug 10, 2020
@yaron2
Copy link
Member

yaron2 commented Aug 18, 2020

Thanks for reporting this.

Can you please try to set up a non TLS endpoint for port 5000 as outlined here?

https://auth0.com/blog/implementing-microservices-grpc-dotnet-core-3/

Then try and run Dapr with app-port 5000.

@heavenwing
Copy link
Author

@yaron2
After disable TLS for grpc server, and run it with "dapr run --app-id grpcsample --app-port 5000 --protocol grpc -- dotnet run", it's working.
See my latest commit: heavenwing/dapr-dotnet-sdk@50809c4

But I think that it is still a bug because of unsupporting TLS.

@msfussell msfussell added the P1 label Oct 9, 2020
@msfussell
Copy link
Member

Enable Dapr to be able to call applications that have https endpoint

@msfussell msfussell added this to To do in 1.0.0 Milestone 1 via automation Oct 9, 2020
@msfussell msfussell added this to To do in 1.0.0-RC1 Milestone features via automation Oct 9, 2020
@msfussell msfussell added the size/XS 2 days work label Oct 9, 2020
@artursouza artursouza added kind/feature New feature request and removed kind/bug Something isn't working labels Oct 13, 2020
1.0.0 Milestone 1 automation moved this from To do to Review Oct 15, 2020
1.0.0-RC1 Milestone features automation moved this from To do to Review Oct 15, 2020
@artursouza artursouza moved this from Review to Done in 1.0.0-RC1 Milestone features Oct 15, 2020
@artursouza artursouza moved this from Review to Done in 1.0.0 Milestone 1 Oct 15, 2020
@artursouza artursouza added this to Release in 1.0.0 Milestone Oct 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature request P1 size/XS 2 days work
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

4 participants