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
@q7314568 - You can't have your app be both gRPC and http. You'll have to choose one or the other.
As for --dapr-grpc-port, that is the port that Dapr itself stands up on and that you will use to communicate with it. The issue here is that when you run dapr and your app together, the ports are given to the app via environment variables. When you start Dapr separately and don't give your app the ports, it'll fail to connect because it expects to find Dapr on its default ports.
@q7314568 - You can't have your app be both gRPC and http. You'll have to choose one or the other.
As for --dapr-grpc-port, that is the port that Dapr itself stands up on and that you will use to communicate with it. The issue here is that when you run dapr and your app together, the ports are given to the app via environment variables. When you start Dapr separately and don't give your app the ports, it'll fail to connect because it expects to find Dapr on its default ports.
Does this answer your question?
I endup found out i need to set endpoint for both of gRpc and http,and the proj can hit the web api again,thanks anyway
I started a demo with dap sdk,and trying to use docker-compose to debug locally.
everyting working fine with http,
but once i set "-dapr-grpc-port",all http action with daprClient starting to get error
compose cmd:
please help me figure out how to set both http & grpc up,and can both work in same service,thx
Here is my demo repo:
https://github.com/q7314568/DaprCounterASPNET
The text was updated successfully, but these errors were encountered: