DayZ server trouble splits into two: the server not listing, and the dreaded mod mismatch on join. Here's how to fix both — vanilla and modded — plus the DZSA-specific quirks and how to stop mismatches recurring.
Quick answer
A DayZ server that does not show in the launcher usually has its game port or Steam query port (UDP) closed. On modded servers, players also hit mod mismatches on join: point them to the DZSA Launcher, which loads the server's mods automatically, and restart the server after any mod update.
Open the ports
DayZ needs the game port plus a Steam query port over UDP:
2302/udp game (default)
27016/udp Steam query
2303-2305/udp (used by some setups)Mods must match — use the DZSA Launcher
For modded servers, every client must load the same mods in the same order as the server. The DZSA Launcher handles this automatically — it reads the server's mod list and loads them for the player. Point players to DZSA rather than manual mod setup.
Restart the server so it serves the new version. A mod that updated on the Workshop but not on the server causes an instant mismatch kick.
Connect directly
In DZSA Launcher you can add the server by IP, or in-game use the community browser and the favourite/direct-connect with server-ip:2302. Direct connect avoids the slow browser refresh.
Still not listing?
- Confirm the Steam query port (27016) is open — it's what feeds the browser.
- Check the server actually started (read the server log for mod load errors).
- Make sure the server name/visibility is set in the config.
Open 2302 + 27016 query, use DZSA so mods match in order, and restart the server after any mod update.
DZSA-specific quirks
- DZSA caches server data — a server that just changed name, mods or ports can show stale info for a while; wait or refresh the list manually.
- BattlEye kicks with a generic message when a client mod version doesn't match — this looks like a mismatch but is really a stale client cache; have the player verify/update mods in DZSA.
- A server behind CDN-style anti-DDoS or a reverse proxy needs its real game IP registered with Steam, not a proxy address, or DZSA can't query it.
How to avoid mod mismatches going forward
- Pin exact Workshop mod versions in your server's modlist rather than relying on "always latest".
- Publish and pin your server's mod list publicly (DZSA reads this) so players' launchers auto-sync.
- Restart the server immediately after any Workshop mod update — don't leave it running the old version.
Related errors
Setting one up from scratch? See how to set up a DayZ server, then tune loot, time and security with our best DayZ server settings. A similar problem on ARK is covered in fixing ARK mods not downloading. For general port setup, see how to port forward a game server.
DayZ is a trademark of Bohemia Interactive. ESAGAMES is an independent hosting provider, not affiliated with or endorsed by Bohemia Interactive.