NolimitHost
Last updated: July 23, 2026
Connection issues are usually caused by an incorrect network configuration, blocked ports, firewall rules, or an incomplete server setup. This guide walks through the most common causes and how to fix them, so you and your friends can join your server.
Make sure the server has finished starting — look for a fully loaded world without fatal errors. You can watch the startup output in the Console of your NolimitHost Game Panel. Common causes of incomplete startup: corrupted save data, invalid config, missing files, or insufficient memory.
Stop your server first, so it doesn't overwrite your changes while you work. Then open PalWorldSettings.ini (the main configuration file for your server) via File Manager and confirm:
PublicPort matches the port (default: 8211) — this is the port players connect toServerPassword and AdminPassword have no accidental quotes or trailing whitespaceMost servers do not need to manually specify PublicIP. Save your changes and restart the server to apply them.
| Field | Value |
|---|---|
| Protocol | UDP |
| Port | 8211 |
| Internal IP | Your server's local IP |
Also allow inbound UDP 8211 in the Windows firewall or Linux firewall (iptables/ufw). Watch for Double NAT if your router's WAN IP differs from your public IP — this may require ISP modem bridge mode.
netstat -ano | findstr 8211 — look for UDP 8211 in usess -lunp — confirm the server bound to UDP 8211public_ip:8211| Problem | Fix |
|---|---|
| Connection timed out | Check port forwarding, firewalls, and that the server finished starting |
| Version mismatch | Update the server via SteamCMD and all clients via Steam |
| Incorrect password | Double-check ServerPassword and remove accidental quotes or spaces |
| Mods causing issues | Temporarily disable all mods and test vanilla |
This website uses cookies to ensure security, session management, and basic functionality. For details on all cookies used and how to manage your preferences, please see our Privacy Policy.