Come chat with us and we will get back to you as soon as possible!
Contact SupportHolyHosting
Holy Team

Getting into a Windrose server is simple once you know which connection method your server is using. Most players will join with an invite code, which works by default. Direct IP is also available, but it must be enabled in the server configuration first. Only one of those two methods can be active at a time, because apparently even servers enjoy making you choose.
Invite codes are the default way to connect to a Windrose server. You can find the code in your server panel, then enter it in-game.
Anyone else joining your server can use the same in-game process. Share the invite code directly with them, then have them follow the steps from opening Windrose onward.
If the server does not appear, copy the invite code again from the panel and check for missing or extra characters. One wrong character is enough to send the search nowhere useful.
Direct IP lets players join with the server IP address and port instead of an invite code. Before turning it on, stop the server. Windrose rewrites `ServerDescription.json` when the server shuts down, so changes made while it is running may be overwritten.
Enabling Direct IP disables invite code joining. To switch back later, set `UseDirectConnection` to `false`, save the file, and restart the server.
```json "UseDirectConnection": true, "DirectConnectionServerAddress": "your.server.ip", "DirectConnectionServerPort": your_port, "DirectConnectionProxyAddress": "0.0.0.0" ```
Use the IP address and port shown in your HolyHosting server panel. Leave `DirectConnectionProxyAddress` as `0.0.0.0` unless you have a specific reason to change it.
Save the file, then restart the server so the new settings take effect.
After Direct IP is enabled, give the server IP address and port to each player who needs access.
If the connection fails, confirm that Direct IP is enabled in `ServerDescription.json` and that the server was restarted after saving the file.
A password gives you another layer of control over who can join. It works with either invite code joining or Direct IP, and it is useful if your invite code or IP gets shared beyond your intended group.
Password settings are also stored in `ServerDescription.json`, so stop the server before editing the file.
```json "IsPasswordProtected": true, "Password": "your_password_here" ```
Choose a password your group can remember, but avoid anything obvious. The `Password` value only matters when `IsPasswordProtected` is set to `true`, so both fields need to be correct before you restart.
Save the file, then restart the server. Players will use the normal invite code or Direct IP steps, then enter the password when Windrose asks for it.
To remove password protection, stop the server, set `IsPasswordProtected` back to `false`, save, and restart. You can leave the password value in the file or clear it, since it is ignored while protection is disabled.
If you cannot connect, check these items before making bigger changes:
If problems continue after these checks, HolyHosting support can review the server configuration and help narrow down what is blocking the connection.
For most Windrose servers, the invite code is the fastest option. Direct IP is useful when you prefer address-based joining, but it requires a short configuration edit first. If privacy matters, add a password so only the players you choose can enter. Once the connection method is set, share the invite code or IP details with your group and start exploring.
Come chat with us and we will get back to you as soon as possible!
Contact SupportSet up a Starbound dedicated server, connect from the game, add admins, enable a whitelist, adjust team size, and install Workshop mods.
Set up a Starbound admin account, enable in-game admin access, and fix common login or permissions errors on your server.
Some Eco players cause more trouble than the actual apocalypse. This guide covers banning, unbanning, and cleaning up the Users.eco file when the standard commands are not an option.