Server Connection Problems

Server Connection Problems

PalCenter connects from inside its container to the official Palworld REST API.

Verify the REST URL

Use a complete URL with protocol and port:

http://192.168.1.50:8212

• Do not omit http:// or https://.
• Use the REST API port from the Palworld server configuration.
• Do not use localhost unless Palworld is running inside the same container, which is not a supported PalCenter deployment.

Verify Palworld configuration

Confirm that:

• The official REST API is enabled
• The Palworld server is running
• The REST API is listening on an address reachable from PalCenter
• The Administrator password is correct

Restart the Palworld server after changing its REST configuration if required by your server setup.

Test container connectivity

Check that firewalls, VLANs, Docker networks, and routing allow the PalCenter container to reach the Palworld host and REST port.

If Palworld is on another Docker network, use an address that is resolvable and reachable from PalCenter. PalCenter does not need the Docker socket.

Read the error

• Connection refused: No service accepted the connection at that address and port.
• Fetch failed or timed out: Routing, firewall, DNS, or service availability is preventing a response.
• Authentication error: Verify the Palworld Administrator password.
• Offline card: PalCenter keeps the saved connection but could not retrieve current live status.

Return to Add Server and run Test Connection after correcting the issue.