Hosting an Unturned LAN server lets you run a local cooperative session for a small group without renting a public server. This guide explains the essential steps including enabling the server, configuring ports, adjusting your firewall, and testing connections from the host and client machines. You will find practical details for both Windows and macOS/Steam LAN setups, plus a quick reference table for ports and settings to reduce troubleshooting time.
Unturned LAN vs public dedicated server
An Unturned LAN server runs on your local network and is visible only to devices on the same router or switch, whereas a public dedicated server uses port forwarding and a global IP to allow connections from the broader internet. For a LAN server, you typically do not need a third-party hosting provider, you avoid monthly costs, and you rely on your home internet and machine resources. Limitations include restricted player count based on your upload bandwidth, no persistence across reboots unless configured, and no public visibility beyond your local network. Choose a LAN setup for low-latency sessions with friends or for controlled testing before publishing to a public server.
Host machine requirements
Your host computer must meet Unturned’s baseline hardware and software requirements, and you should reserve adequate network and storage resources to avoid stuttering or disconnects. Below is a concise reference table summarizing common verified details for planning your LAN deployment.
| Attribute | Verified Detail | Source Type |
|---|---|---|
| Recommended RAM | 8 GB minimum; 16 GB preferred | Unturned system requirements |
| CPU cores | Dual-core modern CPU; i3/Ryzen 3 or better | Unturned system requirements |
| Storage space | 8–10 GB available on install drive | Unturned system requirements |
| Server tick rate | Default 30 tick; can be lowered or raised in server config | Unturned server documentation |
| Max local peers (typical) | 4–8 players; depends on upload bandwidth and router performance | Observed performance guidance |
| HTTP/HTTPS ports used | TCP 80 and 443 for Steam/updates; not required for gameplay | Unturned networking overview |
| Gameplay ports (default) | TCP 28015 and UDP 28015 for query and connections | Unturned server configuration guide |
Step 1: Prepare the server machine
Before launching the server binary, verify system health, close bandwidth-heavy apps, and ensure you have the current Unturned server files. Use a stable power plan and wired Ethernet when possible to reduce latency spikes. Disable unnecessary background downloads and cloud sync that could consume upload capacity. If another device runs a bandwidth-heavy application during play, expect increased latency or timeouts on the LAN session. On Windows, prioritize Performance mode in Power Options; on macOS, ensure adequate cooling and available system memory before hosting.
Install or launch the Unturned server files
Download the dedicated server build from the official channels or Steam if supported, and place it in a clean folder without spaces in the path. Create a batch or shell script to launch the server with desired parameters, such as region, name, password, and max players. Keep a plain-text template of your server.cfg so you can quickly reset values if edits cause connection failures. Back up any existing save files before major config changes to avoid losing progress or custom zones.
Set a static local IP for the host
Assign a static IP to the server machine via your router DHCP reservation or manual network settings so the server address never shifts between sessions. Without a static IP, port forwards break after the lease expires, temporarily disabling remote LAN discovery. On most home routers, reserve an address by MAC, or configure IPv4 in your OS TCP settings and match the router subnet, gateway, and DNS. Record the assigned IP, gateway, and DNS because you will reference them during firewall and port-forwarding steps.
Step 2: Configure server settings for LAN
Unturned’s server configuration is driven by text-based config files, primarily server.cfg, where you control region, name, password, tick rate, and allowed items. For a LAN-only session, you can leave the server bound to localhost-style interfaces and rely on local IP binding rather than wide-open exposure. Set a clear server name, choose a secure admin password, and define max players to match your network capacity. Avoid enabling cheats unless all participants agree, as they alter progression and inventory behavior across the session. Below is a comparison of common configuration options to clarify behavior.
| Config Option | Common Value for LAN | Effect |
|---|---|---|
| region | Use "Automatic" or specify nearest region | Helps matchmake latency expectations and default asset bundles |
| password | Set a strong admin password | Protects server console and admin commands |
| maxplayers | 4–8 depending on bandwidth | players|
| tickrate | 30 (default) | Higher tickrates increase CPU/network load |
| authentication | default (Steam) or local for offline tests | Controls login and anti-cheat expectations |
| bind address | 0.0.0.0 (all interfaces) or local subnet IP | Determines who can reach the server socket |
Edit server.cfg safely
Open server.cfg in a plain-text editor, make incremental changes, and save a copy of the previous version. After saving, restart the server process so the new settings take effect. If the server fails to start, review the console log for specific errors such as invalid syntax, reserved keywords, or mismatched authentication settings. Use simple comments in the config by preceding lines with double slashes to document intent without breaking parsing. When testing, change one variable at a time to isolate the cause of failures.
Step 3: Configure firewall and port forwarding
Windows Defender, third-party antivirus, and macOS firewall may block incoming connections to the server executable. Create an inbound rule to allow UnturnedServer.exe (or the server binary) through the firewall and explicitly allow UDP 28015 and TCP 28015. On consumer routers, set up port forwarding or DMZ rules only if you intend to expose the server beyond the local LAN; many LAN-only sessions work with firewall adjustments alone and without WAN ports forwarded. For IPv6 deployments within the LAN, ensure both firewall and router handle IPv6 traffic explicitly to avoid silently dropped packets. When testing connectivity, use local IPs first; only add WAN-side forwarding if you later decide to open the session to remote players.
Windows firewall example steps
- Open Control Panel → System and Security → Windows Defender Firewall → Advanced Settings.
- Right-click Inbound Rules → New Rule → Port → UDP 28015.
- Allow the connection, apply to Domain/Private, and name the rule "Unturned LAN Server".
- Repeat for TCP 28015 if your server config requires query or admin tools over TCP.
Mac and router considerations
On macOS, add Unturned to the list of allowed applications in System Settings → Privacy & Security → Firewall. On routers, avoid unnecessary exposure by keeping WAN-side ports closed unless cross-network play is required. If you use ISP-grade CGNAT or strict carrier-grade NAT, some inbound behaviors may vary; in those cases, focus on local IP communication and skip external port mapping. When using a mesh network or Wi‑Fi extenders, ensure the host and clients are on the same subnet to prevent discovery failures.
Step 4: Test the connection locally
Start the server on the host, open Unturned on the same machine, and connect using 127.0.0.1 or localhost to confirm the server appears in the server list and joins succeed. Once the local test passes, have another device on the same Wi‑Fi or wired network connect using the host’s local IP address, such as 192.168.1.10. If clients time out, verify the firewall allows UDP 28015, confirm the host IP is static, and check the server logs for binding errors. Use command-line tools like ping and arping to validate IP reachability, and use netstat or lsof to confirm the server is actively listening on the expected ports.
Quick troubleshooting checklist
- Server process is running and not minimized.
- Firewall permits Inbound UDP 28015 (and TCP if used).
- Host IP is static and documented on the LAN.
- Clients use the correct local IP and port.
- No other service (e.g., another game server) is occupying the same ports.
Step 5: Invite client devices
On client machines, use the host’s local IP and the configured port in the server browser or connect via direct IP if the server does not appear in the list. Ensure clients run a compatible Unturned build and, if you set a password, enter it before joining. For consistent performance, ask clients to connect via Ethernet when possible and to pause bandwidth-heavy downloads. If you expand beyond the local subnet later, re-evaluate NAT traversal and consider a VPN or dedicated server instead of relying on port forwarding at home.
Common pitfalls and fixes
- Server visible locally but not on client devices: Verify firewall rules on the host and confirm clients use the correct IP and port.
- High latency or rubber-banding: Limit simultaneous players or upgrade the host’s network; check for background uploads.
- Server fails to bind to port: Ensure no other application holds TCP/UDP 28015 and restart the server with admin privileges if required.
- Authentication or version mismatch: Align server and client builds and avoid enabling authentication modes that mismatch client expectations.
By following these steps you can reliably host an Unturned LAN server for small groups, run tests, or experiment with scenarios before moving to a public server. Maintain consistency between server configs and client builds, monitor available bandwidth, and keep backups of your server.cfg and save data to simplify recovery from crashes or misconfigurations.