Issue after update to 2.52.0
See original GitHub issueDear Since the upgrade I’m getting the following error : System.InvalidOperationException: ‘Channel is configured with an HTTP transport doesn’t support client-side load balancing or connectivity state tracking. The underlying HTTP transport must be a SocketsHttpHandler with no SocketsHttpHandler.ConnectCallback configured. The HTTP transport must be configured on the channel using GrpcChannelOptions.HttpHandler.’
My service is hosted in IIS using gRPC.Web with client load balancing. All was working fine before the update. Here is my client code:
var credentials = CallCredentials.FromInterceptor((c, m) =>
{
m.Add("Authorization", "Bearer " + ...;
return Task.CompletedTask;
});
var clientHandler = new SocketsHttpHandler();
clientHandler.UseProxy = false;
clientHandler.EnableMultipleHttp2Connections = false;
clientHandler.SslOptions = new SslClientAuthenticationOptions
{
RemoteCertificateValidationCallback = ValidateServerCertificate,
};
var channel = GrpcChannel.ForAddress("dns:///...", new GrpcChannelOptions
{
HttpHandler = new GrpcWebHandler(new SubdirectoryHandler(clientHandler, "/...")),
Credentials = ChannelCredentials.Create(ChannelCredentials.SecureSsl, credentials),
//UnsafeUseInsecureChannelCallCredentials = true,
ServiceConfig = new ServiceConfig
{
LoadBalancingConfigs = { new RoundRobinConfig() }
}
});
Issue Analytics
- State:
- Created 6 months ago
- Reactions:1
- Comments:12 (5 by maintainers)
Top Results From Across the Web
Ledger Live version 2.52.0 update : r/ledgerwallet
Hi , I am getting notification of "Update to Live version 2.52.0 is available " in Ledger live application . if new version...
Read more >Ledger Support
The issue has been fixed! 🛠️ Make sure to update Ledger Live to version 2.52.0 https://ledger.com/ledger-live and clear cache ...
Read more >Updating to 2.52.0 and missing memory temperature ...
Updated to 2.52 from 2.49 or 2.50 and the memory temperature for the gpu is gone. Only gpu (die) and hotspot are visible....
Read more >Error when Upgrading 2.46.0 > 2.52.0 (2.51.0 also testet)
Hello, i get following error after Update when i open the Main Web Page. · 2023-04-22 09:37:59,811+0200 ERROR [qtp1442426568-94] *SYSTEM org.
Read more >What's new in Ledger Live
We've fixed the issue, and you'll now see a warning message if your account doesn't have enough energy to cover the transaction. Ledger...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
2.53.0 will revert back to 2.51.0 behavior. Now a log message is written if a proxy is detected.
Use 2.51.0 until it’s available.
Well adding below to IsProxied line 299 in GrpcChannel.cs fixes the immediate issue.
if (!socketsHttpHandler.UseProxy) { return false; }
On the proxy side are you saying it can’t work if a proxy is present? But there is no reason it can’t work (obviously will have a performance impact) but it will still load balance on the target group of servers?