I moved on using CA certs. My original problem ended up being a firewall
issue that I resolved by opening up the ports I needed on the server.
Thanks for the suggestions!
--
View this message in context:
http://activemq.2283324.n4.nabble.com/STOMP-over-secure-websocket-tp4701435p4701998.html
Have you made config changes to allow the broker to trust your self-signed
cert?
On Aug 27, 2015 1:17 PM, "ArturoBelano" wrote:
> I tried to connect using the openssl client and got:
> connect: Connection refused
> connect:errno=61
> That doesn't narrow the issue down too much for me though. I'm
I tried to connect using the openssl client and got:
connect: Connection refused
connect:errno=61
That doesn't narrow the issue down too much for me though. I'm using a
self-signed cert with the ssl connection. Any ideas?
--
View this message in context:
http://activemq.2283324.n4.nabble.com
I still get a connection refused notice. Is there a good way to debug wss
connections? Maybe openssl?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/STOMP-over-secure-websocket-tp4701435p4701457.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
I just accidently removed the ending quote when I posted. Sorry about that.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/STOMP-over-secure-websocket-tp4701435p4701456.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Your config snippet is also missing a closing quote on the wss URI; is that
just an artifact of posting your question?
On Aug 27, 2015 6:02 AM, "Christopher Shannon" <
christopher.l.shan...@gmail.com> wrote:
> You should just use wss://myurl:61616 for your URL. I don't believe you
> need the stom
You should just use wss://myurl:61616 for your URL. I don't believe you
need the stomp+wss at the end.
On Wed, Aug 26, 2015 at 9:01 PM, ArturoBelano
wrote:
> I configured and restarted activemq according to the documentation to allow
> ssl, wss and stomp+ssl (abbrevated here just to show you wh
