How to fix a DayZ server not showing in the launcher

By Niko Catarino

Updated 8 October 2026

If your DayZ server is missing from the launcher, first check whether the game process starts and whether a player can join its public address. Then check the Steam query endpoint used for discovery. A working game connection and a working server-browser query use different ports.

This guide covers a server you administer on DayZ PC. If every community server is missing from one player’s browser, test that client’s filters and connection first; changing your server cannot fix an entire empty client list.

Identify which connection fails

Observation	Investigate first
DayZ exits during startup	Configuration path, mission, mods and startup logs.
The process runs, but no external player can join	Public address, game port, UDP routing and client/server compatibility.
External direct joins work, but the server is missing from lists	Query port, query reachability and launcher filters.
It appears in one launcher but not another	The missing launcher’s query/check process and filters.
Players can join, but a launcher shows an unexpected population	Compare a fresh query with that launcher’s list data and filters.
A query for a second instance identifies the first server	Both instances’ query assignments, process listeners and forwarding destinations.
Other players can find it, but one player cannot	That player’s filters, saved address, game branch and required mods.

Scroll to see all columns →

Write down the exact error, launcher, time, server build and address used. Change one setting or component at a time so a successful join tells you which fix worked.

If DayZ gives a hexadecimal error code, use the connection and kick lookup to choose the next check. A password rejection, character-data error or BattlEye kick needs a different investigation from a missing query reply.

Download the visibility worksheet and keep one record per instance. Record the tester’s network, tool, endpoint, time and outcome. A note saying “ports open” leaves the game and query paths unidentified.

Check startup and the active configuration

Read the latest RPT and script logs, not a previous run’s output. Even when the panel shows a running process, check that the mission finished loading and clients can join.

On a self-managed host, inspect the service or launch script:

• -config must point to the intended server configuration file. A relative path is resolved in the process’s working directory.
• The mission template must match an installed mission directory.
• Required mod paths and dependencies must exist and use the expected load order.
• The game and query ports must match this instance’s assignment and must not conflict with another instance.

For server config not found, correct the actual -config path and working directory. Renaming a file to serverDZ.cfg won’t help if the service launches with a different path. Bohemia’s server configuration reference documents the configuration argument and server settings.

On VXPanel, compare Advanced launch settings with Config. Let the Mods page manage its own load list; resolve startup errors before investigating a launcher cache.

Managed launch settings can override values in the file. Confirm the effective assignment in the panel before editing steamQueryPort manually; CFTools documents this behavior for managed process configuration.

Test a direct connection from outside the host network

Use the server’s public address and game port for a direct join. In VYKIX, copy both from Network, then connect with an updated client and the required mods.

Ask a player on a different network to test, or use another connection you control. A join from the host PC or the same LAN won’t tell you whether outside players can reach it. A home router without NAT loopback can also make your public address fail from inside the LAN even when external players can join.

If the join reports a build or mod mismatch, follow server and mod updates. If it times out, check that the address and game-port routing reach this server before changing its loot files or permissions.

Match the game and query ports

Endpoint	Where its value comes from	Use
Game	The launch -port value or managed assignment	Player connections and gameplay.
Steam query	steamQueryPort in the active configuration or managed assignment	Steam/A2S queries and server discovery.
RCON	The server’s BattlEye/RCON configuration or managed assignment	Private administration tools.

Scroll to see all columns →

For example, a self-managed launch can use -port=2302 and the active server configuration can contain:

steamQueryPort = 2305;

These are example values, not replacements for your provider’s assigned ports. Use the game port for a direct join and the query port for a launcher query check. Opening RCON does not make the server discoverable.

After changing a port, restart during maintenance and update the matching firewall and forwarding rules. Preserve any additional UDP ports required by your deployment’s networking instructions. For a complete installation, use the DayZ networking setup.

Check listeners and UDP routing

On a self-managed Windows host, run PowerShell while DayZ is running:

Get-Process -Name DayZServer_x64 -ErrorAction SilentlyContinue |
    ForEach-Object { Get-NetUDPEndpoint -OwningProcess $_.Id } |
    Select-Object LocalAddress, LocalPort, OwningProcess

On Linux, inspect UDP listeners:

ss -lunp

Look for the expected ports and bind address. If Windows denies access to socket information, run the read-only inspection from an elevated PowerShell session. Linux may hide process details for services owned by another account. A local listener proves that the host has bound an endpoint; it does not prove that an internet query can reach it.

Check each socket rather than assuming that -ip applies to every service. In our Windows test, the game port bound to 127.0.0.1, while the query socket bound to 0.0.0.0. You still need an external query test for that wildcard binding.

If several DayZ instances run on the Windows host, choose the affected process ID from the first command rather than combining their assignments. Replace 1234 with that PID:

Get-NetUDPEndpoint -OwningProcess 1234 |
    Select-Object LocalAddress, LocalPort, OwningProcess

Compare that process’s sockets with its launch settings and the worksheet. If the query identifies another server, retain the response and inspect both instances; a shared public address still needs distinct query endpoints mapped to the intended service. Microsoft UDP endpoint reference.

For a firewall or router you manage, verify:

1. The rules allow the required UDP traffic, including the configured query port.
2. Port forwarding targets the current internal address of the DayZ host.
3. A cloud or provider firewall also allows the assigned traffic, where applicable.
4. The host binds to an address available on its network interface.
5. The public address reaches your router or host. Double NAT and carrier-grade NAT can prevent inbound forwarding through a router you control alone.

Do not treat a TCP-only port checker as a test of a DayZ UDP query. Keep firewall protection enabled and correct the specific rules. On managed VYKIX servers, retain assigned ports and ask support to investigate unreachable endpoints with the address, query port and timestamp you tested.

PowerShell’s Test-NetConnection -Port checks TCP. Neither a pass nor a failure tells you whether UDP works on the same port number. Use the game for the join check and a query client for discovery. Microsoft Test-NetConnection reference.

An A2S_INFO response can identify the server’s name, map, player count and build. Compare those fields with the instance you intended to query. A reply from another instance is evidence to investigate its port mapping. The query client should support Valve’s challenge exchange; a tool that cannot complete it can fail even when a server answers. Valve server-query reference.

Check the launcher with the query endpoint

In VXPanel Network, choose DZSALauncher check after refreshing the address and ports. It opens a check using Server IP + Query Port. This is a discovery check; it does not start DayZ, test a game join or change the server configuration.

On a self-managed server, open the launcher’s Check Server page, enter your public IP:Steam Query Port, and select Check Server. Confirm the returned server identity. Its stated listing delay is approximate; a successful check does not guarantee that every player’s list updates immediately.

For the launcher where the server is missing:

1. Select community servers and clear filters that exclude the server, including password, mod, population and ping filters.
2. Search the exact configured hostname, then check the current address where that launcher permits it. Saved favorites can still reference an old address.
3. Refresh after the server has completed startup. If a launcher query fails, compare its endpoint with the server’s actual query assignment.
4. Compare another player’s result or another launcher. A failure isolated to one list needs that launcher’s discovery checks.

If an external join and fresh query both work, check the affected launcher’s current service notices or support before changing server settings. Don’t assume a server-port fault from a stale population count or a failure in just one launcher. Record which tool produced each result.

Do not repeatedly change ports while waiting for a list to refresh. Keep the known-working game endpoint and diagnose the query endpoint from the recorded result.

Check a mod that reports Workshop ID 0

If the launcher check names a mod with Steam Workshop ID 0, inspect that package’s Workshop metadata before changing ports. In a downloaded DayZ mod, meta.cpp sits at the mod root beside Addons and Keys; it holds publishing metadata. The separate mod.cpp describes how the mod is presented. Bohemia’s DayZ mod structure

1. Match the named mod to the folder your server actually loads. Use the path in the error or compare it with the active mod list. Inspect that folder’s meta.cpp, including its publishedid value.
2. Confirm which original Workshop item supplies those files. Its page URL contains the numeric item ID after id=. A folder label or similar mod name is not enough to identify the item. A private local mod might have no published item at all; don’t give it another mod’s ID or substitute 1 for 0. Ask its author for the supported distribution and joining instructions.
3. Prefer the author’s corrected package when one is available. Back up the installed package and use the normal mod-update procedure, keeping server and client versions aligned. If you publish the mod yourself, Bohemia’s support response says to update it after the initial publication so the ID is included. Publisher support response, November 2023
4. For a temporary correction, first confirm the exact item and that its author supports this repair. Stop the server and back up meta.cpp. Change the existing publishedid = 0; entry to that item’s numeric ID, preserving the semicolon and other fields. Keep the filename meta.cpp; don’t save it as meta.cpp.txt or create a second publishedid entry.
5. Restart, repeat the query check and confirm it identifies the intended package. Then test a client join with matching mods. Check the metadata again after an update, which can replace your local correction. If the change fails, restore the saved file and keep the exact error for the author or launcher support.

The temporary edit follows a mod author’s June 2025 repair instructions, followed by a corrected upload. It addresses an identified package’s metadata, not every “Failed to sync” error. No current DZSA execution or successful mod download was tested for this procedure. Keep the server’s working ports, signature checks and persistence intact while investigating.

Give players a joining checklist

Give players the exact server name, public IP and game port, Stable or Experimental branch, required map/DLC and current mod instructions. Share the join password privately when one is required. Keep RCON credentials out of the joining instructions.

Join through the DayZ launcher

1. Update DayZ in Steam and open its launcher. Use the separate Experimental client only when the owner identifies an Experimental server.
2. Open the launcher’s server browser, choose the community list and search the owner’s exact server name. Clear filters that exclude it. Compare the address and map before joining a similarly named server.
3. Select the server’s join action and review the required-mod setup. Finish any required Workshop downloads before retrying. A mod prompt that cannot identify the package needs the owner’s exact Workshop link or supported manual instructions.
4. If the owner gives an IP and game port, use Direct Connect. Review the mod-management window it opens, then continue the join. Bohemia’s 1.22 launcher notes document that window and the option to add the server to favourites from Direct Connect.
5. Enter the join password if asked. Once connected, confirm the intended server and character. If rejected, retain the full error code and reason instead of repeatedly changing mods.

Join through DZSA Launcher

DZSA Launcher is an unofficial launcher. Its published interface shows a name filter, a triangular Play control for each server and a star in the FAV column.

1. Install the launcher from its own site if you choose to use it. Have Steam and the matching DayZ client installed and updated.
2. Reset restrictive filters, enter the server name and compare the listed IP, map and version with the owner’s details. Show favourites only hides servers you haven’t saved.
3. Use the server’s Play control. Follow the launcher’s required-mod prompts and let downloads finish. If it cannot resolve a required mod, give the owner the exact message and package name; selecting another unrelated Workshop item won’t supply that package.
4. After confirming the server, use its star to save it, then use Show favourites only for the next visit. Recheck saved addresses after a server move.

A launcher listing is only the discovery step. Confirm the game actually joins. If DZSA fails while the ordinary launcher joins, retain both results and use DZSA’s support route; keep the working server endpoint unchanged while investigating.

These player steps used AI-assisted research and drafting on 8 October 2026. The official launcher behavior was checked against Bohemia’s published notes; DZSA’s controls were read from the screenshot currently published on its site. That screenshot has no stated capture date. Neither installed launcher, mod-download workflow nor player join was tested here.

Verify the fix and keep the evidence

The fix is complete when an external client can both discover the server in the intended launcher and join with the required mods. Repeat those checks after a normal restart to confirm that the saved launch settings remain in effect.

Record the public game and query endpoints, configured hostname, build, successful test time and corrected setting. If you still need help, include that record, the exact error and relevant startup log lines. Remove passwords, authentication tokens and unrelated player details before sharing logs.

For a failed configuration change, stop the server, restore the previous config or launch settings, and restore matching routing rules. Do not delete persistence to fix server discovery.