ASTRONEER's distinctive low-poly space exploration, planetary core drilling, and automated orbital logistics make it popular for multiplayer sessions. A self-hosted ASTRONEER Dedicated Server lets multiple players explore different planets independently, runs world physics separately from individual clients, and keeps large automated bases operating continuously. This article provides deployment and configuration standards for production servers.
1. Hardware and network baseline
| Configuration | Minimum requirement | Recommended production configuration |
|---|---|---|
| CPU architecture | 4 cores / above 2.8 GHz | 8 cores / high clock speed of 3.6 GHz+ (for automation across multiple planets) |
| Physical RAM | 8 GB physical RAM | 16 GB+ physical RAM (allowing for planetary terrain meshes and rail logistics calculations) |
| Storage | 15 GB reserved space | Fast NVMe SSD (frequent terrain deformation and save reads/writes are critical) |
| Network | 10 Mbps upload bandwidth | 30 Mbps+ upload (for multiple players traveling between distant planets) |
2. Deploy the server with SteamCMD
The ASTRONEER server supports anonymous downloads through SteamCMD:
- Server AppID:
728470 - Main executable:
AstroServer.exe
# Download/update the ASTRONEER dedicated server anonymously
steamcmd +login anonymous +app_update 728470 validate +quit
The first run of AstroServer.exe generates the complete Unreal Engine configuration in Astro/Saved/Config/WindowsServer/.
3. Network and firewall port matrix
The ASTRONEER dedicated server uses two core ports:
| Port | Transport protocol | Purpose | Forwarding and firewall policy |
|---|---|---|---|
| 8777 | UDP | Core game communication and world state synchronization | Core port; allow it in the host firewall and forward it through the router for public access |
| 1234 | TCP | Local management console (ConsolePort) | Local administration only; binds to 127.0.0.1 by default; never forward directly to the internet |
Allow the port in Windows PowerShell:
New-NetFirewallRule -DisplayName "ASTRONEER Dedicated Server" -Direction Inbound -LocalPort 8777 -Protocol UDP -Action Allow
4. Key configuration: AstroServerSettings.ini
The file is located at Astro/Saved/Config/WindowsServer/AstroServerSettings.ini. The following settings are recommended for production:
[/Script/Astro.AstroServerSettings]
; Publicly displayed server name
ServerName=MyLanGameAstroServer
; Password required to join (leave empty for public access without a password)
ServerPassword=
; Dedicated management console password (for local/remote administration commands)
PublicIP=
Port=8777
ConsolePort=1234
; Maximum simultaneous players (4~8 recommended)
MaxPlayers=8
; Automatic save interval (minutes)
AutoSaveGameInterval=15
; Allow Creative Mode (must be False for Survival Mode)
bIsCreativeMode=False
5. Open-source LGSM management
Manual ASTRONEER maintenance often involves growing world saves (Astro/Saved/SaveGames/) and console password configuration. We recommend the official open-source LanGame Server Manager (LGSM) (repository: GitHub - SZSLGJCOM/LanGame-Server-Manager).
- Download preset templates in seconds: LGSM's built-in ASTRONEER hosting module downloads the
728470core files and generates a validAstroServerSettings.iniautomatically. - Smart adapter binding: Avoids port conflicts and writes the listening IP according to the network adapter topology.
- Frequent automatic snapshots: Schedule full backups of
SaveGamesto protect saves against interplanetary train deadlocks or unexpected terrain collapse.
6. Remote networking and troubleshooting
- Public direct connection: After forwarding
UDP 8777on the router, teammates can addpublic IP:8777under "Dedicated Servers" in the main menu to join. - Networking without a public IP: For rented accommodation or campus networks, use the LINK virtual LAN feature in LanGame OS Orbit to establish an encrypted P2P tunnel, then connect with the virtual adapter IP for interplanetary exploration.