Does the browser trust your broker's self-signed cert? It looks like it doesn't...
Tim On Jun 28, 2017 12:08 PM, "itsebriy" <ihor.t...@gmail.com> wrote: > Hi All, > > I am trying to make secure web sockets to work with activeMQ and have > not > been able to do that yet. > > My mqttContext.xml looks as following : > > <broker id="broker" useShutdownHook="false" useJmx="false" > persistent="true" > > <transportConnectors> > <transportConnector name="vm" uri="vm://localhost"/> > <transportConnector name="mqtt+nio" > uri="mqtt+nio://0.0.0.0:1883"/> > <transportConnector name="ws" > uri="ws://0.0.0.0:1884?websocket.maxBinaryMessageSize=2147483647& > allowLinkStealing=true"/> > <transportConnector name="wss" > uri="wss://0.0.0.0:1885?websocket.maxBinaryMessageSize=2147483647& > allowLinkStealing=true"/> > </transportConnectors> > > <sslContext> > <sslContext keyStore="C:/Users/itsebriy/broker.ks" > keyStorePassword="password" > trustStore="C:/Users/itsebriy/client.ks" > trustStorePassword="password"/> > </sslContext> > > > I am using self signed certificates and in the browser I get following > error. > > mqttws31:977 WebSocket connection to 'wss://192.168.84.184:1885/' failed: > Error in connection establishment: net::ERR_INSECURE_RESPONSE > > Is there anything I could be doing wrong? > > Thanks, > Ihor > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/Cannot-setup-secure-web-sockets-with- > activemq-mqtt-tp4727995.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
