Project Zomboid “Host must allow you to join”: what to check

First: is this a Host game or a dedicated server?

Ask who started the world and how. If your friend selected Host inside the game, begin with that friend’s co-op invitation permissions. If a separate dedicated-server program or hosting panel runs the world, begin with the operator’s access policy and your server account. The same group can use either method, so “my friend’s server” does not settle the question.

The developer explicitly distinguished Steam co-op invitations from the dedicated-server whitelist when explaining this error. Opening a public listing or knowing an IP address does not establish that your account has permission. Preserve the exact message before changing anything; a later timeout is a different symptom.

Source: The Indie Stone · co-op permission clarification · Historical developer clarification

The host: check the invitation in the running world

1. Load the intended Host world and wait until you have entered it. Open Escape, then the Invite or Invite Friends screen.
2. Find the joiner’s exact Steam account. Check its permission state and use the available control to allow the account if it is denied. Labels and toggle appearance can vary by client language and patch.
3. Send an invitation from that running world. Ask the joiner to use the fresh invitation instead of an old server entry or a different friend’s session.
4. Keep the hosting client and world running while the joiner connects. Ask them to report whether the same permission message remains or has changed.

Source: The Indie Stone · Easy Co-op Test · Historical developer instructions

The joiner: accept the right session

Return to the game’s main menu before retrying an invitation. Confirm that you and the host are Steam friends on the accounts actually running the game. A display-name match is not enough when someone uses a second account. Launch the Steam copy through Steam with Steam running.

If you deliberately use a non-Steam launch mode, tell the host. Developer instructions explain that Steam invitations require Steam-enabled clients. Do not add -nosteam as a generic fix for a Steam invitation problem; it changes the connection mode rather than granting permission.

Source: The Indie Stone · Easy Co-op Test · Historical developer instructions

Already allowed, but still cannot join?

1. Compare the full installed version strings and the selected branch on both clients. On a dedicated server, include its startup version. Stable 42.21 was announced on 28 September 2026; merely saying “Build 42” is insufficient.
2. Confirm that the host checked the same account in the same currently running world. Send a new invitation after checking that state.
3. Write down the new result. A permission message, Failed to establish P2P, a missing-file message and Loading Map are different checkpoints; do not keep toggling permission for all of them.
4. For suspected damaged client files, exit the game and use Steam’s installed-file verification. Retest once and record the result.
5. If mods are involved, use a separate named vanilla test world with an agreed client mod state. Keep the original world and its mod configuration intact. If the small test works, investigate the original mod list and logs instead of deleting its save.

Source: Steam Support · Verify Integrity of Game Files · Official Steam support

On a dedicated server: ask the operator about access

Confirm the server address, configured port, server password and your server account username/password with the operator. A server account password is not your Steam password. Do not publish either credential in a help request. If the server is closed to unregistered accounts, the operator must approve or create access using the controls supported by their current server.

Public listing, password protection and Open/whitelist policy are separate concepts. An old tutorial’s Open=true change can broaden admission; it should not be a joiner’s permission workaround for someone else’s private community. Likewise, an older Build 42 migration report is not proof that every player must manually be added by Steam ID. Ask the operator to inspect their generated settings and the exact rejection rather than editing the database from a copied recipe.

Source: The Indie Stone · Whitelist Without Steam IDs · Build 42 support discussion

What to send when the first checks fail

Prepare one short report: Host or dedicated, full client/server versions, Steam or non-Steam mode, whether permission was checked, exact error text, time of the failed attempt and whether a separate vanilla test changes it. The host and joiner should each retain their relevant console output. Redact account credentials, private addresses and unrelated personal details before sharing logs with official support.

Do not delete the Zomboid data directory, remove a character, reset the world or turn off the firewall just because this message appears. First establish whether access was granted. Network diagnosis is useful after the symptom changes to a connection failure; it does not replace the host’s permission check.

Source: Steam · Ultimate Multiplayer Guide [b41] and [b42] · Support-maintained guide