Node tls/ssl issue on ubuntu

#1

Hi,
Everything used to work fine until I enabled TLS. Now it does not and have spent several days trying to get this to work. About ready to give up and replace crossbar with something home grown based on socket.io.

  • I am using a Comodo purchased certificate.

  • Running version 0.11.1 crossbar.io installed from source on ubuntu 14.04.

  • My node.js process fails to connect to the crossbar.io router.

  • If my node process runs on a separate Windows 10 machine then I can connect ok. Go figure. Same code.

  • I have enabled autobahn.js debug.

  • I have enabled “global.debug = true” in the node code so I can see some debug action. e.g. output:

trying to create WAMP transport of type: websocket

using WAMP transport type: websocket

onclose unreachable

retrying in 1.5100164652561976 s

trying to create WAMP transport of type: websocket

using WAMP transport type: websocket

onclose unreachable

retrying in 2.2707157162414875 s

It just keeps retrying and failing

Any suggestions?

0 Likes

#2

http://www.pynut.com/?p=105

OpenSSL on Ubuntu gotcha and fix for Crossbar with GoDaddy[Any] Certs

···

On Monday, September 21, 2015 at 1:11:54 AM UTC-4, Craig Broadbear wrote:

Hi,
Everything used to work fine until I enabled TLS. Now it does not and have spent several days trying to get this to work. About ready to give up and replace crossbar with something home grown based on socket.io.

  • I am using a Comodo purchased certificate.
  • Running version 0.11.1 crossbar.io installed from source on ubuntu 14.04.
  • My node.js process fails to connect to the crossbar.io router.
  • If my node process runs on a separate Windows 10 machine then I can connect ok. Go figure. Same code.
  • I have enabled autobahn.js debug.
  • I have enabled “global.debug = true” in the node code so I can see some debug action. e.g. output:

trying to create WAMP transport of type: websocket

using WAMP transport type: websocket

onclose unreachable

retrying in 1.5100164652561976 s

trying to create WAMP transport of type: websocket

using WAMP transport type: websocket

onclose unreachable

retrying in 2.2707157162414875 s

It just keeps retrying and failing

Any suggestions?

0 Likes

#3

Thanks for the tip, but I am already doing that. Also, the code works on Windows, talking to crossbar running on ubuntu. Its the ubuntu to ubuntu I am having issues with.

0 Likes

#4

As a workaround, I ended up running a non tls transport for processes on the same machine. This seems to work. So its TLS with the outside world and unsecured locally, which is fine.

···

On Monday, September 21, 2015 at 3:11:54 PM UTC+10, Craig Broadbear wrote:

Hi,
Everything used to work fine until I enabled TLS. Now it does not and have spent several days trying to get this to work. About ready to give up and replace crossbar with something home grown based on socket.io.

  • I am using a Comodo purchased certificate.
  • Running version 0.11.1 crossbar.io installed from source on ubuntu 14.04.
  • My node.js process fails to connect to the crossbar.io router.
  • If my node process runs on a separate Windows 10 machine then I can connect ok. Go figure. Same code.
  • I have enabled autobahn.js debug.
  • I have enabled “global.debug = true” in the node code so I can see some debug action. e.g. output:

trying to create WAMP transport of type: websocket

using WAMP transport type: websocket

onclose unreachable

retrying in 1.5100164652561976 s

trying to create WAMP transport of type: websocket

using WAMP transport type: websocket

onclose unreachable

retrying in 2.2707157162414875 s

It just keeps retrying and failing

Any suggestions?

0 Likes

#5

I’ve been using nginx as a reverse proxy that unwraps the https as it sends it off to the wamp router. There is a way to set it up to play nice with the websockets connection upgrade style. With this setup, optionally I can reuse sessions here with other services but I am not that bold.

It’s probably not worth the effort for python to be calling the ssl libs unless absolutely necessary?

···

On Monday, September 21, 2015 at 3:17:24 PM UTC-7, Craig Broadbear wrote:

As a workaround, I ended up running a non tls transport for processes on the same machine. This seems to work. So its TLS with the outside world and unsecured locally, which is fine.

On Monday, September 21, 2015 at 3:11:54 PM UTC+10, Craig Broadbear wrote:

Hi,
Everything used to work fine until I enabled TLS. Now it does not and have spent several days trying to get this to work. About ready to give up and replace crossbar with something home grown based on socket.io.

  • I am using a Comodo purchased certificate.
  • Running version 0.11.1 crossbar.io installed from source on ubuntu 14.04.
  • My node.js process fails to connect to the crossbar.io router.
  • If my node process runs on a separate Windows 10 machine then I can connect ok. Go figure. Same code.
  • I have enabled autobahn.js debug.
  • I have enabled “global.debug = true” in the node code so I can see some debug action. e.g. output:

trying to create WAMP transport of type: websocket

using WAMP transport type: websocket

onclose unreachable

retrying in 1.5100164652561976 s

trying to create WAMP transport of type: websocket

using WAMP transport type: websocket

onclose unreachable

retrying in 2.2707157162414875 s

It just keeps retrying and failing

Any suggestions?

0 Likes

#6

That is a good idea Mark. I might try that at some stage.

0 Likes