Can't Join a The Bus Multiplayer Server? GUID, Mods and Version Fixes

When you cannot join a The Bus multiplayer server, check five things in this order: that you pasted the current GUID from the server console into Add Server, that the server is public if you are searching by name, that you have every mod the server marks Client and Server, that you and the server are on the same game version and branch, and that you typed the right server password. Most failed joins are a stale GUID or a missing mod.

The Bus runs all multiplayer through a dedicated server program, so these fixes apply whether a friend runs the server at home or it is rented.

Problem 1: the GUID is wrong or old

Players join by GUID, not IP. When the server starts, its console prints a line beginning with:

Server can be reached with the GUID

followed by a long ID. Things that go wrong:

• Copied part of it. The ID is long. Copy the whole value, with no spaces before or after.
• Copied an old one. If players say yesterday's GUID stopped working, get the line from the current console output after the latest restart and share that. Whoever runs the server should post the fresh line whenever they restart, until you know whether it stays the same on your setup.
• Typed instead of pasted. One wrong character and the join silently fails. Paste it.

In the game: Multiplayer, Add Server, paste the GUID, then join from your saved servers.

Problem 2: searching for a server that is not public

A server only appears in the public list when listServerAsPublic is true in TheBus/Settings/ServerSettings.cfg. Private servers are joined by GUID only. If you are looking for it by name and it is not there, either the owner kept it private on purpose, or the setting did not save.

For the server owner: open ServerSettings.cfg, check the value, and restart the server. ServerSettings.cfg is JSON, so keep each value in the same format the file already uses, and remember that one broken comma can make the server ignore the whole file. The console shows errors on start.

Problem 3: missing Client and Server mods

This is the big one on modded servers. On the Steam Workshop, The Bus mods are marked as server only or as Client and Server. A Client and Server mod, such as a new bus or map content, must be installed on your PC too. If the server runs one you do not have, you cannot connect.

To fix it:

1. Ask the server owner for the exact list of mods the server runs, with links.
2. Subscribe to every one marked Client and Server.
3. Start the game once so Steam downloads them, then join.

Server owners: post the list in your group chat or Discord and keep it updated. Every time a mod is added on the server, every driver has to add it too. A Steam Workshop collection with exactly the server's client side mods makes this one click for players.

Also watch mod updates. If the server has an older or newer version of a mod than a player, the join can fail the same way. After updating mods on the server, tell everyone to let Steam update theirs.

Problem 4: version or branch mismatch

The Bus updates through Steam. Two common traps:

• Server not updated after a patch. Players get the new version, the server still runs the old one, and nobody can join. The owner reruns the SteamCMD update (or keeps auto update on) and restarts.
• Beta branch on one side only. If the server runs a beta branch and a player does not, or the other way round, they cannot connect. In Steam, right click The Bus, Properties, Betas, and pick the same branch as the server. Owners should only run a beta branch when the whole group has agreed to switch.

Problem 5: password problems

If the server has a password, the game asks for it on join. The value is serverPassword in ServerSettings.cfg. Check capitals and spaces, and remember the separate admin password is not the join password. If the owner changed the password, it applies after the server restarts.

Problem 6: the server is full or not running

maxPlayerCount caps how many drivers can be on. If your group has grown, raise it and restart. And the obvious one: the server program has to be running. If the person who hosts at home turned their PC off, the city is closed.

Problem 7: home network issues

If none of the above helps and the server is hosted at home, the network may be blocking it. Allow the server program through the firewall on the machine it runs on, and check whether your connection is behind CGNAT (common on mobile, satellite and some fiber providers), which blocks incoming connections. Testing from a friend's house rather than the same network as the server tells you whether outside players can reach it.

Checklist for server owners

1. Post the full GUID line from the current console output.
2. Decide public or private, and check listServerAsPublic.
3. Share the list of Client and Server mods, with versions.
4. Keep the server updated, and on the same branch as players.
5. Confirm the password and slot count.

Making it someone else's problem

A The Bus server with GamezServers keeps itself current with auto update on, so the version trap mostly goes away. Server name, password, admin password, max players, public listing and the beta branch are fields in the control panel rather than JSON, the live console shows the GUID line any time you need to share it, and the Mods folder is in the file manager. For a full setup, see how to host a The Bus dedicated server.

FAQ

Where do I find the GUID for my The Bus server?

In the server console when it starts, on the line beginning "Server can be reached with the GUID". Share the ID after it.

Why can I not find my The Bus server in the list?

It is not public. Set listServerAsPublic to true in ServerSettings.cfg and restart, or join with the GUID through Add Server.

Do I need the server's mods to join The Bus multiplayer?

Only the ones marked Client and Server. Server only mods need nothing from players.

Can I join a beta branch server on the normal version?

No. Switch to the same branch in Steam under Properties, Betas, or ask the owner to run the default branch.