HumanitZHumanitZ Server Not Showing or Friends Can't Connect (Fixes)
HumanitZ server missing from Find Server or friends cannot join? Fix game port vs query port, version mismatch, passwords and allowed players.
Updated Oct 7, 2026 · 5 min read
On this page
When a HumanitZ dedicated server does not show in Find Server or friends cannot join, the usual causes are: the query port (UDP 27015 by default) is closed so the list cannot see the server, players typing the query port instead of the game port in the direct connection fields, the server on an older build than the players after a patch, a wrong password, or OnlyAllowedPlayers=1 turning away anyone not on the list. Direct connection with the IP and game port is the fastest way to tell a listing problem from a real connection problem.
How joining works
Players choose Play, then Multiplayer, pick or create a character and click Find Server. The list shows dedicated servers it can query. At the bottom right are direct connection fields: IP, port and password, then IP Connect.
Two ports matter:
| Port | Set by | What it is for |
|---|---|---|
| Game port | -port= on the launch line |
The connection players make, and the port for IP Connect |
| Query port | -queryport=, often 27015 |
Lets the server list read your server |
Both are UDP.
Problem 1: Not in the Find Server list
- Query port closed. The list relies on the query port. If it is not forwarded or the firewall blocks it, the server runs fine but never shows up. Forward it as UDP.
- Search mismatch. Search for the exact
ServerNamefromGameServerSettings.ini. Special characters or a very long name make searching awkward; keep the name simple. - Version mismatch. A server on an older build than the player is hidden or rejected. See problem 3.
- Server still starting. A big save takes time to load. Watch the console until it reports the server is up.
If direct connection works but the list does not show it, the server is reachable and only the query side needs fixing. Players can keep using IP Connect meanwhile.
Problem 2: IP Connect fails
The most common mistake: entering the query port in the direct connection field. IP Connect needs the game port. On a hosted server, that is the port in the address your panel shows, not the query port listed in the settings.
If the port is right and it still times out:
- Forward the game port as UDP to the server's local IP.
- Allow the server executable through the firewall.
- Check for CGNAT: if your router's WAN IP differs from your public IP, port forwarding cannot work. Hosting without port forwarding explains the options.
Problem 3: Version mismatch after an update
HumanitZ left Early Access with version 1.0 in February 2026 and still gets patches. Players update through Steam right away. A self hosted server installed with SteamCMD stays on the old build until you update it:
steamcmd +force_install_dir /home/humanitz/server +login anonymous +app_update 2728330 -beta linuxbranch validate +quit
On Windows, drop the -beta linuxbranch part. Restart the server after updating. Make sure players are not on a beta branch the server is not running: in Steam, right click HumanitZ, Properties, Betas.
Problem 4: Rejected with the right address
| Situation | Cause | Fix |
|---|---|---|
| Rejected after entering a password | Password in the ini differs from what they typed |
Check the value; avoid special characters |
| Rejected with no password prompt | OnlyAllowedPlayers=1 and they are not on the list |
Add them to the allowed list, or turn it off |
| Rejected straight away every time | They are in F_BannedPlayers.txt |
Remove their ID with the server stopped |
| Server full | MaxPlayers reached |
Raise it; the developers list 24 as the cap |
OnlyAllowedPlayers catches people out because it works silently. If you turned it on months ago and a new friend cannot join, that is the first thing to check.
Problem 5: Changes to the ini do nothing
Most HumanitZ settings are read when the server starts. If you changed the password or max players and nothing happened, restart. Also make sure you edited TSSGame/GameServerSettings.ini in the server's folder, not a copy elsewhere. On a hosted server, panel settings are written into that file on every start, so edit them in the panel rather than the file.
Problem 6: Laggy or dropping connections
If players connect but rubber band or drop, the server may be short on memory or CPU, especially with many players spread across the map or a long running save with big bases. Check memory use in your panel or task manager. Why is my game server lagging walks through the checks, and a server closer to your players helps more than any setting.
Checklist
- Server finished starting, console shows no errors.
- Server and players on the same game build.
- Game port and query port forwarded as UDP.
- Friends use the game port for IP Connect.
- Password,
OnlyAllowedPlayersand ban list checked.
A server that is just reachable
A GamezServers HumanitZ server has its own address with the game and query ports open, and Auto Update in the panel brings it to the latest build on restart. Server Password, Max Players and Only Allowed Players are panel fields, and the live console shows when the world has finished loading. Friends type the address from your panel into IP Connect, or find the server by name. New to admin on HumanitZ? See HumanitZ admin commands, and the basics in how to host a HumanitZ server.
FAQ
Why is my HumanitZ server not in the server list?
The query port is usually closed, or the server is on an older build. Open UDP 27015 (or your query port) and update the server.
Which port do I use for HumanitZ IP Connect?
The game port, not the query port.
Why can't my friend join even with the right IP?
Check the password, whether Only Allowed Players is on, and whether they are on the ban list.
Do HumanitZ ini changes need a restart?
Yes. Most settings are read when the server starts.
Skip the setup. Your own HumanitZ server.
Then $14.99/mo. Just trying it? $3.75 for 3 days