A convoy session that is running but invisible is almost always one of these.
1. No valid logon token
Without a Steam game server token the session runs but is never published. Check the console during boot, then set server_logon_token in server_config.sii with a token created for App ID 227300 on your own Steam account.
2. The session is hidden by config
show_servermust betrue.friends_onlymust befalseunless you only want Steam friends to see it.- A password does not hide a session, it only asks for the password on join.
3. Use the Session Search ID
The browser list is long and slow. The console prints a Session Search ID, a long number with a slash in it. Pasting that into the search field finds the session directly. Send it to your friends rather than asking them to scroll.
4. Server packages are missing or stale
- Without
server_packages.siiandserver_packages.datthe server cannot host the map properly. - If they were exported before a game update, export them again and upload both.
- A player who does not own the map DLC in the packages cannot join, even when they can see the session.
5. The config file will not parse
- A
moderator_listcount that does not match the entries breaks the file. - Missing quotation marks around text values break it too.
- The console prints a parse error early in the boot.
6. Version mismatch
Steam updates your players' game automatically. Restart the server from the panel after a patch so it updates too, then try again.
Open a ticket from Support in the Client Area with the console output from a fresh start if the session is still missing.





