GameRail Proxy Setup

Live controller workflow

Controller anywhere. VPS preferred for this checkpoint.

This flow defaults to a VPS as controller plus proxy when available, but keeps controller, proxy, and target as separate modules so the controller can move later.

0/0online

0active routes

0pending

0attention

Connect to your controller to configure a proxy route.

Using http://127.0.0.1:8787

Connect to controller

Use the local or remote controller URL for this workspace.

Controller URL Controller API token

Add machines

Pair the public VPS and the AMP host. Machines start unassigned.

Machine label

Designate the VPS

For this checkpoint, enable controller and proxy on the public machine. This is a default, not a data-model requirement.

No live machines yet. Pair the VPS and AMP host first.

Choose AMP target and ports

Use detected ports when the API provides them, or enter TCP/UDP ports manually.

Proxy machine

AMP target

Route name

No listening game ports were detected on this target. Enter the port mapping manually.

GameRail starts with the target port and selects the next compatible free range when needed.

Protocol

Target port

Target end

Public port

Public end

Choose the public VPS or proxy machine.