PALA Server Getting Started

What the server does

PALA Server hosts the HTTPS API that PALA Client connects to. It also stores PALA's own data locally and can manage a Palworld dedicated server install for you, including the optional UE4SS mod loader and the PalEventer mod used for scripted server events.

By default, the server listens on:

https://localhost:17443

That default is local-only. If you want other machines to connect, change the listen address and open the port.

Start the server

PALA Server does not require any manual configuration file setup before its first run. Just start it from its install folder:

Windows

.\pala-server.exe

Linux

./pala-server

On first start, PALA Server automatically creates its per-user data folder, generates its TLS certificate, and writes its own config.json with sensible defaults. You do not need to hand-edit any configuration file to get started.

If the server has no enabled Owner account, startup also prints a one-time owner bootstrap token to the PALA server console.

First-time setup

Whenever PALA Server has no enabled Owner account, it enters owner bootstrap mode.

The normal first-run flow is:

1. Start PALA Server.
2. Read the owner bootstrap token printed in the PALA server console.
3. Open PALA Client on any machine that can reach the server.
4. Connect the client to the server URL, such as https://localhost:17443, https://192.168.1.50:17443, or your remote hostname.
5. When prompted, enter the bootstrap token and create the new Owner account.

After an enabled Owner exists, normal login is available again and the printed token is no longer usable.

If you want other machines to connect

The default server bind is 127.0.0.1:17443, which means only the local machine can reach it. To allow LAN or remote clients:

1. Stop PALA Server, edit the listenAddress value in its config.json to a reachable interface and port, then start it again.
2. Open that port in the host firewall.
3. If users are outside your LAN, forward that port through your router or use a VPN/private network.
4. Point client connection profiles at the server's hostname or IP, such as https://pala-server:17443.

Common first-run notes

• Client connection profiles must use an https:// base URL.
• On a private or self-signed setup, the client usually uses TOFU trust mode.
• If you lose every enabled Owner account later, restart PALA Server and use the newly printed bootstrap token to create a replacement Owner account.

Release-package uninstall behavior

Current packaged PALA server releases ship uninstall helpers that distinguish between a standard uninstall and a purge uninstall.

• Standard uninstall removes PALA-created service registrations, packaged PALA server files, and the bundled Mods\PalEventer source copy from the PALA install root, while preserving PALA's config.json and data directory unless you explicitly request purge cleanup.
• Purge uninstall also removes PALA-owned configuration and data from the PALA install root.
• Neither mode ever uninstalls, modifies, or removes the Palworld game-server installation, a live UE4SS installation, or any of their files/data.