Enshrouded Server Ports and Addresses
Your Enshrouded server uses one UDP port for everything. What it is, why there is no second port, and what to give players adding the server to Steam.
One port, UDP
An Enshrouded server listens on one UDP port. That single port carries both the game traffic and Steam's server queries โ the ones that make your server show up in the browser and report its player count.
Your port is on the Connect card of your server's Overview: Server Address (the address and port together, with a copy button) and Game Port. GameGrid assigns it from your server's own block and writes it into the server's configuration (queryPort in enshrouded_server.json) before every start. Settings โ System shows it read-only.
| Protocol | UDP only |
| Ports used | One |
| What it carries | Game traffic and Steam queries |
| Set by | GameGrid, automatically |
| Changeable | No |
There is nothing to forward and no firewall rule to add. That is all handled.
There is no second port
You will find guides that tell you to open two ports, usually described as a game port and a query port one number apart.
That layout predates Enshrouded's own update 2 and no longer applies. The current server documents one port and listens on one port. A socket capture of a running server shows that single UDP port and nothing else inbound.
This matters in one practical place: when a player adds your server to their Steam favourites, give them the port from your panel. A favourite added with the port one lower, as the older guides say, never answers.
It is IPv4
Enshrouded's server is IPv4 only, so give players your server's IPv4 address, as the Connect card shows it.
Why you cannot change it
Each GameGrid server gets its own port so that many servers can run on one machine without colliding. Letting it be edited would let two servers fight over the same port, and the one that lost would look broken for no visible reason.
If you need a specific port for something, open a support ticket rather than editing the configuration file โ a hand-edited port is overwritten at the next start.
Checking the port is answering
The server overview shows the server as online once it is answering Steam queries on its port. If it says starting for a long time, look at the Console: Enshrouded takes a moment on a first start while it creates the world, and the log tells you where it is.
A server that is running but not answering queries is almost always still loading. See Your Enshrouded Server Won't Start.
How your player count is worked out
Worth knowing, because it explains why the panel can name your players when the game's own query cannot.
Steam's query on that one port reports how many players are on, but Enshrouded answers it with empty names โ the count is real, the names are blank. On its own that would give you "4 players" and nothing else.
So GameGrid uses three sources and prefers the best one available:
| Source | Gives |
|---|---|
| The GameGrid server module | Names, character names, Steam ids and live positions โ used whenever it is healthy |
| The server's own log | Names, from the join and leave lines |
| Steam's query on your port | The count, as the fallback |
That is why the live map can show you who is where, and why the player list has names at all. Players' IP addresses are never shown, from any of the three. See The Enshrouded World Map and The Enshrouded Console and Server Log.
What to give players
| They want to | Give them |
|---|---|
| Search the in-game browser | The server name |
| Search by address in game | The address |
| Add a Steam favourite | address:port, both from your panel |
And remind them to turn on the dedicated-server option in the game's server filter: see How to Join Your Enshrouded Server.