Forum Discussion
Websocket forwarding?
I have an old (really old, RBR10) mesh router, and I'm trying to use an app which prefers to use websockets. Does port forwarding allow this? If so, how do I configure it?
I'm trying to use an app which prefers to use websockets
Websockets (as the name suggests) are built on browser protocols. They generally just use port 80 (unencrypted http) or port 443 (encrypted https). Port forwarding is NOT likely to be the appropriate solution.
Can you give more details on the app you are trying to use, and what problem you are seeing? Is there any documentation for the app that suggests that port forwarding is needed?
Basically, it's desktop as a service on a shoestring. (We're a little non-profit, and this is a little project; my budget is limited.) So I've got a Windows system with two different ways to establish a VNC connection through a browser, but one of them requires websockets and the other prefers them. So, any thoughts?
So I've got a Windows system with two different ways to establish a VNC connection through a browser, but one of them requires websockets and the other prefers them. So, any thoughts?
The easiest would be to just use Google remote desktop, which requires no development at all.
Anyway, I'd think the reverse proxy you have in the design would work, you could just put it in the router DMZ.
Other approaches you could look into are using TailScale or maybe a CloudFlare tunnel.
That's a good idea, and not one I'd considered. There are other remote desktop solutions that might also work. Thanks!