Troubleshooting Windrose Server Crashes
Windrose is in Early Access. Occasional crashes happen, especially on patch days or with a full crew. Repeated crashes in a short window usually mean not enough RAM, a version mismatch, a bad save, or a mod.
Work the steps in order.
1. Take a Backup
Section titled “1. Take a Backup”Stop the server and create a backup before you change files or restore anything.
2. Read the Console
Section titled “2. Read the Console”- Open the AleForge Panel
- Open
Console - Scroll to the lines just before each crash. Look for
Error,Crash,Out of memory, or a repeating exception
The same string on every crash is your starting clue. Copy the last ~50 lines for support.
3. Check RAM
Section titled “3. Check RAM”Watch the memory graph on Console during the activity that precedes the crash (boarding, a dense settlement, a full crew).
If memory pins near the plan limit, upgrade RAM. Official dedicated server guide sizing:
- 2 players: 8 GB
- 4 players: 12 GB
- Larger crews: 16 GB
4. Match the Game Patch
Section titled “4. Match the Game Patch”Crashes that start right after a Windrose update are often a stale dedicated server.
- Stop the server
- Start it so the panel can update
- Compare the version printed in
Consolewith the client and the Windrose news / patch notes
If files will not update, open Settings → Reinstall Server. Reinstall replaces binaries. Worlds in R5/Saved/ and R5/ServerDescription.json stay unless you chose a wipe. See empty files / reinstall.
5. Disable Mods
Section titled “5. Disable Mods”If you added UE4SS mods, backup, then disable new entries in mods.json (or move the folder out of ue4ss/Mods) and restart. See installing mods.
6. Restore an Earlier World
Section titled “6. Restore an Earlier World”If logs and RAM look fine, the RocksDB world may be in a bad state.
- Stop the server
- Restore a panel backup from before the crashes
- Play a session
If crashes stop, keep that restore as the live world.
Still Crashing?
Section titled “Still Crashing?”Contact support with:
- Server ID
- How often it crashes and when it started
- Last 50 lines of
Consoleat crash time - RAM plan and usual player count
- Whether it started after a Windrose patch or a mod change
Frequently Asked Questions
Section titled “Frequently Asked Questions”Is it normal for a Windrose server to crash?
Section titled “Is it normal for a Windrose server to crash?”Sometimes, during Early Access. Repeated crashes in minutes usually mean RAM, patch mismatch, mods, or a damaged save.
How do I tell if RAM is the cause?
Section titled “How do I tell if RAM is the cause?”If the memory graph sits at the cap before the process dies, add RAM. Official guidance is 16 GB for a large crew.
What should I send support?
Section titled “What should I send support?”Server ID, crash times, console excerpt, RAM plan, crew size, and whether a patch or mod change came first.