RMS Connect provides a proxied remote access session to a Teltonika device’s web interface (Luci-based UI) and CLI (command line) from the RMS dashboard. It works through NAT and firewalls without port forwarding or a public IP on the device. Sessions are encrypted end-to-end via the RMS tunnel.
The Teltonika device maintains a persistent outbound HTTPS connection to the RMS platform. When you initiate an RMS Connect session from the dashboard, RMS proxies your browser session through this existing tunnel to the device’s local web interface. You see the device’s own web UI as if you were connected locally – but you are accessing it via the cloud.
For CLI access, RMS Connect provides a browser-based SSH terminal that connects to the device’s shell via the same tunnel. No SSH client installation required on your side; no open SSH port required on the device side.
| Method | Setup complexity | Public IP needed | Port forwarding | Security |
|---|---|---|---|---|
| RMS Connect | Zero – included in RMS | No | No | TLS via RMS tunnel |
| OpenVPN / WireGuard | Medium – requires VPN server | For VPN server | Depends on config | Strong – if well configured |
| Port forwarding SSH | Low – but risky | Yes | Yes | Poor if exposed publicly |
| RMS VPN | Low – configured in RMS | No | No | TLS via RMS |