Weird error calling my grpc server "Stream removed" #138
Comments
I found a workaround at stack overflow. Basically, don't use https. Update your launchSettings.json file and change the applicationUrl property.
Then use port 5000 with BloomRPC |
Thanks @sumpubu !! |
To get the workaround mentioned above to work in my application I had to restrict the protocols on the endpoint to Http2 only:
I'm still in proof of concept with my project so I don't know what other ramifications this may have (like if I host a standard webapi in the same project?). Having to do this just to get BloomRPC to work seems less than desirable. I am able to call the endpoint just fine from other clients without making the configuration change above. See below code example:
Any idea why I have to make this adjustment to use BloomRPC but not use HttpClient? |
It's perfect working with 0.0.0.0:5000. |
I'm not sure if @uditsing's reply was to the original post or mine (seems to be toward the original). My question above still stands. I'm trying to find out why the setting I mention seems to be necessary to work with BloomRPC when it is not needed using the code I posted above. Anyone have any insight here? Should I open a separate issue for this? |
@JarrodJ83 The side effect is that gRPC-Web won't work that way. The only way I've been able to get bloomrpc to work on windows is by manually importing the kestrel development certificate into it because it apparently won't use the system certificate store to get it. |
I created new server grpc:
dotnet new grpc -o GrpcGreeterServer
ather
dotnet run
after invoke BloomRPC
And i received:
dotnet --info
The text was updated successfully, but these errors were encountered: