How to Fix Can’t Join Friend’s Minecraft World

Almost always a network, version, or settings issue — here’s how to work through it

---

Not being able to join a friend’s Minecraft world is one of the most common multiplayer frustrations, and it happens across every version of the game.

The error you see — or don’t see — points toward a specific cause, but even without a clear error message there’s a reliable set of fixes that covers the vast majority of cases.

Start with the simplest checks and work toward the more involved ones.

---

Make Sure You’re on the Same Version

This is the single most common reason two players can’t connect, and it’s the first thing to check before doing anything else.

Minecraft Java Edition and Minecraft Bedrock Edition are completely separate games and cannot connect to each other under any circumstances. If one person is on Java and the other is on Bedrock, you simply cannot play together — there is no workaround for cross-version play between these two editions.

Within Java Edition or within Bedrock, both players also need to be on the same game version. Java Edition 1.21 cannot connect to a world hosted on 1.20.4. Bedrock has the same requirement.

Check your version in the Minecraft launcher before anything else. Both you and your friend need identical versions. If one person is ahead on an update, the other needs to update — or the host needs to roll back using the launcher’s version selector.

---

Check the Host’s World Settings (Bedrock)

On Bedrock Edition, the host’s world settings control whether other players can join at all. Several settings can silently prevent connections.

The host should open their world settings and verify:

Multiplayer is enabled. In the world settings, there’s a toggle specifically for multiplayer — if this is off, nobody can join regardless of anything else.

Multiplayer game type is set correctly. The game needs to allow the joining player’s permission level.

Online Play is not restricted by Xbox/Microsoft account settings — covered in more detail below.

---

Check Microsoft Account and Xbox Settings for Bedrock

Bedrock Edition uses Microsoft accounts and Xbox network for multiplayer, and account-level restrictions frequently prevent joining — especially on accounts belonging to players under 18.

The host and joining player should both check:

Go to account.xbox.com/settings and sign in. Under Privacy and Online Safety, check the settings for You can join multiplayer games and You can play with people outside of Xbox Live. Both need to be set to Allow.

For players under 18, these settings are controlled by the Microsoft Family account parent. The parent needs to log into the family settings and grant multiplayer permissions to the child’s account. This is by far the most common reason younger players can’t join friends on Bedrock.

---

Use the In-Game Friend System Instead of Direct IP

For Bedrock Edition, trying to join through the in-game Friends tab is more reliable than manually entering an IP address. The Friends tab uses Xbox network infrastructure to establish the connection without requiring port forwarding.

Both players should be friends on Xbox/Microsoft network — search for each other’s gamertags and add each other as friends. Once you’re friends, the host’s active world should appear in the joining player’s Friends tab under Joinable Friends’ Worlds. Tap or click it to join directly.

For Java Edition, the Friends tab doesn’t work the same way — Java uses direct IP connections or services like Minecraft Realms.

---

Check Firewall and Antivirus Settings

Firewalls blocking Minecraft’s connection are a very common cause of join failures, particularly on Windows where Windows Defender Firewall is active by default.

Go to Windows Security → Firewall and Network Protection → Allow an App Through Firewall. Look for Minecraft in the list. If it’s present, make sure both Private and Public boxes are checked. If it’s not in the list, click Allow Another App, navigate to the Minecraft executable, and add it with both boxes checked.

Also check any third-party antivirus or firewall software separately — these maintain their own rules independent of Windows Firewall and frequently block Minecraft’s network traffic.

---

Port Forwarding for Direct Java Edition Connections

If your friend is hosting a Java Edition world on their home network and you’re trying to connect via their IP address, their router needs to have port forwarding configured to allow outside connections in.

Minecraft Java Edition uses port 25565 by default. The host needs to:

Log into their router’s admin panel — typically at 192.168.1.1 or 192.168.0.1 in a browser. Find the port forwarding section. Create a rule forwarding TCP and UDP port 25565 to the local IP address of the computer hosting the game.

The host also needs to share their public IP address — not their local 192.168.x.x address — with you. They can find this by searching “what is my IP” in a browser.

This process varies by router model and is one of the more involved steps. If it feels like too much, consider using a Minecraft Realm or a service like Hamachi or Playit.gg instead — these handle the network routing without requiring router configuration.

---

Use Hamachi or Playit.gg as an Alternative to Port Forwarding

These services create a virtual private network or tunnel that lets two players connect as if they’re on the same local network — without either player touching their router settings.

Hamachi (by LogMeIn) — both players install Hamachi, the host creates a network, the joining player joins it, and then connects to the host’s Hamachi IP address in Minecraft. Free for small groups.

Playit.gg — the host installs the Playit agent which creates a tunnel and provides a public address. The joining player uses that address to connect. More reliable than Hamachi in many cases and doesn’t require both players to install anything.

Both services sidestep the port forwarding requirement entirely, making them popular solutions for casual friend groups who don’t want to configure routers.

---

Check for LAN World Visibility (Java Edition)

Java Edition allows hosting a local LAN world — opening a single player game to other players on the same network. If you and your friend are on the same Wi-Fi, this is the simplest way to play together without any server setup.

The host presses Escape in their single player world and clicks Open to LAN. Configure the settings and click Start LAN World. On the joining player’s computer, go to Multiplayer — the LAN world should appear automatically in the server list.

LAN worlds only work when both players are on exactly the same network. Different houses, different Wi-Fi networks, or one player on Ethernet and one on Wi-Fi from different routers won’t work — LAN detection doesn’t cross network boundaries.

---

Check Xbox NAT Type for Bedrock

NAT type affects Bedrock Edition multiplayer — a Strict NAT prevents connections with other players who also have Strict NAT, and can prevent some multiplayer scenarios entirely.

On Windows, open the Xbox app and go to Settings → General → Network Settings. Check the NAT Type displayed. Open is ideal. Moderate works in most cases. Strict causes connection failures with other Strict NAT users and some Moderate ones.

Changing NAT type requires router configuration — enabling UPnP in your router settings often automatically moves a Strict NAT to Open without manual port forwarding.

---

Minecraft Realms as the Simplest Solution

If networking issues keep getting in the way, Minecraft Realms is the officially supported solution that sidesteps every networking problem. Realms are Microsoft-hosted servers — no port forwarding, no firewall configuration, no NAT issues. Both Java Edition and Bedrock Edition have Realms.

The host pays a monthly subscription fee and invites friends by username. Invited players join from the Realms menu without needing any IP address or network configuration. It’s the most reliable multiplayer option available for casual friend groups.

---

Reinstall or Repair Minecraft

If nothing else resolves the issue, a corrupted Minecraft installation can cause connection failures that look like network problems. Reinstalling ensures the game files are intact.

For Java Edition, the launcher handles reinstallation — go to Installations, find your version, and use the repair or reinstall option if available. Alternatively delete the version files from the .minecraft/versions folder and let the launcher redownload them.

For Bedrock on Windows, go to Settings → Apps, find Minecraft, and use Repair first. If repair doesn’t work, uninstall and reinstall from the Microsoft Store.

---

A Quick Checklist

Work through these in order:

• Verify both players are on the same version — Java and Bedrock cannot connect to each other
• Check Bedrock world multiplayer settings — multiplayer toggle must be on
• Check Microsoft and Xbox account privacy settings — especially for accounts under 18
• Use the Friends tab on Bedrock instead of manual IP entry
• Check Windows Firewall — allow Minecraft through for private and public networks
• Configure port forwarding on the host’s router for Java Edition direct connections
• Use Hamachi or Playit.gg to bypass port forwarding entirely
• Check LAN visibility if both players are on the same network
• Check Xbox NAT type and enable UPnP if Strict NAT is showing
• Consider Minecraft Realms for a hassle-free permanent solution

---

The Bottom Line

Not being able to join a friend’s Minecraft world almost always comes down to version mismatch, account permission settings, or network configuration. The version check and Bedrock account settings together resolve a significant majority of cases — particularly the Microsoft Family account restrictions that block multiplayer for younger players without any obvious error message.

For Java Edition, port forwarding or a tunneling service like Playit.gg handles the network side cleanly. For persistent connection problems across both editions, Realms eliminates the networking complexity entirely.

Most join failures have a specific cause with a specific fix — check the version first, the account settings second, and the network configuration third.