Mordhau Server Not Showing in Server Browser (Fixes)
Mordhau server missing from the browser or players cannot join? Fix query and beacon ports, patch mismatches, filters, mods and Game.ini resets.
Updated Oct 7, 2026 · 5 min read
On this page
- The three ports Mordhau needs
- Cause 1: Version mismatch after a patch
- Cause 2: Query or beacon port blocked
- Cause 3: Browser filters and search
- Cause 4: The server is not using your Game.ini
- Cause 5: Players see it but cannot join
- Testing with open
- Cause 6: Console players
- Keep it listed without the port work
- FAQ
If your Mordhau server does not appear in the in game Server Browser, the usual causes are a blocked query port (UDP 27015) or beacon port (UDP 15000), the server running an older build than players after a patch, or browser filters hiding it. If players can see it but not join, check the game port (UDP 7777), the password, and whether a mod or mod map is failing to download. You can always test the connection directly from the console with open ip:7777.
The three ports Mordhau needs
| Port | Default | Protocol | Role | Symptom when blocked |
|---|---|---|---|---|
| Game | 7777 |
UDP | Gameplay | Join fails or times out |
| Query | 27015 |
UDP | Server browser listing | Server missing from the list |
| Beacon | 15000 |
UDP | Connection handshake | Joining hangs or fails |
They are set on the launch line with -Port=, -QueryPort= and -BeaconPort=. Forward all three and allow the server through the firewall. If you run several servers on one machine, every port in every set must be different.
Cause 1: Version mismatch after a patch
When Triternion patches Mordhau, players update through Steam or Epic straight away. Your server keeps the old build until it is updated, and a server on a different build drops out of the browser for updated players. Update it with SteamCMD:
steamcmd +force_install_dir C:\MordhauServer +login anonymous +app_update 629800 validate +quit
Then restart. If the server vanished on a day the game patched, this is nearly always the answer.

Cause 2: Query or beacon port blocked
A server with the query port blocked runs perfectly, and players can even join with open, but it never appears in the list. Forward UDP 27015 (or your QueryPort) and check:
- The launch line actually uses the port you forwarded. Copying a launch line from another guide can leave a different port in place.
- No other program on the machine uses the same port. A second game server with Steam query on
27015is a common clash. - Your router's WAN IP matches your public IP. If not, you are behind CGNAT and forwarding will not work. See how to host a game server without port forwarding.
Cause 3: Browser filters and search
The Mordhau Server Browser filters by things like mode, region, ping and whether servers are full, empty, passworded or modded. A new empty server is easy to filter out.
- Reset filters.
- Show empty and password protected servers.
- Search by your exact
ServerName. - Check the ping limit if the server is in another region.
If it appears with filters cleared, the server is fine.
Cause 4: The server is not using your Game.ini
If you see your server, but with the default name or no password, it is not reading the config you edited.
- Edited while running. Mordhau writes
Game.iniback to disk on shutdown, overwriting changes made while it runs. Stop the server, edit, start. - Wrong folder. The Windows server uses
Mordhau/Saved/Config/WindowsServer/Game.ini, the Linux server usesMordhau/Saved/Config/LinuxServer/Game.ini. Editing the other one does nothing.
Cause 5: Players see it but cannot join
| What happens | Likely cause | Fix |
|---|---|---|
| Join times out | Game or beacon port blocked | Forward UDP 7777 and 15000 |
| Password rejected | ServerPassword differs |
Check Game.ini, restart |
| Stuck downloading or kicked on join | A mod.io mod fails to download | Remove the newest Mods= line, retest |
| Map fails to load | Mod map not loaded, or wrong name | Make sure the mod is in Mods=; check MapRotation= names |
| Server shows full when it is not | MaxSlots lower than you think |
Check the launch line and Game.ini |
Mods come from mod.io and players download them on join. If a mod was removed or broke after a patch, joins can fail for everyone. The Mordhau mods guide shows the Mods= format and the default map gotcha with mod maps.
Testing with open
Open the console with the backtick key and type:
open 203.0.113.10:7777
with your server's IP and game port. If that connects, networking for gameplay works, and a missing browser listing comes down to the query port or the patch level. If open also fails, focus on the game and beacon ports.
Cause 6: Console players
Mordhau added crossplay with PlayStation and Xbox in 2024, but it is built around the game's official servers. Community servers are in practice a PC crowd, Steam and Epic together. If a console friend cannot find your server, that is expected.

Keep it listed without the port work
A GamezServers Mordhau server comes with its own address and its game, query and beacon ports open, and Auto Update brings it to the latest build on each start, so after a patch a panel restart puts it back in the list. Server Name, Server Password, Admin Password, Max Players and Default Map are in the control panel, Game.ini is in the file manager, and the live console shows the startup log. Getting started? See how to host a Mordhau server, and for running it, Mordhau admin commands.
FAQ
Why is my Mordhau server not in the server browser?
The query port (UDP 27015) is usually blocked, or the server is on an older version after a game update.
What ports does a Mordhau server need?
UDP 7777 (game), 27015 (query) and 15000 (beacon) by default.
How do I join a Mordhau server by IP?
Open the console with the backtick key and type open followed by the IP and game port.
Why do my Game.ini changes keep resetting?
The server rewrites Game.ini when it shuts down. Stop it before editing.
Skip the setup. Your own Mordhau server.
Then $9.99/mo. Just trying it? $2.50 for 3 days