no more room in hell 2 can't join friends
No More Room in Hell 2: Can't Join Friends or Failed to Join Squad
Install available updates on every device, then try one fresh squad invitation. If joining still fails, record whether it affects one account, one platform pair or the entire squad, and when the error appears.

Direct answer
- Record the installed build on each device before comparing invitation attempts.
- Separate a request that never arrives from a squad that forms and immediately disbands.
- The September 15, 2026 Resupply notes document squad-formation problems under certain network conditions.
Choose the next comparison from the symptom
| What you see | What it narrows down | Next check |
|---|---|---|
| One account fails with every leader | The failure follows the same account in these attempts; its cause is still unknown. | Compare that account with another teammate and record both platforms and builds. |
| The squad forms but immediately disbands | Invitation acceptance succeeds, but the session does not stay together. | Record who disconnects first and whether it happens before matchmaking. |
| Only a mixed-platform pair fails | This pair behaves differently; that result alone does not establish the cause. | Record the precise platform pair and the available crossplay settings. |
| Everyone fails at roughly the same time | Several players share a failure window; check for an official incident notice. | Read official announcements before repeating the same test. |
Before you start
Write down each player's platform, installed build, exact error and local time with time zone. Note whether the invitation arrived, whether the player appeared in the squad and when any disconnect happened. Keep an error screenshot with private account details hidden.
1. Install available updates and record builds
Keep a record of the version shown on each device instead of assuming that all platforms received the same update.
- Close the game and install available updates on each device. Reopen it and record the displayed build.
2. Try a fresh squad invitation
Record invitation delivery and squad membership as separate outcomes so the report identifies the stage that fails.
- Leave the previous squad, create a new one and send a fresh invitation. Record whether the request arrives and what happens after acceptance.
3. Change the squad leader once
Keep the players and other conditions unchanged for this comparison; changing several things together makes the result harder to interpret.
- If the attempt fails, change the squad leader once and send a new invitation. Record whether the result changes.
4. Compare one other player pair
Use a teammate who is available for a short comparison. Stop repeating an identical failed attempt once you have a reproducible example.
- Compare a two-player invitation involving the affected account with a pair that can join. Record the accounts privately, platform pairs and outcomes for each attempt.
If it does not work
Use the Support link in the official update notes or the official Discord. Include the date and time zone, platforms and installed builds, exact error, failed stage, squad leader, comparison results and shortest reproduction sequence. Attach the screenshot; keep passwords, authentication codes and private account identifiers out of public posts.
Source notes
Official source checked October 16, 2026. The dated 1.1 notes establish the historical issue above; the latest release status has not been reviewed for this article. The comparisons are troubleshooting suggestions, not results from our own current game-client testing. Current platform menu paths and router/NAT procedures have not been validated here.
What the official notes confirm
The September 15, 2026 Resupply 1.1 notes acknowledge squad-formation problems under certain network conditions and request reports through Support or Discord. They also describe Recently Played With list fixes and a controller binding for accepting or rejecting requests; those changes do not establish a fix for the network-related issue.