Overview
Your server is running but nobody can find it — or you can't find it yourself. This is one of the most common DayZ setup issues and it's almost always one of a handful of causes. Work through these checks in order.
Check 1 — Both UDP Ports Must Be Open
DayZ requires two separate UDP ports to be open:
| Port | Purpose |
|---|---|
Game port (default 2302) |
Player connection and game traffic |
Query port (game port + 1, default 2303) |
Steam server browser queries |
Both must be open. A lot of setups open only the game port and wonder why the server isn't listed. The query port is what lets Steam's master servers (and the in-game browser) discover your server.
If you changed your game port with -port=, your query port is always that number + 1. For example, -port=2400 means query port is 2401.
Verify your ports are open using a UDP port checker tool, or check your control panel's network configuration.
Check 2 — Wait for the Server to Fully Initialize
The server must complete startup before it registers with Steam. In your console or .RPT log, look for:
Roles assigned.
This is the line that confirms DayZ is fully initialized and listening for connections. If you check the browser before this line appears, the server won't be listed yet. On a modded server with many mods, startup can take several minutes.
Check 3 — BattlEye Initialization
If BattlEye fails to initialize, the server may not register correctly. Look for BattlEye errors in your startup log:
BattlEye Server: Initialized (v...)
If BattlEye initialization fails, check that the battleye/ folder exists in your profiles directory and that the BE config file is present. Reinstalling server files often fixes this.
Check 4 — verifySignatures Mismatch
If verifySignatures in serverDZ.cfg is set to a value that conflicts with your installed mods (e.g., strict verification with unsigned mods), the server may refuse connections entirely or behave unexpectedly. Check your startup log for signature-related errors.
Check 5 — Steam Master Server Propagation Delay
Even when everything is correctly configured, a new server or a server returning from downtime can take 5–10 minutes to appear in the Steam server browser. This is normal. The browser syncs from Steam's master server list on a delay.
While waiting, use the direct connect method to verify the server is actually up:
- In DayZ, go to the server browser.
- Press
Ctrl+For click the direct IP field. - Enter your server's IP and port (e.g.
123.45.67.89:2302).
If direct connect works but the browser doesn't show it, it's a propagation delay. Give it a few more minutes.
Using the Steam Server Browser as a Diagnostic Tool
The Steam client has its own server browser at View > Servers > Internet (or press Shift+Tab in any game and go to the server browser). Filter by game "DayZ". This browser often updates faster than the in-game one and lets you search by IP directly:
- Open Steam Server Browser.
- Click Favorites.
- Right-click and choose Add a Server by IP address.
- Enter
your.server.ip:2302.
If it shows up here with players/ping data, the server is working. The in-game browser just hasn't caught up yet.
Quick Diagnostic Checklist
- Game port (2302 UDP) is open
- Query port (2303 UDP) is open
- Log shows "Roles assigned."
- BattlEye shows "Initialized"
- No mod signature errors in the log
- Waited at least 10 minutes after startup
- Direct connect works