Troubleshooting

When a server crashes on startup, Vaerune shows a crash report card in the workspace. The card summarizes the exit code and the last few lines of console output. Use Copy report to copy a formatted summary you can paste into a support request.

Common causes and fixes:

• Port already in use - another process (or another server you manage) is on the same port. Change the port in Server settings.
• Missing files- the install is incomplete or corrupt. Use the repair option in the game's menu to re-verify and restore missing files without reinstalling.
• Missing runtime - some games need a specific version of a Visual C++ runtime or .NET. The crash report will usually name it. Install it from Microsoft and try again.

Check the health dot first. If it is red, the server is unreachable from outside. Open the Connectivity tab and look at which check failed.

• UPnP failed - try a manual port forward in your router instead, or enable the Vaerune Tunnel (Plus/Pro).
• Port forwarded but still red - your ISP may be blocking inbound traffic (CGNAT). The tunnel bypasses this.
• Firewall- Windows Defender Firewall may be blocking the game's port. Check inbound rules for the server executable.

If the Vaerune Tunnel shows as disconnected or fails to assign an address:

• Check that your Plus or Pro subscription is active from your account page.
• Try toggling the tunnel off and on again. Vaerune picks the nearest relay on connect; if one relay is degraded it retries on a different one.
• A Windows firewall rule blocking outbound UDP on port 51820 can prevent the WireGuard connection from forming. Allow it for the Vaerune process.

The fastest path to a fix is Discord. Paste your crash report, describe what you tried, and someone in the community or on the Vaerune team will help. For billing or account issues, send a message in the support channel and tag the team.