Networking & ports

This guide covers networking & ports for a Frags4u-managed Palworld dedicated server. It is written for the Frags4u managed environment, so the server identity, allocated resources and network values shown in the Panel take priority over defaults copied from a generic self-hosting guide.

Palworld operational notes • Networking: Use the assigned UDP game endpoint shown in the Frags4u Panel. A running PalServer process and successful client connectivity are separate checks. • Startup: The managed Linux startup uses PalServer.sh and the server's allocated resources/network settings. • Failure evidence: If the process starts but players cannot join, verify assigned networking and current logs before changing unrelated configuration.

Recommended checks

  1. Use the current address/ports allocated by Frags4u rather than another provider's defaults.
  2. Separate game traffic from query/RCON/reliable/shard endpoints where this game uses them.
  3. Check process health and listening-port evidence independently.
  4. Include the exact client error and the endpoint you tried when raising a ticket.

When to stop changing things If the failure persists after one controlled test, avoid repeated restarts, broad file deletion or unrelated configuration changes. Preserve the newest evidence. A clean process start, a listening game endpoint and a successful client connection are separate signals; record which one is failing.

What to send Support Include the affected server, approximate failure time, exact error text, the last change made and whether the problem affects startup, connectivity, performance, updates or mods. Technical tickets remain bound to the selected game server so staff and AI Support can inspect the correct managed context rather than guessing.

Backups and recovery Before destructive maintenance, keep a verified recovery point. For Palworld, the persistent save/world and configuration areas described above should be treated separately from replaceable base-game assets. Do not use a wipe, reinstall or deletion of runtime files as a first troubleshooting step.

Frags4u AI Support safety boundary AI Support can only use approved typed support actions inside the customer's server boundary. It has no root, sudo, general shell, SSH or node-administration access. Any bounded repair requires customer consent, creates a protected snapshot first, remains limited by the existing remediation policy, and is followed by restart/post-repair verification where a restart is required.