Virtual Machine
UnknownVM failed to start — usually not enough free RAM on this PC. Lower memory and retry.
Battlegroup
UnknownWaiting for status...
SSH Key Problem
The manager cannot authenticate to the VM. Battlegroup commands will fail until this is fixed.
If you start the manager from WSL, prefer start_as_admin.bat on Windows after a reboot. You can also go to Settings → Rotate SSH Key while the VM is running.
Battlegroup setup incomplete
The VM exists but the battlegroup was never fully installed (empty namespace). Enter your server token and run repair — this deletes the empty namespace and re-runs bootstrap.
Quick Links
Initial Server Setup
Step 1 of 6Pre-flight Checks
Verifying your system is ready for the Dune: Awakening server.
A Dune server VM is already on this machine. Delete everything and run setup again from scratch.
- Hyper-V VM
dune-awakening DuneAwakeningServerfolders on all drives- SSH keys and saved VM credentials
- All in-VM battlegroup data (world, characters, configs)
This cannot be undone. Export a database backup first if you need your world data.
VM Configuration
Choose where to install and how much resources to allocate.
Installing
Importing VM, configuring network and memory, starting the virtual machine. This can take several minutes.
VM imported but failed to start — most likely not enough RAM. Reduce the memory and retry.
Security
This will generate an SSH key, install it on the VM, and change the default password — all in one step.
Player Connectivity
Choose how the VM gets its IP and which IP players will connect to.
Finalize
Configure your world, then upload bootstrap files and run the first-time battlegroup setup. This is the final step.
Battlegroup Controls
Manage the lifecycle of your battlegroup. Start, stop, or restart game servers, and check for updates.
Swap Memory
Enable experimental swap memory to significantly reduce RAM requirements per game server. Recommended if VM has less than 20GB allocated.
Web Interfaces
Access the built-in web tools running inside the VM.
Log Export
Download logs from all battlegroup components or operator pods.
Database Management
Back up or restore the battlegroup database. For best results, stop the battlegroup before performing these operations.
Select Character
Game Configuration
Change VM Password
Change the dune user password on the VM.
SSH Key
Generate a new SSH key pair and install it on the VM, replacing the current one.
Experimental Features
Warning: Features on this tab are untested and may break your battlegroup. Always take a database backup before making changes. Use at your own risk.
Multi-Sietch
Add additional sietches (Hagga Basin instances) to your battlegroup. All sietches share the same Overmap, Deep Desert, Arrakeen, Harkonnen Village, and instanced content (dungeons, story missions). Players from different sietches will see each other in shared areas but not in their respective Hagga Basin maps.
- Each sietch requires approximately 12 GB RAM
- Overmap + infrastructure (DB, RabbitMQ, K8s) uses ~6 GB
- 1 sietch: ~18 GB minimum (current default)
- 2 sietches: ~30 GB minimum
- 3 sietches: ~42 GB minimum
Port Forwarding
Each additional sietch adds one game server pod using host networking. Game ports auto-assign starting at UDP 7777. For N sietches you need ports 7777–7778+N (UDP) forwarded, plus the corresponding beacon ports. When in doubt, forward the full range 7777–7900 UDP.