[rabbitmq-discuss] Issues with RabbitMQ, SSL and .NET

Mon Sep 12 11:18:53 BST 2011

> =ERROR REPORT==== 9-Sep-2011::16:12:49 ===
> error on TCP connection <0.605.0>:{ssl_upgrade_error,timeout}

I've looked into this and, as far as I can tell, the only way to get
that error is if the client connects successfully, but takes too long to
complete the SSL handshake.

Just to confirm, you've tried to connect the .NET client to an s_server
running on the same machine as the broker and it worked?

Cheers,
Alex

On Fri, Sep 09, 2011 at 03:22:43PM +0200, umut.sahin at vigasis.com wrote:
> >We haven't had any reported issues with that configuration, so it
> >should probably work.  Is there anything in the broker logs about this?
> 
> =INFO REPORT==== 9-Sep-2011::16:12:44 ===
> accepted TCP connection on [::]:5671 from 10.35.110.131:4712
> 
> =INFO REPORT==== 9-Sep-2011::16:12:44 ===
> starting TCP connection <0.605.0> from 10.35.110.131:4712
> 
> =ERROR REPORT==== 9-Sep-2011::16:12:49 ===
> error on TCP connection <0.605.0>:{ssl_upgrade_error,timeout}
> 
> =INFO REPORT==== 9-Sep-2011::16:12:49 ===
> closing TCP connection <0.605.0>
> 
> Broker logs are above...
> 
> 
> >
> >> endpoint=amqp-0-9://10.35.110.167:5671, attempts=1
> >> System.IO.IOException: Uzak taraf tama akn kapattndan
> >> kimlik dorulamas
> >
> >I don't suppose you could get an English version of the error, could
> >you?  The Google Translation doesn't sound familiar.
> 
> "Authentication failed as remote party has closed the transport stream" is the translation
> 
> >
> >Also, 1) is the CA's certificate in the Trusted Root Certificate
> >Authorities store? 2) does the server's hostname match the common name
> >on the certificate?
> >
> 
> 1) Yes, it is
> 2) Yes it does match CN=hostname O=server (like http://www.rabbitmq.com/ssl.html examples..)
> 
> Thnx in advance,
> Umut
> 