Stormworks Server Not Showing or Friends Can't Join (Fixes)

When a Stormworks dedicated server is not in the Join Game list or friends cannot get in, check five things in order: the server has finished loading, all three UDP ports starting at port are open (not just the first), the server is on the same game version as the players, the password matches, and the player is not blocked by the <whitelist> or <blacklist> in server_config.xml. The first two cover most cases on home hosted servers, and the version check covers most of the rest after a Stormworks update.

Quick checklist

Cause 1: the server is not ready yet

A Stormworks server takes a while to load its islands, the save and any addons. It only accepts players once it is done. In the console, wait for a line like Server: ready to spawn for peer. Until then, the list either does not show it or the join hangs. Large saves with many vehicles and a few Lua addons make this noticeably slower, so give it time after each restart before you start debugging.

Cause 2: only one of the three ports is open

This is the most common mistake. The Stormworks server uses three consecutive UDP ports starting at the port attribute in server_config.xml:

Forward all three to the PC running the server, and allow server64.exe through Windows Defender Firewall on both private and public networks. If you run a second server on the same machine, set its port three higher so the ranges do not overlap.

If you forwarded correctly and the ports still look closed from outside, check two things. A modem that is also a router in front of your own router means double NAT, and forwards on the inner router do nothing. A provider using carrier grade NAT means no forward can work. See how to tell if you are behind CGNAT, and our port forwarding guide for the router steps.

Cause 3: version mismatch after an update

Stormworks patches often. Players' games update through Steam automatically, the dedicated server does not unless you update it. A server on the previous build drops out of their list or refuses the join. Update it through SteamCMD:

steamcmd +login anonymous +app_update 1247090 validate +quit

Then restart. If you host on a panel with an auto update option, make sure it is on, since some setups ship with it off by default. Players on a beta branch of the game can only join a server on that same branch.

Cause 4: the password

The join password is the password attribute on server_data:

<server_data port="25564" name="Harbor Crew" password="mayday" max_players="16" ...>

The server only reads the file when it starts. If you changed the password while it was running, your edit either did nothing or was overwritten when it saved. Stop the server, edit, then start. To make the server public, leave the value empty: password="".

Cause 5: whitelist and blacklist

Below the attributes, the config holds lists of Steam64 IDs:

<whitelist>
    <id value="76561198000000000"/>
</whitelist>
<blacklist>
    <id value="76561198000000001"/>
</blacklist>

When the whitelist has entries, players missing from it cannot join. Anyone in the blacklist is refused, and an in game ?ban adds people there. If one friend cannot join while everyone else can, look at these two lists first. Use the long Steam64 ID that starts with 7656, not a profile name.

Cause 6: they can join, but cannot do anything

A player who connects but cannot use the workbench or spawn vehicles is not broken, they are not authorized. Add them in game with ?add_auth <session id> or list them under <authorized> in the config so it survives restarts. The full config and the admin commands are in our Stormworks hosting guide.

Finding it in the list

Players open Multiplayer, then Join Game. The list can be long and sorted oddly, so search for part of the name rather than scrolling, and make the name distinctive. A password protected server shows a lock. If the server only appears after a refresh or two, that is normal right after a restart.

Players with high ping can still join, but physics heavy vehicles feel laggy for them.

When it is one player's machine

If the server works for everyone but one person, the problem is on their side. Have them restart Steam, verify the game files (right click Stormworks, Properties, Installed Files, Verify integrity), turn off any VPN, and make sure they are not on a beta branch. Antivirus that blocks the game's network traffic also shows up as an endless join.

Skip the port part

Causes 1 to 3 are mostly about running the server at home. A GamezServers Stormworks server has its own address with all three ports open, the live console shows the ready line so you know when to join, and you edit server_config.xml in the file manager or over SFTP. Updates are a restart away, and one click backups protect the save before you try one. It stays online when you log off, and the group can split the bill instead of one person carrying it.

FAQ

Why is my Stormworks server not showing in Join Game?

The server is still loading, or the three UDP ports from port to port + 2 are not all open. Wait for the ready line in the console and forward all three.

What ports does a Stormworks dedicated server use?

Three consecutive UDP ports starting at the port value, 25564 to 25566 by default.

Why can my friend see the server but not join?

Usually a version mismatch after an update, a wrong password, or the whitelist. Update the server and check the lists in server_config.xml.

Why can't players spawn vehicles after joining?

They are not authorized. Add them with ?add_auth in game or under <authorized> in the config.

Do I need to restart after changing server_config.xml?

Yes. The server reads it only at start, so stop it, edit, and start again.