We are your new 5-Star Hosting Company. At least according to


Check out our current game server offerings HERE.

All servers come with a 24-Hour Trial, Free Backups, and 40Gbps DDoS Protection included!

We offer quality support, a detailed knowledgebase, video tutorials on most topics, and even live support in case you prefer a live human 😉


Use code SAVE15 to take 15% OFF Your First Invoice with ChicagoServers! Limited Time!

Common Windrose Server Issues (and How to Fix Them) Print

  • 15

Running into problems with your Windrose server? You are not alone. Since the Early Access launch, a handful of issues keep coming up. The good news is that most of them are simple to fix once you know where to look.

If your server is not working as expected, start with the sections below. In most cases, you will find the solution quickly.


The Tutorial Requirement (Most Common Issue)

This is by far the most frequent cause of connection problems.

Windrose requires every player to complete the singleplayer tutorial before joining multiplayer. If they skip it, the game does not show a clear error. Instead, it may fail to connect or send them back to the menu.

To resolve this, have the player:

  • Launch Windrose in singleplayer
  • Complete the full tutorial (about 15 to 20 minutes)
  • Exit and reconnect to your server

Once completed, this fixes the issue in most cases.


Connection Issues

If the tutorial is not the problem, check the following:

Server Still Starting

Your server must fully boot before players can join. After starting or restarting, give it a minute to finish loading.

You can monitor progress in the ChicagoServers Control Panel using the Web Console or Log Viewer. Once the world has loaded, players should be able to connect.

If your invite code shows as unavailable, the server likely has not completed its first startup.


Invite Code Problems

Windrose uses invite codes instead of IP addresses.

Players must:

  • Go to Play → Connect to Server
  • Enter the invite code exactly

Common mistakes include:

  • Codes are case-sensitive
  • Confusing characters like O and 0 or l and 1

It is best to copy and paste the code directly from the control panel.


Version Mismatch

The server and all players must be running the same version.

If they are not, connections will fail without much explanation.

To fix this:

  1. Stop the server in the control panel
  2. Run Steam Update to validate server files
  3. Have players update their game through Steam
  4. Restart the server

Network or DNS Issues

If a player can connect on one network but not another, DNS or routing may be the issue.

Try the following:

  • Switch to Google DNS (8.8.8.8 and 8.8.4.4)
  • Disable VPNs or proxies temporarily
  • Make sure the Windows firewall allows Windrose

Configuration File Issues

Windrose uses two main configuration files:

  • ServerDescription.json
  • WorldDescription.json

Both can be accessed through your ChicagoServers control panel.


Editing While the Server Is Running

This is a common mistake.

Windrose rewrites configuration files on shutdown. If you edit them while the server is running, your changes will be lost.

Always follow this order:

  1. Stop the server
  2. Make your changes
  3. Save the files
  4. Start the server again

Preset Switching to Custom

If you manually change world settings, the preset will automatically switch to Custom, also known as Captain’s Choice.

This is intended behavior. If you want to keep a preset, avoid editing individual settings.


WorldIslandId Mismatch

The WorldIslandId in ServerDescription.json must match the IslandId in WorldDescription.json.

If they do not match, the world will not load.

To fix this:

  • Check both files carefully
  • Restore from a backup if needed

Performance Notes

Windrose is still in Early Access, so performance can vary, especially with larger groups.

  • Around four players tends to be the most stable
  • Larger groups may experience lag or slowdowns
  • ChicagoServers plans include sufficient RAM, so performance issues are usually related to the game itself

Keeping group sizes smaller is the best option until further optimization is released.


Save and World Loading Problems

If your server starts but the world does not load, check the Log Viewer for errors.

Common causes include:

  • WorldIslandId mismatch
  • Corrupted save data after a crash
  • Invalid JSON formatting in configuration files

For JSON issues, use an online validator to find missing commas or brackets.


No Console Commands (Yet)

Windrose does not currently support admin console commands in Early Access. Server management is handled through:

  • Configuration files
  • The ChicagoServers control panel

More advanced tools are expected in future updates.


General Troubleshooting Checklist

If you are not sure what is wrong, try the following:

  • Check the Log Viewer for errors
  • Run Steam Update to verify files
  • Restart the server
  • Confirm client and server versions match
  • Review resource usage in the control panel

Most Windrose server issues fall into one of these categories. The tutorial requirement alone accounts for many connection problems. Once that is completed, everything else tends to fall into place.


Was this answer helpful?

« Back