Getting started

This walkthrough takes you from two fresh Linux machines to a live proxy route: a VPS that fronts the public internet, and a game host that runs your server. The whole flow is install, pair, map ports, preview, apply.

Private alpha. GameRail currently ships the proxy product. Keep using AMP, GSA, or your existing game-server software. The installer prints a short-lived browser pairing link; you do not copy credentials between machines.

What you need

Use a public VPS as the proxy and workspace authority, and a second machine as the private target. GameRail does not need to run your game-server software.

A public VPS with a routable IP address, a DNS hostname pointing to it, and TCP 443 available for workspace setup.
A game host, at home or rented, running your game server.
Both running Linux with systemd, on x86_64 or ARM64. GameRail checks host prerequisites before installation.
sudo on each machine.

Install on the VPS

Run the installer on the machine that will own your workspace state.

VPS · shell

$ curl -fsSL https://gamerail.app/install | sh

The installer:

resolves one immutable Go release and verifies its installer and assets;
installs gamerail-v2 and dedicated systemd services;
stages the pinned Headscale and tailscaled runtimes for workspace networking;
prints a browser link so you can sign in and choose or create your workspace.

Connect your workspace

Open the link printed by the installer and sign in. Create your workspace and provide the VPS hostname when prompted. The dashboard completes secure enrollment.

installer output

https://dashboard.gamerail.app/#bootstrap=...

The first machine owns your workspace state. Hosted access connects the dashboard to its private API; no browser SSH tunnel or copied controller token is required.

Choose machine roles

Once the machine is online, enable Networking in the dashboard on each proxy participant. Installation and machine roles are separate steps.

Open Network.
Select the VPS.
Enable the Networking module and follow the dashboard setup prompts.

Module dependencies such as WireGuard, nftables, and iperf3 are installed through module setup after you choose what the machine should do.

Pair the game host

Run the same installer on your game host. Open its browser link, sign in, and select the workspace you just created. No second enrollment command is needed.

game host · shell

$ curl -fsSL https://gamerail.app/install | sh

The game host connects out to the workspace authority, so it does not need an inbound port open for pairing.

Build the route

Back in the dashboard, with both machines online, set up the proxy route.

Choose the VPS as the public proxy and the game host as its target.
Confirm the public IP, local interface and tunnel endpoint shown in the setup.
Select the TCP/UDP ports you want to publish.
Review and approve the planned changes, then check the connection status.

When the route is active, players connect to your VPS on the public port and GameRail forwards the traffic across the WireGuard overlay to your game host. Point your server's DNS or share the address, and you are live.

Reference

The stable installer manages its own release URL and checksum verification. It does not accept the old standalone-binary URL or controller-mode overrides.

To inspect the installed version, run gamerail-v2 version. Stable installations enable gamerail-v2-update.timer; an administrator can start gamerail-v2-update.service to check for an update immediately.

Open the dashboard Back to home