This post has NOT been accepted by the mailing list yet.
I'm trying to get webstomp working with the latest RabbitMQ 3.3.1 and a self signed certificate, but I keep on getting SSL errors when I point my browser to <a href="https://$myserver:$port/stomp">https://$myserver:$port/stomp
In Firefox 29 this is what I get:
The key does not support the requested operation. (Error code: sec_error_invalid_key)
In Chrome the message is different but I'm quite sure it's due to the same error:
Error code: ERR_SSL_CLIENT_AUTH_SIGNATURE_FAILED
However, in IE9 and IE11 I successfully get the "Welcome to SockJS!" message.
Here are some more details of the issue you described; as you mentioned firefox and chrome report an SSL error. If you set security.tls.version.max to 0 in firefox you should be able to connect (this setting means configure SSL 3.0 and disable TLS). It looks like WebStomp insists on using the old vulnerable SSL 3.0 protocol perhaps?