Choose the right hosting model
| Setup | Best for | Host requirements | Important limitation |
|---|---|---|---|
| Open to LAN | Players on the same local network | Host keeps the single-player world open | Not designed for remote players |
| Open to Internet | Small temporary remote session | Host keeps the world open; UPnP or manual networking may be needed | Availability ends when the host leaves the world |
| Dedicated self-hosted server | Persistent private or public world | Windows or Linux host, server process, firewall/router configuration | Administrator maintains updates, backups, security, and uptime |
| Paid hosting | Persistent world without maintaining local hardware | Subscription and host control panel | Features, mod support, and backup access vary by provider |
The official self-hosting page presents all four paths and provides conservative hardware guidance. Actual needs vary with world size, mods, view distance, and concurrent activity.
Start a local multiplayer world
- Load the single-player world that will become the session host.
- Open the pause menu and choose Open to LAN.
- Share the displayed local address with players on the same network.
- Keep the world open. Closing it ends the hosted session.
This is the simplest option for people in the same home or building. If another device on the local network cannot connect, check that the operating-system firewall allows Vintage Story and that both devices are actually on the same network.
Allow remote players
After opening a world to LAN, the host can choose Open to Internet. The game attempts to create a route through the router using UPnP. If that fails, use manual port forwarding or a trusted virtual private network arrangement.
For manual hosting, the official multiplayer documentation uses port 42420. Configure the router and host firewall for both TCP and UDP as required. Send remote players the public address, not a private address such as 192.168.x.x. Do not expose unrelated services or broad firewall ranges merely to make the game reachable.
Set up a dedicated server
Windows outline
The Windows installation includes VintagestoryServer.exe. Use a separate --dataPath so server saves, mods, logs, and configuration do not collide with client data. Allow the server executable through the firewall and forward port 42420 when required.
Linux outline
- Copy the current Linux server-only archive link from the Account Manager.
- Download and extract it into a dedicated server directory.
- Run it under a separate non-root user.
- Configure
server.sh, the data path, and firewall rules for TCP and UDP port 42420. - Start the server, apply the whitelist if used, and grant administrator rights only to trusted accounts.
The official dedicated-server guide currently requires .NET 8.0 for its Linux x64 setup. Recheck that guide when changing major game versions because runtime and package requirements can change.
Configuration and security baseline
Stop the server before directly editing serverconfig.json. Commands can set its name, password, UPnP behavior, and public-list visibility.
| Task | Recommended practice |
|---|---|
| Private world | Set a password or whitelist and keep public advertising disabled |
| Administrator access | Use /op playername only for trusted game accounts |
| World protection | Keep scheduled backups outside the active data path and test restoration |
| Server process | Use a dedicated, non-root OS account on Linux |
| Updates | Stop the server, back up data, then replace program files without deleting the separate data path |
| Mods | Change the mod set while offline and confirm game/mod compatibility before reopening |
| Firewall | Permit the specific application or port needed; avoid unnecessarily broad rules |
Version 1.22.5 server note
The July 20, 2026 official announcement calls v1.22.4/5 a stable server-safety patch. It fixes several interactions that did not correctly check player or land-claim permissions, along with other server and gameplay issues. The post was then edited to announce v1.22.5 because v1.22.4 prevented players from trading with traders.
For a current server, update directly to 1.22.5 rather than stopping at 1.22.4. Verify future releases against the official news page and Account Manager.
Modded multiplayer
Place server mods in the Mods directory configured for the server’s data path, and restart after changes. Modern clients can automatically maintain server-specific mod sets under ModsByServer for server-side or universal mods offered by the host. Client-only mods may require manual action.
Keep a manifest with exact versions. When errors appear, compare the server manifest, game version, dependencies, and cached ModsByServer copy. Back up before changing content mods.
Troubleshooting connections
| Symptom | Likely area to inspect |
|---|---|
| Local players cannot connect | Host firewall, wrong local address, different networks, server process not running |
| Remote host does not respond | Port forwarding, public address, changed host IP, TCP/UDP rules |
| Connection actively refused | Firewall rule or server not listening on the expected port |
| Version mismatch | Client and server are not both on 1.22.5 or the same intended older build |
| Mod download or join failure | Missing dependency, incompatible mod file, stale ModsByServer cache |
| Periodic stalls | Server resource pressure, autosaves, storage speed, or a problematic mod |
Test in layers: confirm the server starts locally, connect from another device on the LAN, and only then troubleshoot public internet access. This separates game configuration from router and firewall problems.
Frequently asked questions
Can macOS players join a Windows or Linux server?
Yes. Vintage Story supports Windows, macOS, and Linux clients. Game and mod compatibility matter more than matching the host operating system.
Does a dedicated server need SteamCMD?
No. Vintage Story is not on Steam. Obtain the current server files through the official Account Manager.
Should I expose my private server publicly?
No. Keep advertising disabled and use a password or whitelist unless you intentionally operate a public community server.
Related Guides
Public Sources
- Official self-hosting overview
- Community-maintained wiki, officially hosted: Setting up a Multiplayer Server
- Community-maintained wiki, officially hosted: Dedicated Server
- Community-maintained wiki, officially hosted: Troubleshooting multiplayer
- v1.22.4/5 server safety patch announcement
- Vintage Story Account Manager