---
title: Project Zomboid server not showing up or failed to respond? A Build 42 checklist
description: Build 42 went stable in July 2026 and brought a record crowd, a lot of new dedicated servers and the same handful of failures: the server isn't in the list, 'failed to respond', a version mismatch after an update, or a start that takes ten minutes of mod downloads. Here's what DefaultPort and UDPPort actually do, how to check a server from outside, and how to tell your survivors it's down before they tell you.
canonical: https://watchfor.io/blog/project-zomboid-server-not-showing-up
---

# Project Zomboid server not showing up or failed to respond? A Build 42 checklist

2026-11-16 · WatchFor Team · Game servers · game-servers, project-zomboid, networking

Build 42 went stable in July 2026 and brought a record crowd, a lot of new dedicated servers and the same handful of failures: the server isn't in the list, 'failed to respond', a version mismatch after an update, or a start that takes ten minutes of mod downloads. Here's what DefaultPort and UDPPort actually do, how to check a server from outside, and how to tell your survivors it's down before they tell you.

Build 42 changed what a Project Zomboid server is. Multiplayer arrived on
the unstable branch in
[December 2025](https://store.steampowered.com/news/app/108600/view/1818752592122972),
Build 42 became the stable default with
[42.20 on July 29, 2026](https://store.steampowered.com/news/app/108600/view/1839676055882259),
and July set the game's all-time Steam record at about 124,500 concurrent
players ([SteamCharts](https://steamcharts.com/app/108600)). That brought a
lot of new servers, and a lot of searches that start with "project zomboid
server not showing up" and "failed to respond".

Most of those come down to the same few causes. This checklist goes through
them in the order they usually turn out to be the problem, then covers how
to check a server from outside and how to keep watching it.

## The two ports, and which one answers the list

In your server's `.ini` (by default `Zomboid/Server/servertest.ini`, named
after your server):

```ini
PublicName=Knox County Survivors
Public=true
DefaultPort=16261
UDPPort=16262
MaxPlayers=16
Password=
WorkshopItems=...
Mods=...
```

| Key | Port | Protocol | Used for |
| --- | --- | --- | --- |
| `DefaultPort` | 16261 | UDP | Players connecting **and** the Steam server query |
| `UDPPort` | 16262 | UDP | Game traffic |

Forward **both, over UDP**. A TCP-only rule, or a forward of 16261 alone,
gives you a server that sometimes lets people in and never quite behaves.

The Steam query, which the in-game browser, server trackers and monitors
use, answers on **`DefaultPort`**. So the address you give a status tool is
the same `your-ip:16261` players use. Project Zomboid is friendlier than many
games here: no separate query port to hunt for.

## "Not showing up" in the list

1. **`Public=true`?** A server that isn't public doesn't register in the
   list. Friends can still join by IP.
2. **Both UDP ports forwarded**, on the router and on the host's firewall.
3. **Steam mode.** A server started with `-nosteam` doesn't register with
   Steam at all; it won't appear in the Steam list or answer the Steam
   query. Only use it on purpose.
4. **The filters.** The in-game list hides servers that don't match your
   version, are full, or have a password, depending on the filter settings.
   Search by name with the filters cleared before assuming the worst.

## "Failed to respond"

This one is about timing more often than networking.

- **The server isn't ready yet.** A server with a long Workshop list
  downloads and validates mods on every start. Until the log shows the
  server is up, it doesn't answer, and clients report "failed to respond".
  Ten minutes is not unusual for heavy modlists.
- **A mod failed.** A mod that was removed from the Workshop or broken by an
  update can stop the server during launch ("server has stopped during
  launch" is the other common search). The server log names it.
- **Ports.** As above: UDP, both of them.
- **Memory.** Larger maps and more players need more Java heap. If the
  server stalls or dies under load, raise the `-Xmx` value in the server's
  launch configuration, within what the machine actually has.

## After an update: same server, nobody can join

Project Zomboid clients and servers must run the same build. Two things to
know in the Build 42 era:

- **Branches moved.** On
  [October 27, 2026](https://store.steampowered.com/news/app/108600/view/1847286114049399)
  The Indie Stone replaced the "unstable" branch with a **pre-release**
  branch, where builds spend at least a week before they reach stable.
  Players who opted into pre-release can't join your server on the default
  branch, and the other way round. Build 41 lives on as `legacy41`.
- **Update the server when the game updates.** The dedicated server is its
  own Steam app (380870). Install the same branch your players are on:

```bash
steamcmd +login anonymous +app_update 380870 validate +quit
# pre-release players? add: -beta pre-release
```

The version the server reports in its query reply is the quickest way to
see which build it runs; compare it with the game's current build after
every patch.

## Checking it from outside

To see the server the way the list does, query `DefaultPort` from another
network, for example with [python-a2s](https://github.com/Yepoleb/python-a2s):

```python
import a2s
info = a2s.info(("203.0.113.10", 16261), timeout=5)
print(info.server_name, f"{info.player_count}/{info.max_players}", info.version)
```

| Result | Meaning |
| --- | --- |
| A reply with your name and player count | The server is up and queryable. If it's not in the list, it's `Public`, Steam mode or the list's filters. |
| Timeout | Nothing answered on UDP 16261 from where you are: the server isn't up yet, the port isn't forwarded, or a firewall filters it. |
| A reply with an old version | The server needs updating, or is on a different branch from your players. |

Steam's `GetServersAtAddress` API
(`https://api.steampowered.com/ISteamApps/GetServersAtAddress/v1/?addr=<your-ip>`)
also tells you whether Steam has your server registered at all; appid 108600
is Project Zomboid.

## Restarts and mod updates

Most servers restart on a schedule to apply Workshop updates and clear
memory. That's healthy, as long as it's predictable:

- Pick fixed times and announce them.
- Expect the restart to take as long as the mod download, not just the
  reboot.
- Tell your monitoring about them (next section), so a planned restart
  doesn't wake anyone.

## Watching the server from outside

A WatchFor **Game server** monitor with the **Project Zomboid** preset
queries your server on `DefaultPort` (16261) over UDP, from the regions you
pick, and records the server name, survivors online out of `MaxPlayers`,
the build version and the latency on every check.

The monitor page has the same layout for every game. This one is from our
demo organization and happens to watch a Rust server:

![A WatchFor game server monitor (a Rust server in the Acme demo organization): uptime since creation, incidents in the last 24 hours, and the server card with players out of slots, latency, map, version and a Connect button, above the population chart.](/marketing/game/overview.webp)

- **A slow start isn't an outage.** A failed check is repeated before an
  incident opens, from the monitor's other locations when it has several
  (how many depends on your plan). For planned restarts with long mod
  downloads, a recurring [maintenance window](/docs/monitors/maintenance)
  keeps alerts quiet and the uptime honest.
- **A version on the card.** After a game update, a server still on the old
  build shows it at a glance.
- **Discord without a bot**: a channel webhook gets "offline" with the last
  player count, then "back online" with how long it was down. Slack,
  Telegram, Teams and email work the same way.
- **A status page** for your community with the server's state, uptime and
  the address to join. Player names never appear on it.

It reads the public Steam query only; your RCON password stays on the
server. A server in `-nosteam` mode can still be watched for reachability
with a [UDP monitor](/udp-monitoring) on the game port. Game server
monitoring is part of the paid plans from Starter, counted toward the
plan's normal monitor total ([pricing](/pricing)). The
[Project Zomboid page](/game-server-monitoring/project-zomboid) lists the
ports and what the monitor reads.

## Checklist

1. `Public=true`, Steam mode on.
2. Forward UDP 16261 **and** 16262.
3. Give status tools `your-ip:16261`, the same address players use.
4. Wait for mods to finish before calling it "failed to respond".
5. Same build and branch on server and players; `legacy41` and
   `pre-release` don't mix with the default branch.
6. Fixed restart times, known to your monitor.

## Frequently asked questions

### What ports does a Project Zomboid dedicated server need?

UDP 16261 (`DefaultPort`) and UDP 16262 (`UDPPort`), both set in your server's .ini file. Forward both. The Steam server query, which the in-game list, trackers and monitors use, answers on `DefaultPort`.

### Why does my Project Zomboid server say 'failed to respond'?

Most often the server is still starting (downloading or loading Workshop mods), the ports aren't forwarded over UDP, or the client and server are on different builds. Wait for the server log to show it's ready, check UDP 16261 and 16262, and make sure players are on the same Steam branch as the server.

### Why can't players join after a Project Zomboid update?

Client and server must run the same build. When Steam updates the game, update the server too, and check branches: since October 2026 testing builds ship on a 'pre-release' branch, and players on it can't join a server on the default branch, or the other way round.

### Is Build 42 multiplayer stable?

Yes. Multiplayer came to the Build 42 unstable branch in December 2025, and Build 42 became the stable default on July 29, 2026 (42.20). Build 41 remains available as the `legacy41` branch.

### Can I get a Discord alert when my Project Zomboid server goes down?

Yes, with an outside monitor that queries the server on DefaultPort and posts to a Discord channel webhook once the outage is confirmed. Nothing needs to be installed on the server and no RCON password is involved.

---

Canonical page: https://watchfor.io/blog/project-zomboid-server-not-showing-up · All articles: https://watchfor.io/blog/all.md · Site guide: https://watchfor.io/llms.txt
