Server Info (please complete the following information):
OS: Ubuntu 20.04.6 LTS
Browser: Firefox
RMM Version (as shown in top left of web UI): v0.18.2
Installation Method:
[x] Standard
[ ] Standard with --insecure flag at install
[ ] Docker
Agent Info (please complete the following information):
Agent version (as shown in the 'Summary' tab of the agent from web UI): v2.7.0
Agent OS: Windows 10 Pro
Describe the bug
For all agents it is impossible to take control, when those machines are not in the same network as the TRMM server.
When logging the requests with the Firefox developer console, the last thing which happens is a 101 Switching Protocols to wss://mesh.example.com/control.ashx. Then nothing more is done. This WebSocket frequently has a outgoing "action:ping" and an incoming "action:pong" going on, but the window stays blank. On top there is just the "TRMM Agent Status: online" indication.
For machines in the same network as the TRMM server it works as expected.
From the outside only port 443 is accessible to all 3 TRMM domains. As there are no other documented ports, I guess everything runs over port 443.
Server Info (please complete the following information):
Installation Method:
--insecureflag at installAgent Info (please complete the following information):
Describe the bug For all agents it is impossible to take control, when those machines are not in the same network as the TRMM server. When logging the requests with the Firefox developer console, the last thing which happens is a 101 Switching Protocols to wss://mesh.example.com/control.ashx. Then nothing more is done. This WebSocket frequently has a outgoing "action:ping" and an incoming "action:pong" going on, but the window stays blank. On top there is just the "TRMM Agent Status: online" indication. For machines in the same network as the TRMM server it works as expected. From the outside only port 443 is accessible to all 3 TRMM domains. As there are no other documented ports, I guess everything runs over port 443.