Are you saying that when you tried using insecure (non-TLS) WebSocket from JavaScript, and it didn't work? What sort of error did you get?
If both TLS WebSocket and insecure WebSocket are having problems, then that removes suspicion of something specific to the certificate code. You might have already ruled out that you don't have existing leapd
processes running via ps -A | grep leapd
, but just In case it's a port conflict with something else, could you check lsof -i :6436
and lsof -i :6437
?
I just noticed you said:
since I'd like to run several leap motions off the same machine.
Our software doesn't support two Leap Motion peripherals on the same OS, unfortunately. We've looked into this, and the requirements include some mechanism to distinguish two USB devices, a way to output API data on a separate domain socket, and API support to consume this. For JavaScript, we only require the first one which isn't too hard, but we haven't had much focus on improving the JavaScript API these days.
Others on the forums have accomplished running two Leap Motion devices off the same machine via running a VM.