---
title: Enshrouded dedicated server ports after 1.0: queryPort, the gamePort that's gone, and staying online
description: Enshrouded 1.0 shipped on October 15, 2026, and plenty of setup guides still tell you to open two ports. Current dedicated servers have one setting that matters, queryPort, 15637 by default. Here's the config that counts, why a server doesn't show up in the list, what 'server is full or unavailable' usually means, and how to keep a 16-player world online for your group.
canonical: https://watchfor.io/blog/enshrouded-dedicated-server-ports
---

# Enshrouded dedicated server ports after 1.0: queryPort, the gamePort that's gone, and staying online

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

Enshrouded 1.0 shipped on October 15, 2026, and plenty of setup guides still tell you to open two ports. Current dedicated servers have one setting that matters, queryPort, 15637 by default. Here's the config that counts, why a server doesn't show up in the list, what 'server is full or unavailable' usually means, and how to keep a 16-player world online for your group.

Enshrouded left early access with
[1.0 on October 15, 2026](https://store.steampowered.com/news/app/1203620/view/1846651706678083),
on PC and PlayStation 5, and October's Steam peak was back above 116,000
players ([SteamCharts](https://steamcharts.com/app/1203620)). A lot of
groups set up a dedicated server for the release, many of them by following
guides written in 2024. That's where most of the trouble starts, because the
server's port settings changed after those guides were written.

This post covers the config that matters now, the reasons a server goes
missing from the list, and how to keep a 16-player world reachable.

## One port, not two

Early Enshrouded server configs had two port settings, `gamePort` (15636)
and `queryPort` (15637), and that's what most older guides and some
tools still show. With the mid-2024 content update that introduced user
groups, `gamePort` disappeared from the server config, as hosting
documentation such as
[G-Portal's](https://www.g-portal.com/wiki/en/how-do-the-new-usergroups-user-groups-for-enshrouded-server-work/)
notes. A current `enshrouded_server.json` looks like this (user group details
trimmed):

```json
{
  "name": "Our Embervale",
  "saveDirectory": "./savegame",
  "logDirectory": "./logs",
  "ip": "0.0.0.0",
  "queryPort": 15637,
  "slotCount": 16,
  "tags": [],
  "userGroups": [
    { "name": "Friends", "password": "change-me", "canKickBan": false, "...": "..." }
  ]
}
```

What each setting means for reachability:

| Setting | Default | Notes |
| --- | --- | --- |
| `queryPort` | 15637 | UDP. The port to forward, and the one the Steam server query answers on. |
| `ip` | `0.0.0.0` | Listen on all interfaces. A wrong address here means nobody outside reaches it. |
| `slotCount` | 16 | Maximum players. 16 is the cap. |
| `userGroups` | | Replaced the old single server password: each group has its own password and permissions. |

Forward **UDP 15637** (or whatever you set) on the router and allow it in
the Windows firewall. Some Docker images and hosting templates also open a
Steam port such as 27015; that does no harm, but `queryPort` is the one that
must work.

The official dedicated server is Steam app **2278520** and is Windows-only.
Hosts and community Docker images run it on Linux under Wine or Proton,
which works well in practice, but expect the occasional Wine-specific
problem after an update.

## "My server doesn't show up in the list"

In order of likelihood:

1. **The port isn't reachable over UDP.** Router forward, Windows Defender
   Firewall, and on rented servers the host's own firewall. A TCP rule does
   nothing.
2. **It's still starting.** A large world takes a while to load, especially
   on first start after an update. The server log says when it's ready.
3. **`ip` is wrong.** Leave it at `0.0.0.0` unless you know why you're
   changing it.
4. **The list's filters.** Since late 2025 servers can carry tags (looking
   for players, play style and so on), and the in-game filters hide servers
   that don't match. Search by exact name with filters cleared.

To check the server the way the list does, query the port from a different
network, for example with [python-a2s](https://github.com/Yepoleb/python-a2s):

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

A reply with your server's name and `x/16` means the query side works. A
timeout means UDP 15637 isn't reachable from where you asked.

## "Server is full or unavailable"

The message covers several different situations:

- **It really is full.** Sixteen slots go quickly when a group invites
  friends of friends. The player count in the query reply tells you.
- **Version mismatch.** After a patch, clients update through Steam or
  PlayStation automatically; your server updates only when you or your host
  run the update. Until then, nobody on the new version can join. Compare
  the version in the query reply with the game's current build.
- **The server is still starting or saving.** Big bases make long saves,
  and the server can stall for a moment while it writes.

## Keeping a world up for your group

An Enshrouded server is usually a group's shared world on a rented box,
which means two things: nobody is watching it all the time, and the first
report of a problem is a friend who can't join after dinner. A few habits
help:

- **Update deliberately.** After each Enshrouded patch, update the server
  the same day; a server one version behind is effectively down for
  everyone.
- **Restart on a schedule**, at a time nobody plays, rather than whenever
  memory runs out.
- **Back up `saveDirectory`.** A world is months of building. Copy it before
  every update.
- **Watch it from outside.** The machine can't tell you that its network
  route broke or that the host's firewall changed.

## Monitoring an Enshrouded server

A WatchFor **Game server** monitor with the **Enshrouded** preset queries
your server's `queryPort` (15637 by default) over UDP, the same question
the server list asks, from the regions you choose. Every check records the
server name, players out of 16, version and latency.

![The WatchFor Latency by region card of a game server monitor (a CS2 server in the Acme demo organization): latency from the Vilnius location with jitter and loss, above the latency chart with average, minimum and maximum.](/marketing/game/regions.webp)

- **Confirmed before anyone is told.** One lost UDP packet doesn't make 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). Long world saves don't page anyone.
- **Your group's Discord, no bot.** A channel webhook gets a message when the
  server is confirmed offline and another when it's back.
- **The version on the card.** After a patch, a server that missed the
  update shows its old version at a glance.
- **A status page** with the server's state, uptime and the address to copy,
  so nobody has to ask in chat.

Game server monitoring is part of the paid plans from Starter, counted
toward the plan's normal monitor total ([pricing](/pricing)). The
[Enshrouded page](/game-server-monitoring/enshrouded) has the details the
monitor reads.

## Checklist

1. One port: `queryPort`, 15637 by default, UDP. Ignore guides that insist on
   15636.
2. Forward it on the router, the Windows firewall and the host firewall.
3. `ip` stays `0.0.0.0`; `slotCount` up to 16.
4. Update the server on the day of every patch, after a save backup.
5. Query it from outside to see what the list sees.

## Frequently asked questions

### What ports does an Enshrouded dedicated server use?

Current servers have one port setting, `queryPort` in enshrouded_server.json, 15637 by default, over UDP. Forward that. Older guides also list a `gamePort` of 15636; that setting was removed from the server config in 2024, and some hosting templates and Docker images still open extra ports out of habit.

### Why is my Enshrouded server not showing up in the server list?

Check that queryPort is forwarded over UDP on the router and on the Windows firewall, that `ip` is 0.0.0.0 (or the machine's own address), and that the server finished starting. Then search by name with the filters cleared. Players can also join by address when the list is slow.

### Does the Enshrouded dedicated server run on Linux?

The official server (Steam app 2278520) is Windows-only. Many hosts and community Docker images run it on Linux under Wine or Proton, which works, but it's not an official platform.

### How many players can join an Enshrouded server?

Up to 16, set with `slotCount`. 'Server is full or unavailable' usually means every slot is taken, the client and server are on different versions after an update, or the server is still starting.

### How do I know when my Enshrouded server goes down?

Use a monitor that queries the server on its queryPort from outside and posts to your group's Discord through a webhook once the outage is confirmed. Nothing has to be installed on the server.

---

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