websockify on android

[glitch128]

hey, is it possible to start and connect the websockify server on the android device with termux or something?

[yume-chan]

Termux has Node.js, I believe WebSockify-JS will run on Android. Just note that WebSocket connections to other machines must use TLS encryption. Running both Tango and WebSockify on same Android device should work like running them on same PC.

[glitch128]

ok, so now i get this error using wss://device IP address:15555

Error: WebSocket connect failed
    at WebSocket.<anonymous> (https://tango-adb.github.io/old-demo/_next/static/chunks/pages/_app-b8a1688d9ffda068.js?__WB_REVISION__=b8a1688d9ffda068:1:8643)```

[yume-chan]

There can be three devices, one running Tango, one running WebSockify, and one running Android you want to connect. In WebSockify, use the third device's IP address and ADB over WiFi port as the third argument. In Tango, use the second deviece's IP address, the port number is the first argument to WebSockify.

If device number 2 and number 3 are the same device, i.e., WebSockify is running on the Android device you want to connect, then you can use localhost:<adb port> as the third argument to WebSockify, and use the device's IP address in Tango.

When device number 1 and number 2 are different, i.e., WebSockify is running on a different machine than Tango is running on, an SSL certificate must be provided to WebSockify. In Tango, use wss:// instead of ws://. If the certificate is not issued by a trusted CA, manually trust the certificate on the device running Tango.

[greathh]

@glitch128 Did you solve it? If you solve it, can you share the process? I get the error is _handler exception: [SSL: SSLV3_ALERT_CERTIFICATE_UNKNOWN] sslv3 alert certificate unknown (ssl.c:1007)

[parkerlreed]

Yeah, I think the confusion here is that Chrome no longer allows unsecure web socket from an HTTPS domain and generating your own self-signed certificate for WebSockify.js doesn't seem to be as easy as they claim.

[parkerlreed]

Okay, I think I got the certificate installed. But I'm running into another issue, but I think it's just because of my connecting device (Quest 2)