Lanthorn Host

Lanthorn Host
Game server node
—

Servers

CPU—
Memory—
Network—
live, every 2 s

Server
Status
Map
Players
Port
Mesh address
Uptime

No servers yet

Pick a game and start one. It is announced on the mesh as soon as it is up.

Games this node has a pack for. A game this node cannot run says why.

Game files on this node's disk, and downloads in progress. Deleting files keeps the game on the Games page; it can be downloaded again.

Per game: checks, downloads and moving servers
This node's agent is older than this page and cannot list its game files. Update the agent.
Game
Status
Size
Used by
Installed

No game files yet

Install a game from the Games page, or start a server and its files download first.

Announced on the mesh

—

Connections for hosted games

How the servers this node runs reach the mesh. A TCP address like 0.0.0.0:4789 makes this node a relay others dial; anything else dials one. LAN auto-discovery does not work from inside a container, where the local network is Docker's own. These apply to every server and are kept across restarts.

UDP here is point-to-point and is not discovered: the far side needs the mirror of this, its local and peer swapped.

Index uplink

This node has no [uplink], so no index drives it. That is separate from hosting on the mesh: [uplink] is how an index manages this node, [mesh] is what announces its games.

Index uplink

This node's address: —

No uplink connections yet.

A move to another region is asked for from a server's menu (Move to another worker…) and decided by an admin of the controller, on the Admin tab. Once approved, the server moves to a worker in that region, which becomes its home; coming back is another request.