A running game process and player reachability are separate checks. With BYO hosting, you manage the machine's network and your provider's rules.
Find the service address
Open the world, environment, and intended service. The environment's service list displays an Endpoint when assigned. Use that service's address and port; do not substitute a port from someone else's example.
If no address is assigned, check the deployment result and networking configuration. A private machine address is reachable only from its network unless you configure an external route.
Confirm game readiness
Before changing networking, confirm the latest task finished and the game is running. Inspect game logs for port binding errors or repeated restarts.
Two game processes on one node must not listen on the same address and port. A separate environment does not itself resolve port conflicts.
Check network rules
- Confirm the game version and required protocol (TCP or UDP) for your service.
- Check the Linux machine firewall.
- Check inbound network rules at your VPS provider.
- Behind a router, check forwarding for the intended port and public address availability.
- Try connecting from the player's network, not only from the host machine.
If players cannot connect
Check the address, port, client version, and mods. Confirm the server save is loaded and inspect logs for connection rejection. A modded server may require a compatible loader and mod set on the client.
If the process is stopped, return to Troubleshooting. If it runs but the network is unreachable, include the selected address, protocol, and checked network rules in your support request, without secrets.