Troubleshooting Common Windrose Server Issues

Overview

Running a Windows-based Unreal Engine dedicated server in a containerized Linux environment can occasionally encounter Wine initialization errors, save corruptions, or networking dropouts. Diagnosing issues methodically using DustBowl Warden console logs minimizes server downtime.

This guide outlines standard error signatures and their resolutions.

Common Error Signatures and Solutions

1. Server Exits with Code 137 (Out of Memory)

• Log Signature: The server stops abruptly and Warden prints Process terminated with exit code 137.
• Cause: The server exhausted its container RAM quota. Windrose requires at least 8 GB RAM to initialize and up to 16 GB during intense multi-player exploration.
• Resolution:
  1. Increase memory allocation in your DustBowl Warden dashboard.
  2. Clear temporary caches in /home/container/Windrose/Saved/Logs/.
  3. Schedule daily automated restarts to clear memory fragmentation.

2. Connection Timed Out / Server Not Found

• Log Signature: Connecting players report infinite loading screens or Failed to connect to host.
• Cause: Port 7777 UDP is blocked, or the domain is configured with Cloudflare HTTP Proxying (orange cloud).
• Resolution:
  1. Ensure Cloudflare DNS records are set to DNS Only (Grey Cloud).
  2. Verify that Port in ServerDescription.json matches your assigned Warden port.
  3. Confirm that UseDirectConnection is set to true.

3. Wine / UE4SS Hook Failure on Boot

• Log Signature:

  wine: Unhandled page fault on execute access
  [UE4SS] Failed to attach to target process
  

• Cause: Incompatible UE4SS version after a major game update, or missing Wine Visual C++ redistributable packages.
• Resolution:
  1. Temporarily disable UE4SS by setting WindrosePlus : 0 in Windrose/Binaries/Win64/ue4ss/mods/mods.txt.
  2. Download the updated UE4SS release that corresponds to the latest game build.

4. World Save Corruption

• Log Signature: LogWorld: Error: Corrupt save package detected in WorldData.sav.
• Cause: Unclean server termination (power loss, killing container during disk write).
• Resolution:
  1. Stop the server in DustBowl Warden.
  2. Open the Snapshots tab and restore your most recent clean snapshot.
  3. In ServerDescription.json, ensure AutoSaveIntervalMinutes is set to at least 15.

Systematic Diagnostic Checklist

When investigating an unfamiliar crash:

1. Review Live Logs: Inspect /home/container/Windrose/Saved/Logs/WindroseServer.log via the Warden File Manager.
2. Validate Game Files: Toggle Auto Update to true in Warden Startup Parameters and restart to trigger SteamCMD file verification.
3. Isolate Modding: Disable custom UE4SS mods to determine if vanilla binaries launch cleanly.

Useful Interactive Tools

• Test connection endpoints with the Direct Connect URL Generator.
• Test remote administration with the RCON Command & Configuration Helper.