Your ReSkate server is online, but players cannot find it in Multiplayer > Servers, or they find it and the join fails. Nearly every case is one of the causes below. Work down the list in order: the first two cover most tickets.
1. The player and the server are on different ReSkate releases
Players and the server must run the same ReSkate release. Players get new releases through the ReSkate launcher. Your server checks GitHub when it starts and every 30 minutes after that, and installs a newer release as soon as nobody is on. Right after a release there is a window where the two do not match: a player who has updated cannot join a server that has not, and the other way round.
Fix: type update in the console. The server checks for a new release and installs it straight away (anyone on is told to rejoin). On the player's side: close skate. and start it again through the ReSkate launcher, which brings them up to the current release.
If you are not sure which side is behind, run update anyway: it only installs something when a newer release exists.
2. The server is not listed in the browser
The ReSkate browser lists only servers that sign in to Steam with a game server login token. We create one for every server when it is built. The How players join card on the Overview tab warns you if your server has none, and the Steam token section of the Server Settings tab says whether one is set.
Fix: if no token is set, paste one on the Server Settings tab and restart. Make it at steamcommunity.com/dev/managegameservers for App ID 3354750; each running server needs its own, so do not reuse one from another server. If a token is set and the server is still missing, open a ticket: the token may need replacing, and we can do it for you.
Until it is listed, players can still join with the join code printed in the console when the server starts (status shows it again).
3. "Show in the server browser" is off
With that switch off on the Server Settings tab, the server is hidden on purpose, and the join code is the only way in.
Fix: turn it on, save, and restart.
4. Players are searching for the wrong name
The browser finds servers by name. Send players the exact Server name from the How players join card; they can type part of it into the search box. If you renamed the server, the new name shows in the browser only after a restart.
One more trap: each player's game hides a server whose name contains a word on the ReSkate team's word list, whatever your settings say. If the server is listed for nobody even with a token, try a plainer name.
5. The server has not finished starting
Between Start and the server reporting that it is up, it is checking for an update, signing in to Steam and loading the map. Joins during that window fail.
Fix: watch the console, wait for the server to come up, then refresh the server list.
6. Wrong password
If the player reaches the server and is turned away at the password, the network side is fine. The password is the Join password on the Server Settings tab (letters and numbers only, and case matters). A new password applies at the next restart.
Fix: copy the password from the How players join card. If you just changed it, restart first.
7. The server is full
The player cap comes from your plan: 16, 32, 64 or 128. Players with a reserved slot, listed in access.reserved_players_slots or given a role that has one (vip, moderator, admin), can still join a full server; each adds a slot beyond the cap, so the browser can show 33/32.
Fix: give your regulars a reserved slot (role <SteamID64> vip in the console), or move to a plan with more player slots.
8. The server is running a map the player does not have
Players need the same custom map installed to join while it runs. A map whose folder in Mods keeps its Thunderstore name (Owner-Name or Owner-Name-1.0.0) is offered to players who lack it, and the game downloads it and rejoins. A map in a renamed folder is not, and players have to install it themselves.
Fix: keep the Thunderstore folder name, or switch to a built-in map (map San Vansterdam). More in custom maps and park mods.
9. The player is kicked or banned
A player kicked by an admin stays out for the kick time (by default until the server restarts). bans lists the server's own bans, and unban <SteamID64> lifts one. The server also turns away players the ReSkate team has banned from multiplayer.
10. One player, everyone else fine
If exactly one person cannot join while the rest are in, it is their side: their ReSkate release (section 1 again), a game not started through the ReSkate launcher, or their own connection. The server needs no open ports on anyone's side; players connect through Steam's relay network.
Still stuck?
Open a ticket from your dashboard with: the exact message the player sees, the ReSkate release their launcher shows, the last lines of your server console, the server name they searched for, and whether anyone at all can join. Those five answers usually let us solve it in one reply. The longer explanation of the token rule is in ReSkate server not showing in the browser.
ReSkate is a community project. Connect Hosting is not affiliated with Electronic Arts, Full Circle or the ReSkate team. skate. is a trademark of Electronic Arts.