I have a problem with using websockets with Argo.
Our application has three components
- IIS7 hosting the static content (*.html, *.js, *.png, …) over HTTP on port 8003.
- Standalone application serving dynamic RESTful content over HTTP on port 1341.
- Another standalone application serving streaming content over a websocket (ws://) on port 7171.
I can create an argo tunnel with the command
./cloudflared --hostname host1.example.com --url http://server.internal and connect with my browser to `https://host1.example.com and see the static content loading. However I can also see it trying to connect to the other components using their internal hostnames and ports which obviously fails from outside the internal network.
What do I need to do to successfully tunnel all three internal sources?