Fix common Windrose server errors

Most Windrose server problems come down to four things: using an invite code instead of the address, a version mismatch, the wrong world ID, or not enough memory. Start at the top of this page and work down. Windrose often shows no error text at all, so each problem below is named by what you see.

Joining problems

The invite code can’t find the server

Why: Your server runs in direct connection mode, so players join by its address only. The developers say invite codes don’t work while direct IP is on.

Fix:

1. In Windrose, choose Play, then Connect to Server, and switch to Direct IP.
2. Type the address and the port from the address card on Overview.
3. Connect.

Invite codes and direct connect explains why we use this mode.

You’re sent back to the main menu with no message

Why: The developers list this as a known issue with Direct IP. If the password is wrong, or your game and the server are on different versions, the game drops you at the main menu without saying why.

Fix:

1. Check the password in Settings. It’s case-sensitive.
2. Update Windrose in Steam or Epic, then restart the game.
3. Check that the server is on the newest version too. Restart it from Overview to pick up a new build, unless you pinned a version in Settings.

Version mismatch after an update

Why: Your game and the server must be on exactly the same Windrose version. Right after a patch, one of them may still be on the old one.

Fix:

1. Update the game. If Steam doesn’t show the update, restart Steam.
2. Restart the server from Overview. It installs the newest version on start.
3. If the server is still behind, the Linux server build for that patch may not be out yet. Wait a little, then restart again.

Connection times out, or you’re stuck loading

Why: The server is still starting or waking, the port is wrong, or something on the player’s side blocks the connection.

Fix:

1. Check the status on Overview. Wait until it says Running, then join again.
2. Check that you typed the port from the address card, not 7777.
3. Restart your game and Steam. The developers also suggest restarting your PC and router, and turning off any VPN.
4. If only one player can’t connect, check their firewall or antivirus. The developers’ FAQ shows how to let Windrose through Windows Firewall.
5. Windrose is built for IPv4 internet connections. The developers say a PC that prefers IPv6 can have trouble connecting, and their FAQ shows how to change that.

The game won’t take the address

Why: The Direct IP screen is made for an IP address (a number like 203.0.113.25). If your version won’t accept a name like galleon.play.wilderack.com, use the number behind it.

Fix:

1. On Windows, open Command Prompt.
2. Type nslookup galleon.play.wilderack.com, using your server’s address, and press Enter.
3. Use the number shown under “Address” in the address box, and the port from the address card in the port box.

If the number ever stops working, look it up again the same way.

World and save problems

The server made a new, empty world

Why: The server loads the world whose ID is in WorldIslandId, in R5/ServerDescription.json. If no world folder matches, it makes a new one. This happens most often after uploading a world.

Fix:

1. Stop the server.
2. In Files, open R5/Saved/SaveProfiles/Default/RocksDB_v2_Backups/, then the version folder and Worlds. Note the folder name of your world.
3. Set WorldIslandId to exactly that name.
4. Start the server.

If your world folder isn’t there, it’s in the wrong place. See bring your single-player world. Your new, empty world stays in its own folder and does no harm.

A save is broken

Why: A crash or a bad copy damaged the newest save. Windrose checks its saves when it starts.

Fix:

1. Make sure AutoLoadLatestBackupIfHasBroken is true in ServerDescription.json. Then the server loads the newest good backup by itself, and marks the bad one with Broken- at the start of its name.
2. If that doesn’t work, restore a backup from Backups. We make a safety backup first.

Server problems

The server crashes or stops when the crew is on

Why: Usually not enough memory. Windrose needs a lot of RAM, more for each player.

Fix:

1. Open the Console. If the crash helper card shows, follow its hint.
2. Check the RAM graph on Overview. If it was near the top before the crash, move up a plan: 8 GB for 2 players, 12 GB for 4, 16 GB for more.
3. If RAM was fine, restart the server and note what the crew was doing. Then send the console lines to us from the crash card.

Still stuck?

Write to us at support@wilderack.com with your server’s name and what you see. Real people read every message. For bugs in the game itself, the developers take reports through their support site.