Connection does not work: firewall, relay and network
Direct or via relay: which connections are needed (443 TCP/UDP) and how to check firewall and proxy.
Agile Remote connects devices directly (P2P) whenever possible. If that fails (strict firewall, mobile network, corporate network), the session automatically runs via relay (TURN) on our server, still end-to-end encrypted. The connection details show which path is used (Path: Direct (P2P) or Relay (TURN)).
These outgoing connections must be allowed:
remote.agiledeveloper.deport 443 (HTTPS and WebSocket/signal): sign-in, presence and connection setup.turn.agiledeveloper.deport 443 UDP (STUN/TURN) and 443 TCP (TURN over TLS) as fallback.- For the direct path also outgoing UDP to any port (allowed in most home and corporate networks).
Check step by step:
- Does the app show Ready for connections? With No connection to the service something blocks access to remote.agiledeveloper.de (firewall, antivirus, proxy).
- A proxy must let WebSocket connections to remote.agiledeveloper.de through.
- If the session hangs at Establishing the connection …, UDP is usually blocked and TCP 443 to turn.agiledeveloper.de as well. Ask your IT to allow both destinations.
- For diagnostics you can turn on Connect via relay only (diagnostics) in the desktop app under Settings › Security. If it works then, the direct path is the problem.
- If the picture stutters, choose quality Highest speed or a single screen.
If the connection drops briefly, Agile Remote reconnects by itself within 30 seconds.
War dieser Artikel hilfreich?