Agent firewall entries
Traffic between Manager and the Agent is WebSocket. With the default configuration that is WebSocket over TLS (wss) on port 8090.
If you change http_server.port in config.toml, update the firewall to match.
Allow this on every Agent host:
- TCP inbound on the Agent listen port
- TCP outbound on the Agent listen port
- TCP outbound to the cloud controller and the other hostnames below
Do not whitelist by IP. Those addresses change. Allow the hostnames.
| Hostname | Use |
|---|---|
| Agent listen address, default port 8090 | Manager and API clients |
gw.gameserver.cloud port 8080 | Default cloud controller |
api.gameserver.cloud | Licensing and cloud-controller peer list |
api2.gameserver.cloud | Fallback peer list |
cdn.gameserver.cloud | Windows assets and content, World region |
architect.cftools.com | Agent updates and tray assets |
gw-architect.cftools.ru | Windows assets when the Agent country code is RU |
Manager-side hostnames are listed in Networking requirements.
Creating extra host firewall rules from Manager is a separate screen. See Firewall rules.
Related Articles
Frequently asked questions
Common questions about connecting Manager to an Agent, console windows, OmegaManager migration, ports, RCon, and the cache directory.
Moving an Agent installation
Depending on requirement, you may not require to move the entire installation, it is possible to change the locations of the following directories:
Updating an Architect Agent
Update Architect Agent from Toolbox on Windows, or replace the binary manually when an automatic update is not available.