Necesse Dedicated Server Troubleshooting
Solutions to common Necesse dedicated server problems: server not visible, players unable to connect, config not applying, latency kicks, and world load failures.
Server Not Visible / Players Cannot Find It
Necesse does not have a public server browser. Players must connect via direct IP and port. There is no listing to appear in.
- Share your server's public IP address and port (default
14159) directly with players. - Confirm your public IP using a service like whatismyip.com.
If players can see the IP but cannot connect, continue to the next section.
Players Cannot Connect
Check UDP port 14159 is open and forwarded:
# Linux — confirm the port is listening
ss -ulnp | grep 14159
# Test from an external machine
nmap -sU -p 14159 <your-public-ip>
- Verify your router has a port forward rule: UDP
14159→ server LAN IP. - Verify the host firewall allows UDP
14159inbound (see Port Forwarding guide).
Confirm the world has finished loading:
The server console must show Server started before players can connect. If the server is still generating the world or loading assets, connections will be refused. Wait for that message before directing players to connect.
Config Changes Not Applying
server.cfg is overwritten on every startup based on launch arguments. If you edit the file manually and then restart the server without matching arguments, your edits will be lost.
Solution: set all configuration via launch arguments:
./StartServer-nogui.sh -world MySave -port 14159 -slots 10 -password "secret"
Review the server.cfg Reference for the full list of available arguments.
Players Getting Kicked for Latency
The maxClientLatencySeconds setting (default: 30 seconds) kicks clients whose latency exceeds the threshold. If players on high-latency connections are being kicked unexpectedly, raise this value:
./StartServer-nogui.sh -world MySave -maxclientlatencyseconds 60
Server Crashes on Startup
Check the server logs for the error:
| Platform | Log Path |
|---|---|
| Linux | ~/.config/Necesse/logs/ |
| Windows | C:\Users\[Username]\AppData\Roaming\Necesse\logs\ |
Common causes:
- Missing dependencies (Linux): Ensure
lib32gcc1andlib32gcc-s1are installed. See Linux server guide. - Corrupted save file: If the crash occurs when loading a world, restore from a backup. See World Backups.
- Port already in use: Another process is using UDP
14159. Change the port with-portor stop the conflicting process.
Players Cannot Join After World Wipe
If you deleted or renamed the world .zip and players cannot join, verify:
- The new (or restored)
.zipfilename exactly matches the-worldargument passed to the server. - The server console shows
Server started— the new world may take longer to generate. - There are no leftover lock files or partial saves in the saves directory.
The -world argument is case-sensitive on Linux. MySave and mysave are treated as different worlds.
Permissions Not Taking Effect
The /permissions set command requires the target player to be online at the time the command is run. You cannot pre-grant permissions to offline players. Have the player connect first, then run the command.