Ports and addresses

Allocations, not a private IP

Each instance is assigned allocations: an IP, a port, and a protocol. Uniqueness is that tuple on the node. Several customers can share one IPv4 when their ports differ — that is port multiplex, the launch path.

Pack ports declare bind configurable (host port may remap) or fixed (host port must match the guest). The control plane owns that inventory. The node agent only binds what it is given. It does not pick a port or invent an address.

Join host

Services, the instance overview, and the Ports tab lead with Join address — the IP:port players type into a client. Copy address copies that IP:port and the protocol. It does not mint a dedicated address.

When bind is configurable, the host port may differ from the pack guest port. Join the host IP:port shown — not the guest containerPort. Ports lists each allocation next to its pack bind so remaps stay obvious.

When no allocations are assigned yet, Ports shows UnavailablePanel. That means inventory has not bound a port — not that you are waiting on a dedicated IPv4.

1. Open the instance from Services (the list shows the join host when one exists).
2. Copy address from the overview or Ports — IP:port and protocol.
3. Give players that join host. Switching titles keeps those allocations on the same instance id.

How players join

Type the join host from the overview into the game client. That string is IP:port plus protocol. Several servers share one IPv4. When bind is configurable, the host port may differ from the guest port. When bind is fixed, those two ports match. If Ports shows UnavailablePanel, inventory has not assigned an address yet.