Skip to content

Networking and Multiple Launchers

Launcher Admin opens in a browser at the Launcher Server address. Windows Agent on a gaming PC connects to that server separately to report status and receive session commands. To check Agent’s connection, open General → Connection.

  • In configured mode, Agent connects to one address set by your administrator. Check it under Launcher connections. On another PC, use a network address that the gaming PC can reach.
  • In auto mode, Agent periodically sends a broadcast request on the local network. Launcher Servers with discovery enabled respond with their names and addresses. Agent tries to maintain a separate connection to each server it discovers.
  • If the intended server is unreachable, Agent may show Waiting for Launcher Server, Waiting for Launcher Servers, Discovery error, or Reconnecting. Check the target server’s state and address under Launcher connections and record Details if shown. The installation administrator changes the mode and address.

One PC can appear in Available Agents on multiple Launcher Servers. Each server has its own My Agents list. Add the PC on the server you will use to run the session. Removing it from one list affects that list.

If two Launcher Servers try to launch a game on the same Agent at the same time, Agent handles the requests in order. Once the first launch is running, the other request is rejected because the PC is busy. Stop the session from Running Sessions on the Launcher Server that started it. For a game process with a recorded owner, that server keeps permission to stop the process after reconnecting.

  1. Check Launcher connections under General. When you see Partially connected, find the row for the intended server. Healthy connections to the other servers can remain active.
  2. If the server is missing from the list, check that it is running. Ask your administrator to verify Agent’s connection mode, discovery on both sides, matching UDP ports, and whether the broadcasts reach the server. Broadcasts may fail to cross network segments.
  3. If the server appears as Reconnecting or Disconnected, give your administrator the displayed address and Details. Check whether the gaming PC can reach the Agent connection address and port. Check discovery replies and the Agent connection separately.
  4. Once the connection returns, open Launcher Admin for that server and check My Agents. If the problem recurs, open the Agent logs.
Purpose Default port in the installed package
Launcher Admin in a browser TCP 8080
Windows Agent connection to Launcher Server TCP 8090
Automatic discovery UDP 47777

Check the actual values in your club’s configuration and firewall rules. A bind address controls the interfaces on which the server listens. 0.0.0.0 means all local IPv4 interfaces. The advertised address is the address the server gives Agent during discovery. Gaming PCs must be able to reach it. With auto, Launcher Server picks a suitable local IPv4 address. On a server with multiple interfaces, check that the selected address is reachable from the gaming network. Without a suitable address, server startup fails and the server log records the reason.

Use automatic discovery on the club’s trusted network. My Agents stores the participant list for one Launcher Server. Control network access separately using your club’s rules. The Agent WebSocket currently uses an unencrypted connection without transport-level authentication. Keep discovery and Agent WebSocket ports off the public internet.