On Thu, 2015-03-12 at 09:55 +0000, Chris Richardson wrote: > Not sure if this will turn out to be helpful or spam but I've previously > encountered this error message and added the following to our kb: > > This is related to an invalid SSL certificate and has been observed in a > situation where the address used to contact the server did not match that > of its certificate, eg: using "localhost" instead of > "localhost.localdomain" or using a DNS alias which does not exist in the > certificate. Depending on the client, the error may be accompanied by a > message on the client such as "[Security] warning Connect failed: Failed: > Unable to communicate securely with peer: requested domain name does not > match the server's certificate. [-12276] "
This is one of the possible causes - the problem is more general than this though, as Pavel's simple reproducer shows (essentially interrupting a client using SSL causing a client side disconnect will give you this message). Andrew --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
