I tried configuring crossbario to use TLS, but I could only connect web browser using Autobahnjs. With Node.js Autobahnjs is not connecting and I am getting ‘host unreachable’ error message.
I tried examples from here http://crossbar.io/docs/Secure-WebSocket-and-HTTPS/ except ‘Using commercial certificates’ because I wasn’t able to understand how to do that one.
Do you know any bullet proof easy way how to configure secure WebSocket?
torstai 3. syyskuuta 2015 1.22.04 UTC+3 Tobias Oberstein kirjoitti:
A common source of issues is some dumb firewall or proxy. You can (almost always) take those intermediaries out of the equation by using secure WebSocket (wss). The intermediaries will be sad, as they now no longer can look into and fuzz around with you traffic.
Am Mittwoch, 2. September 2015 12:30:23 UTC+2 schrieb Jarkko Peltonen:
The error was removed when I removed sending debug log lines from node.js to webbrowser using publish. Everything works fine now when I am not sending so much traffic to webbrowser. I have no problems receiving all the events in node.js log server but only using webbrowser.
sunnuntai 30. elokuuta 2015 14.16.06 UTC+3 Jarkko Peltonen kirjoitti:
I am getting the error in the subject in the IE 11 browser client using autobahn connection to crossbario and the backend is nodejs. This error appears quite frequently under heavy load and lots of traffic.
Is there a log in crossbario somewhere so I could check what happens when the WebSocket connection drops?