[grpc-io] Re: SSL connection failure(status:12, empty err message returned)

2018-09-19 Thread solomon lifshits
The problem is solved. The issue was because of overloaded target name mismatch with the rpc method authority. Thanks! On Wednesday, September 19, 2018 at 1:40:55 PM UTC-4, Yang Gao wrote: > > is your client and server using the same proto? Can you collect the client > side trace as well? From t

[grpc-io] Re: SSL connection failure(status:12, empty err message returned)

2018-09-19 Thread 'Yang Gao' via grpc.io
is your client and server using the same proto? Can you collect the client side trace as well? From the server log it does not seem like using ssl is related. On Thursday, September 13, 2018 at 5:44:22 PM UTC-7, solomon lifshits wrote: > > Thank you for reply! > No, the error message is empty.

[grpc-io] Re: SSL connection failure(status:12, empty err message returned)

2018-09-13 Thread solomon lifshits
Thank you for reply! No, the error message is empty. I patched the grpc code and put unique error messages in all the places where UNIMPLEMENTED status was returned. What I figured out is that it was a completion tag of type UnimplementedAsyncRequest that is placed on server cq( src/cpp/server/

[grpc-io] Re: SSL connection failure(status:12, empty err message returned)

2018-09-13 Thread 'Carl Mastrangelo' via grpc.io
Is there an error message provided with Unimplemented? Usually that error code is for calling a method that the server doesn't know about. On Thursday, September 13, 2018 at 11:02:34 AM UTC-7, solomon lifshits wrote: > > Unable to connect to grpc server using SSL credentials, while connection