Hosting a Mordhau server from home is a good option if you want a private place to play with friends, test mods, run a duel server, or learn how dedicated servers work before paying for hosted infrastructure. Mordhau supports self-hosted dedicated servers on Windows and Linux, including installs through Steam or SteamCMD. Official community documentation also notes that there is no in-game private server hosting option, so dedicated server setup is the normal path for self-hosting.
This guide is written for beginners and focuses on home hosting, not commercial hosting panels. It covers what hardware and network setup you need, how to install the server, where the config files are located, how to make the server visible to friends, and the most common reasons a server works on LAN but not over the internet.
What home hosting means for Mordhau #
When you host from home, the server runs on your own PC or on a second machine inside your home network. Your friends connect through your public IP address, and your router forwards the required ports to the PC running the server. The Mordhau community hosting guides specifically call out port forwarding and note that servers often appear only in LAN until the required ports are opened correctly.
Home hosting is best for:
- private friend groups
- testing server settings
- duel servers
- learning mods and configuration
- temporary community servers
Home hosting is usually not ideal if you want guaranteed uptime, DDoS protection, or a public server that is online all day.
Basic system and network requirements #
Your draft requirements were directionally fine, but the more important practical requirements for home hosting are:
- a 64-bit Windows or Linux system
- a modern CPU with decent single-core performance
- enough RAM to run the server and the OS comfortably
- SSD storage
- stable upload speed
- wired ethernet instead of Wi-Fi whenever possible
For a small private server with friends, a mid-range gaming PC or spare desktop is usually enough. The bigger issue is often network quality, not raw hardware. Community guides repeatedly point to port forwarding and correct public visibility as the main blockers for home hosts.
A practical home-hosting recommendation is:
- CPU: 4 modern cores or better
- RAM: 8–16 GB available to the machine
- Storage: SSD preferred
- Upload speed: at least 20 Mbps, with more being better for larger groups
- Network: wired ethernet
- Router access: required for port forwarding
Before you install the server #
Before installing anything, decide whether you are using:
- the Steam tool version of the Mordhau Dedicated Server
- SteamCMD for manual installation and updates
- WindowsGSM PC application
If you already own Mordhau on Steam, the dedicated server tool is available in the Steam Library under Tools. The Mordhau Wiki documents that approach directly. SteamCMD is also supported and uses app ID 629800.
Option 1: Install the Mordhau Dedicated Server through Steam #
This is the easiest path for most new home hosts.
- Open Steam.
- In your Library, make sure Tools is visible.
- Search for MORDHAU Dedicated Server.
- Install it.
- Launch it once so it generates the server config files.
- Shut it down after it finishes loading.
The Mordhau Wiki’s Steam setup specifically says to launch the dedicated server once so that the required config files are created. It also notes that the default client and server can conflict on ports, so you may want to use custom ports if you are hosting and playing on the same machine.
Option 2: Install Mordhau with SteamCMD #
SteamCMD is better if you want cleaner control over install paths, updates, or Linux automation.
Windows SteamCMD install #
Install SteamCMD, then use:
login anonymous
force_install_dir C:\MordhauServer
app_update 629800 validate
quit
The Mordhau Linux and SteamCMD guides both confirm app ID 629800 for the dedicated server.
Linux SteamCMD install #
A typical Linux install looks like:
sudo apt-get update
sudo apt-get install steamcmd
mkdir ~/mordhau-server
steamcmd +login anonymous +force_install_dir ~/mordhau-server +app_update 629800 validate +quit
That matches current community guidance for Linux installs.
First launch: generate the config files #
Whether you install through Steam or SteamCMD, the first thing you should do is run the server once and then stop it. This creates the configuration files you will edit next. Community hosting guides call this out directly, including the Windows install walkthrough.
Where the Mordhau config files are located #
For a self-hosted server, the important config path is inside the server install directory.
Typical Windows path:
Mordhau\Saved\Config\WindowsServer\
Typical Linux path:
Mordhau/Saved/Config/LinuxServer/
The Mordhau Wiki and community guides point to these locations for Game.ini and related server configuration.
The most important file: Game.ini #
For most home hosts, Game.ini is where the main server setup happens.
A simple example looks like this:
[/Script/Mordhau.MordhauGameSession]
MaxSlots=16
ServerName=My Home Mordhau Server
ServerPassword=
AdminPassword=ChooseAStrongAdminPassword
BannedPlayers=()
MutedPlayers=()MapRotation=ThePit
MapRotation=Contraband
MapRotation=Grad
If you are running mods, keep mod entries in this same MordhauGameSession section. The community configuration guidance and your earlier draft align on that behavior.
Choosing a starting map and launch target #
The Mordhau server is launched with a starting map and one or more port values. The official Steam setup example uses a map name first, then logging and port arguments, such as:
FFA_Contraband -log -Port=7779 -RconPort=7780 -QueryPort=27018 -Beaconport=15002
The Wiki notes that these ports should be different from the defaults if you are also running the client on the same machine, because the game client uses the same defaults.
For a simple home server, the exact map can vary, but the principle is the same: the launch line needs a valid starting map and the ports you plan to use.
Required ports for home hosting #
One of the biggest problems with Mordhau home hosting is incomplete port forwarding. Community guides consistently mention four ports that need to be opened for the server to appear correctly and allow outside players to connect:
777777782701515000
If you change the defaults, forward the custom values you actually use in your launch parameters. It is highly recommended to use ports other than the default. While home hosting and playing on the same PC the server and then client are attempting to use the same ports if you leave them at default.
A practical rule for home hosting:
- forward the game port
- forward the related secondary/service ports
- make sure the ports point to the correct internal IP of the server PC
- keep that PC on a static local IP reservation if possible
Router setup for home hosting #
To make the server visible to friends:
- Give the server PC a static local IP or DHCP reservation.
- Log into your router.
- Forward the required Mordhau ports to that PC.
- Save and reboot the router if needed.
- Make sure Windows Firewall or your Linux firewall allows the same ports.
This is the step many home hosts miss. If your server works locally but not for friends, the issue is usually router forwarding, firewall rules, or using the wrong internal IP. That pattern shows up repeatedly in community troubleshooting.
Windows firewall setup #
On Windows, create inbound allow rules for the Mordhau server executable and for the required ports. Community home-hosting guides specifically mention allowing the executable through Windows Defender Firewall for both private and public networks.
Launching the server on Windows #
A batch file is the simplest option. Example structure:
"MordhauServer.exe" FFA_Contraband -log -Port=7780 -QueryPort=27016 -Beaconport=15001
If you want to run the server on the same machine you use to play Mordhau, consider using non-default ports, as documented by the Mordhau Wiki Steam setup.
Launching the server on Linux #
A basic shell launch can look like:
./MordhauServer.sh FFA_Contraband -log -Port=7780 -QueryPort=27016 -Beaconport=15001
If you plan to run multiple servers, community discussion confirms you can assign different port values per instance.
How friends join your home-hosted server #
Once everything is working, your friends normally connect using your public IP and the correct server port, or by finding the server in the browser if it has registered properly.
If the server only appears in LAN:
- verify the ports are forwarded
- verify the firewall rules
- verify the launch ports match the forwarded ports
- verify your ISP is not blocking inbound traffic
- verify the server machine’s local IP matches the router forwarding target
These are the exact patterns seen in Mordhau community support threads.
Home hosting on the same PC you play on #
This is possible, but there are two common issues:
- port conflicts with the Mordhau game client
- performance strain when playing and hosting at once
The official Steam setup guidance explicitly warns that the dedicated server and the Mordhau client use the same default ports, so if you are hosting and playing on one machine, change the server ports.
For this reason, many home hosts either:
- use a second PC for the server
- run the server on the same PC but on custom ports
- keep the player count low
Mods on a home-hosted Mordhau server #
Mods can be used on self-hosted servers, but they add complexity. Keep the server stable first before loading mods. Once the base server works, add mods carefully and test them one at a time.
As with other Mordhau config work, make sure mod entries go in the correct Game.ini section and give the server time to download them on first startup.
Good starter settings for a small home server #
For a simple friend-group server, start small:
- 8 to 16 player slots
- one clear game mode
- a small map rotation
- strong admin password
- no mods at first
- wired network only
This makes troubleshooting much easier than trying to launch a 32–48 slot modded server on day one.
Common Mordhau home hosting problems #
Server is not joinable for me, but friends can join #
This is a known loopback bug while home hosting and playing from the same IP of the public server. To get around this you must join the server by using your local LAN IP or 127.0.0.1 and joining through the console command open 127.0.0.1?ServerPassword=yourpassword
The ?ServerPassword=yourpassword is only required if you have your server private and password protected.
Server appears in LAN but not internet #
Usually caused by missing port forwarding, wrong public IP, firewall blocks, or ISP restrictions. Community threads on this issue are very common.
Friends time out when joining #
Usually caused by forwarding the wrong ports, forwarding to the wrong internal IP, or Windows Firewall blocking the server.
Config files are missing #
Run the server once, let it fully initialize, then shut it down. That creates the config files.
Hosting and playing on the same PC causes weird issues #
Often caused by port conflicts with the client. Use custom ports for the server.
Performance tips for home hosts #
If your server feels unstable:
- use SSD storage
- close background apps
- use ethernet instead of Wi-Fi
- do not overfill player slots
- avoid heavy mods until the base server is stable
- restart after major config changes
- keep the server updated through Steam or SteamCMD
These are simple changes, but they matter more than people expect on home-hosted game servers.
A realistic expectation for new server owners #
The hard part of Mordhau home hosting is usually not installing the files. It is getting the networking right. Most first-time hosts can get the server running locally. The real challenge is making it reachable from outside the house. Once your ports, firewall, and launch parameters are correct, the rest becomes much easier.
