Re: [grpc-io] Re: Getting "all SubConns are in TransientFailure" sending to local grpc service.

Hi Josh, Thanks a lot for your help. Yes, the custom dialer helped to understand the actual error message (in my case the certificate is valid for the "hostname", but the client is using "localhost" to connect to the server). After changing it, things started to work. thanks. On Friday,

Re: [grpc-io] Re: Getting "all SubConns are in TransientFailure" sending to local grpc service.

Hi, Ravi, Yes, I understand. That is because grpc.Dial doesn't actually return an error just because there are issues establishing socket connections -- it asynchronously starts a client that will transparently retry dialing as needed (possibly continuously dialing, with some backoff, depending on

Re: [grpc-io] Re: Getting "all SubConns are in TransientFailure" sending to local grpc service.

Hi Josh, Thanks for sharing your thoughts. In my case, grpc.Dial is successful, there is no error for this call. The error occurs when the rpc call is invoked. On Fri, Dec 22, 2017 at 3:42 PM, Josh Humphries wrote: > If you use a custom dialer, specify the "insecure"

Re: [grpc-io] Re: Getting "all SubConns are in TransientFailure" sending to local grpc service.

If you use a custom dialer, specify the "insecure" dial option in the GRPC client, but then handle TLS in your custom dialer, you can get at the actual error messages that are causing the transport failure. Here's an example I used in a command-line tool, where I wanted to be able to show users a

Re: [grpc-io] Re: Getting "all SubConns are in TransientFailure" sending to local grpc service.

Hi Yufeng, My server side code exactly like yours. My certificates and keys are fine, because when I plug them into example route_guide code (grpc-go/examples/route_guide) they work. My server-client logic is also fine without certificates. The moment I enable certificates, I get this error:

Re: [grpc-io] Re: Getting "all SubConns are in TransientFailure" sending to local grpc service.

Hi Ravijo, I have fixed the issue, I just change the service code below. The cert is bought normal cert from “https://www.rapidssl.com/“. certificate, err := credentials.NewServerTLSFromFile(conf.CRT, conf.KEY) if err != nil { log.Errorf("could not load server key pair: %s", err)

[grpc-io] Re: Getting "all SubConns are in TransientFailure" sending to local grpc service.

How to fix / debug such issue? I keep getting this error: rpc error: code = Unavailable desc = all SubConns are in TransientFailure The same client - server logic works fine if I remove the TLS credentials ... any help to resolve would be appreciated! On Monday, December 4, 2017 at 5:44:41 AM

[grpc-io] Re: Getting "all SubConns are in TransientFailure" sending to local grpc service.

Hi Paul, can i ask did you have solved the issue. i have the same problem.. On Tuesday, November 14, 2017 at 5:36:19 AM UTC+8, Paul Breslin wrote: > > > I'm running local grpc services under Docker for Mac. All has been fine > but today I started getting intermittent failures: > rpc error: code