Most Mordhau tickets are the config file being overwritten or the browser using the wrong port.
1. Settings revert after a restart
Mordhau writes Game.ini from memory when the server shuts down. Anything typed while it is running is replaced by whatever the server had loaded.
- Stop the server and wait for the panel to report it is offline.
- Edit
Game.iniand save. - Start the server and check the console.
2. A setting is ignored
- Check it is under the correct section header. Lines above the header are skipped without an error.
- Check the spelling of the setting name.
- Values set at launch win over the file. Look at the Startup page of your server, reached by adding
/startupto the end of its panel address.
3. The server is not in the browser
- Prove the server works with
open IP:GamePortin the game console. - The browser reads the query port, which is a different number from the game port. Both are in your panel and neither should be changed in the config.
- Give a newly started server a few minutes and clear the browser filters.
4. Players cannot join
- Check
MaxSlotsand the server password. - Restart the server after a game update so it matches the clients.
- Check the ban list in
Game.iniif one specific player is refused.
5. The map rotation is not being followed
- Every map has to be listed with its own
MapRotationline and the exact map name. - A misspelled entry is skipped silently.
- Read the console when the map changes to see what it picked.
6. The server stops on its own
Read the last 50 lines of the Console. If the process was killed rather than reporting a game error, it ran out of memory, and a lower slot count or a larger plan is the fix. A scheduled nightly restart from the Schedules section keeps a busy server healthy.
Open a ticket from Support in the Client Area with the console output if none of this fits.





