Troubleshooting

The most common issues on a Windrose server, and how to fix them. In every case, the panel Console is your first tool: read the last lines shown before the shutdown or error.

The server won't start

Error in ServerDescription.json or WorldDescription.json

A trailing comma, a missing quote or an unclosed brace makes the JSON invalid and prevents the server from starting or loading the world.

1. Stop the server
2. Compare the file with your last working copy, or check it with a JSON validator
3. Fix the error, save, then restart

See Configuring the server and World settings.

The world cannot be found

If the server cannot find the configured world, check that:

• WorldIslandId in ServerDescription.json matches the name of a world folder exactly
• this folder is in the right version subfolder (RocksDB/<GameVersion>/Worlds/)
• the folder has not been renamed and all its files were transferred

See Importing a solo world.

My changes disappear

The server rewrites ServerDescription.json on shutdown. If you edited the file while the server was running, your changes were overwritten. Stop the server, make the change again, then start it.

The server stops after a mod or replaced files

The Windrose dedicated server is a Windows program, run in an environment managed by YorkHost. Do not replace the server executables or files with files copied from your game installation, and remove the last mod you added if the problem started right after. As a last resort, restore a backup from the Backups tab.

The world no longer loads

After a game update or a hard shutdown, a world may refuse to load. Restore a backup from the Backups tab: see Backups.

Players can't join the server

Symptom	Likely cause	Solution
Invite code not found or rejected	Typo, wrong case, old code	Copy and paste the InviteCode value from ServerDescription.json; the code is case-sensitive
Server not found right after startup	Server still loading	Wait for the console to settle, then try again after a minute
Rejected or disconnected for a different version	Client and server not on the same version	Update the server after each game update, see Updating the server
Password rejected	Password changed while the server was running, or inconsistent IsPasswordProtected	Stop the server, check both fields, restart
Server full	MaxPlayerCount reached	Raise the value (8 maximum at the moment)
Only one player can't connect	VPN, proxy or their router's DNS	Turn off the VPN or proxy; try another DNS (for example 8.8.8.8)
Multiplayer menu unavailable	Depending on the version, you must have started the adventure (prologue) in solo	Play the start of the adventure in solo, then try again
Player on another platform	Our servers are designed for the PC (Steam) version	Contact support

Ports and direct connection

Joining with an invite code requires no ports to be opened on your players' side. On the server side, opening the required ports is handled by YorkHost. Do not change the network settings in ServerDescription.json (UseDirectConnection, DirectConnectionServerPort, P2pProxyAddress…): the server must use the port assigned by the panel. See Are all ports open? and Unable to connect to the server.

Lag and not enough memory

Windrose is RAM-hungry: usage grows with the number of players and above all with the size of the bases built. Typical signs of low memory: increasing lag, desyncs, or even the server stopping abruptly without a clear error in the console.

1. Check RAM usage on your server's page in the panel. See also Server performance debugging.
2. Compare with the recommendations: about 8 GB for 2 players, 12 GB for 4 players, 16 GB for 8 players.
3. Lower MaxPlayerCount if the server is always full and saturated.
4. Restart the server regularly, for example every night, with an automatic restart in the Schedules tab.
5. Upgrade to a higher plan if RAM stays saturated: the Admiral plan (24 GB) adds headroom for large bases. See Choosing a plan.

Lag for a single player

If only one player lags while the others play normally, the problem usually comes from their connection (Wi-Fi, VPN) or their PC, not the server.

The server degrades over time

Like many Early Access game servers, Windrose runs better after a restart. Schedule a daily restart at an off-peak time from the Schedules tab: see Configure automatic restart. Use the panel's stop button rather than killing the server, so the world has time to be saved.

Still stuck?

Contact support 7/7 on Discord or through your client area, including:

• your server name
• what you changed just before the problem
• the last console lines at the time of the error