Zed

> Yes, I'm sure. Let me show you another log with grpc 1.24.11. Their server is the same.

@murgatroid99 ``` I0301 15:21:21.185661000 4590949888 call.cc:626] OP[client_idle:0x1100e17f0]: SEND_INITIAL_METADATA{key=3a 70 61 74 68 ':path' value=2f 6a 64 79 5f 6c 6f 67 5f 71 75 65 72 79 2e 4a 64...

Sry, my bad. This is a clerical error, they are not real ip. In the log, I changed the real ip, they represent the same server.

In the last log, I cut out some lines because there are too many. And I found something interesting. This is the log with grpc-js 1.5.7 and Node 12.16.2, I...

Connect to the same adress dev.test.com:443 （Forwarding grpc requests using ingress） grpc 1.24.11 + Node 14.18.3 Success. grpc 1.24.11 + Node 12.16.2 Success. grpc-js 1.5.7 + Node 14.18.3 Error, client...

> You can ignore the IP and domain mentioned in the log. The domain name in the certificate is the same as the configuration in the code. I replaced the...

> I'm not 100% if it's the same thing, but this might be related to #2090. I've tested version 1.6.4 and it's the same problem, cry....

I guess the current situation is different because the TLS module of node version is different. grpc-js 1.5.7 + Node 14.18.3 Error, client hangs and no callback from server grpc-js...