---
title: 7 Days to Die dedicated server ports, 'server not showing up', and staying up for horde night
description: Since 1.0 in 2024, 7 Days to Die has moved through V2.0 with dedicated-server crossplay and V3.0 in 2026, and the server questions stay the same: which ports, why isn't it in the list, and why can't the console players see it. Here's what serverconfig.xml actually controls, the ports to forward, what to keep closed, and how to make sure the server is up before the blood moon rises.
canonical: https://watchfor.io/blog/7-days-to-die-dedicated-server-ports
---

# 7 Days to Die dedicated server ports, 'server not showing up', and staying up for horde night

2026-11-16 · WatchFor Team · Game servers · game-servers, 7-days-to-die, networking

Since 1.0 in 2024, 7 Days to Die has moved through V2.0 with dedicated-server crossplay and V3.0 in 2026, and the server questions stay the same: which ports, why isn't it in the list, and why can't the console players see it. Here's what serverconfig.xml actually controls, the ports to forward, what to keep closed, and how to make sure the server is up before the blood moon rises.

Horde night is the one evening your players will not forgive a dead server.
Everyone has spent a week building, the blood moon is at 22:00, and the
server is in the middle of an update nobody asked for, or behind a port
nobody forwarded.

7 Days to Die has changed a lot since its
[1.0 release on July 25, 2024](https://store.steampowered.com/app/251570/):
V2.0 "Storm's Brewing" brought crossplay to dedicated servers in June 2025,
V3.0 followed in June 2026, and V3.4 is the current stable branch. The
server's basics haven't moved much. This post covers the settings that
decide whether people can find and reach your server, the ports to open and
the ones to keep closed, and how to know it's up before the horde arrives.

## serverconfig.xml: the settings that decide visibility

The dedicated server (Steam app 294420, Windows and Linux) reads
`serverconfig.xml`. The lines that matter for being found and reached, with
their shipped defaults:

```xml
<property name="ServerName"              value="Navezgane Survivors" />
<property name="ServerPort"              value="26900" />
<property name="ServerVisibility"        value="2" />     <!-- 2 public, 1 friends, 0 unlisted -->
<property name="ServerMaxPlayerCount"    value="8" />
<property name="EACEnabled"              value="true" />
<property name="TelnetEnabled"           value="true" />
<property name="TelnetPort"              value="8081" />
<property name="TelnetPassword"          value="" />
<property name="WebDashboardEnabled"     value="false" />
<property name="WebDashboardPort"        value="8080" />
<property name="BloodMoonFrequency"      value="7" />
```

Two of these trip people up:

- **`ServerVisibility` 1 is a trap.** The shipped comment says it plainly:
  "friends only" doesn't work for a dedicated server, because you're never
  friends with it, so the server only shows once someone has connected by
  IP. Use **2** for a public server, **0** if you deliberately want it
  unlisted.
- **`ServerMaxPlayerCount` 8 is the shipped default.** Raise it if your
  community is bigger, and expect performance to change with it.

## Ports: what to open, what to keep closed

| Port | Protocol | Open to the internet? | Used for |
| --- | --- | --- | --- |
| 26900 (`ServerPort`) | TCP + UDP | Yes | Players connecting, and the Steam server query |
| 26901–26903 | UDP | Yes | Game traffic |
| 8081 (`TelnetPort`) | TCP | **No** | Admin console |
| 8080 (`WebDashboardPort`) | TCP | Only if you use it, behind auth | Web dashboard |

Guides disagree on exactly how many UDP ports after 26900 are needed;
forwarding 26900–26903 covers all the common answers. If you run a second
server on the same machine, move its `ServerPort` far enough that the ranges
don't overlap (27000, 26910 and similar are common at hosts).

**Telnet is on by default**, and that's fine as shipped: with no
`TelnetPassword`, the server only listens for Telnet on the loopback
interface. If you set a password to use it remotely, it becomes a full
admin console on the internet; firewall it to your own address. Nothing
about monitoring requires Telnet.

## "Server not showing up"

Work through it in this order:

1. **Visibility is 2**, and the server log shows it registered.
2. **Ports forwarded**, TCP and UDP on 26900, UDP on the next three, on the
   router and the host firewall.
3. **The world is ready.** A fresh random world can take a long time to
   generate on first start. Until it's done, the server isn't listed.
4. **Version.** The browser hides or rejects servers on a different build
   from the client. After a game update, update the server the same day.
5. **Console players.** Crossplay arrived for dedicated servers with V2.0,
   with requirements of its own; a modded server or one with EasyAntiCheat
   off stays PC-only. "Not showing up on PS5/Xbox" is usually this, not the
   network.

To see the server the way the browser does, query it from another network.
Steam's server query answers on the game port; for example with
[python-a2s](https://github.com/Yepoleb/python-a2s):

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

The `map_name` is the world: Navezgane, or the name of a generated world. A
reply means the server is reachable and listed with Steam; a timeout means
UDP 26900 isn't reachable from where you asked, or the server isn't up.
(Some query tools try 26901; on the servers we checked, the query answered
on the game port itself.)

Player names won't come back: 7 Days to Die shares them only with tools that
log in over Telnet. The count is exact without them.

## Horde night without surprises

The blood moon comes every `BloodMoonFrequency` days (7 by default), and
it's the peak of your server's week: the most players, the most zombies,
the most load. A few habits:

- **Restart before, not during.** Schedule the daily restart for the
  morning, and never in the two hours before the blood moon.
- **Don't update on horde day.** Take updates the day after, when a broken
  mod costs you a quiet evening instead of the big one.
- **Watch the save.** Large worlds stall briefly while saving. If that
  trips a latency alert, raise its threshold rather than muting the offline
  alert.
- **Know it's up an hour before.** That's the job of a check from outside.

## Monitoring a 7 Days to Die server

A WatchFor **Game server** monitor with the **7 Days to Die** preset
queries your server on `ServerPort` (26900 by default) over UDP, from the
regions you choose. Each check records the world name, players out of the
slots, the version and the latency.

![WatchFor game server monitor for a 7 Days to Die PvE server: players out of the slots, the world name, the game version and the latency.](/marketing/game/7dtd.webp)

- **Confirmed outages only.** 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), so a server that hitches during a save doesn't page
  you.
- **Alerts to Discord without a bot**: a channel webhook gets "offline" with
  the last player count and "back online" with the downtime. Slack, Telegram,
  Teams and email work the same way.
- **Version on the card**, so a server left behind after an update is
  visible before horde night.
- **Busy hours.** A weekday-by-hour heatmap of players, in your own time
  zone, for picking restart and update times.
- **A status page** with the server's state, uptime and players for your
  community.

It doesn't need Telnet or the web dashboard; keep both closed. Game server
monitoring is part of the paid plans from Starter, counted toward the plan's
normal monitor total ([pricing](/pricing)). The
[7 Days to Die page](/game-server-monitoring/7-days-to-die) has the port
table and what the monitor reads.

## Checklist

1. `ServerVisibility` 2, `ServerPort` known.
2. Forward 26900 TCP/UDP and 26900–26903 UDP.
3. Telnet stays on loopback (no password) or firewalled; the dashboard off
   or behind auth.
4. Update the server the day the game updates, never on horde day.
5. Query it from outside on the game port to see what the browser sees.

## Frequently asked questions

### What ports does a 7 Days to Die dedicated server use?

`ServerPort` from serverconfig.xml, 26900 by default, over TCP and UDP, plus the next few UDP ports (26901–26903) for game traffic. Forward 26900 TCP/UDP and 26900–26903 UDP. Telnet (8081) and the web dashboard (8080) don't need to be reachable from the internet.

### Why is my 7 Days to Die server not showing up in the server browser?

Check `ServerVisibility` (2 = public; 1 only shows to friends, and nobody is friends with a dedicated server), the port forwards, and that the server finished generating or loading its world. Then compare versions: a server on an older build than the players is filtered out or refuses them.

### Why can't PS5 or Xbox players see my 7 Days to Die server?

Crossplay for dedicated servers arrived with V2.0 in June 2025, and crossplay servers have requirements of their own (EasyAntiCheat on, unmodded, version-matched). A modded or EAC-off server stays PC-only. Check your version's release notes for the current rules.

### Is it safe to leave Telnet enabled on a 7 Days to Die server?

Telnet is enabled by default on port 8081. With no `TelnetPassword` set, the server only listens for Telnet on the loopback interface, which is the safe default. If you set a password to use it remotely, firewall the port to the addresses that need it; it's a full admin console.

### Can a monitor see player names on a 7 Days to Die server?

Not from the public query: 7 Days to Die only shares player names with tools that log in over Telnet. The public Steam query gives an exact player count, the world name and the version, which is what uptime monitoring needs.

---

Canonical page: https://watchfor.io/blog/7-days-to-die-dedicated-server-ports · All articles: https://watchfor.io/blog/all.md · Site guide: https://watchfor.io/llms.txt
