Fix "Unable to Connect to World" on Minecraft Bedrock

"Unable to Connect to World" is Bedrock's one-size-fits-all failure screen, and the thing behind it far more often than a bad address or your NAT type is a Microsoft privacy setting called "You can join multiplayer games" that has to read Allow before the game will connect you to anything. Check that toggle first, then work down the list below in the order these actually fail: account, then app version, then the address itself, then your network, instead of guessing at NAT or ports the way most guides start.

One screen, five different problems

The reason this error is so annoying is that it never tells you anything. There's no error string under it, no code, just the same blank line whether the address is wrong, the port is wrong, your version is behind, your account is blocked, or your network is dead. Five different problems, one screen. So you don't fix it by reading the message. You fix it by odds, working through the causes from most common to least, and that ordering is the whole point of this post. If you'd rather diagnose strictly by elimination, ruling out address, then network, then DNS one layer at a time, the deeper companion is Bedrock can't connect with no error; this one is the "fix it in order of likelihood" version.

Before anything else, run the fast triage move: add a second server you already know is online and try connecting to that. If the known-good one loads, your device, network, and account are all fine, and the fault is the first server's address, port, or version. If the second one fails too, the problem is local, and you live in the account and network sections below. Grab a clean, currently-populated address from the live rankings on the homepage or the full server list, and confirm it's actually up first. A quick status check before you join saves you from blaming your own setup for a server that's simply offline.

Start with the privacy toggle: the usual culprit

This is the number one fix, and most people never touch it. The setting is "You can join multiplayer games", and it has to be set to Allow. You change it at account.xbox.com, under Privacy & online safety > Xbox/Windows online safety, not anywhere inside Minecraft itself, which is why so many people bounce off this. While you're there, flip "You can play with people outside of Xbox" too, because most Bedrock servers are crossplay and that toggle gates them.

After you change either one, sign out of Minecraft and back in so the game actually pulls the updated permissions; it won't re-check on its own mid-session. Give it time to propagate, usually a few minutes, sometimes an hour or two, and once in a while close to a full 24 hours before it sticks.

Child and family accounts are their own case. Both toggles are off by default, and only the family organizer can change them, over at account.microsoft.com/family. If it still refuses after the organizer allows both, the account's birthdate is the likely culprit: a birthdate that puts the profile under the child threshold can force child-account limits no matter what the toggles say. The Xbox account rules for Bedrock servers walk through both toggles and the age logic in full.

Then confirm you're actually signed in

Second most common cause, and just as easy to miss: you're not signed in. Your gamertag has to show on the main menu. If it doesn't, external servers are flatly refused, and the only multiplayer you'll get is LAN games on your own network. Every Bedrock platform authenticates through Xbox network services: Windows, Xbox, PlayStation, Switch, Android, and iOS. The account itself is free.

If sign-in looks stuck, sign out and back in, and when you do, pick "Save to Microsoft Account" so it actually persists. On mobile specifically, sign in from the main menu before you open the server list, or the list won't populate and every entry throws the blank error.

Version, address, and port: the silent misses

Further down the list, but they catch people. A version mismatch on Bedrock often shows up as exactly this blank error, no text at all. If the connection got far enough to compare builds, you'll instead see "This server is not compatible with your current version" spelled out, but plenty of mismatches never get that far and land on the same empty screen. Check your version in the bottom corner of the main menu, next to the Play button. There's no in-game update button on Bedrock (it updates through your platform's store or console), so update there and then relaunch the game fully before you retry.

The address and port are the other silent miss. Re-copy the address instead of typing it. One wrong character fails silently with no warning: a capital O standing in for a zero, a trailing space you can't see, a lowercase l for a 1. Bedrock also splits the entry into two separate boxes, Server Address and Port, and people leave the port wrong or blank all the time. The default Bedrock port is 19132. A Java-only address running on 25565 will never connect from Bedrock at all unless that server bridges both editions with crossplay. If the two-field layout trips you up, the add-a-server walkthrough for Bedrock covers it step by step, and edition-mismatch cases are worth checking against the crossplay server list.

When it's your network, not the server

Lower frequency than the account stuff, but real, and worth a pass once the toggle and sign-in are confirmed. Restart the app first. That alone clears a surprising share of mobile blank-connects. Then restart the router and modem, and toggle Wi-Fi off and on. The cleanest test is a different network entirely: try your home Wi-Fi versus a phone hotspot. Works on one and not the other, and you've pinned it on your router or ISP rather than the game.

NAT Type is the setting to check next. It's under in-game Settings > Network, and you want it reading Open. If it says Strict, Moderate, or Double NAT detected, that's actively blocking connections, and you fix it at the router: turn on UPnP, or manually forward UDP 19132. On Windows, also make sure Minecraft is allowed through the firewall. I'm keeping the DNS and IPv6 side deliberately thin here, because it's a rabbit hole: the short version is that IPv6 can resolve to the wrong port while Bedrock Dedicated Server listens on 19133 for v6, and switching your DNS to 1.1.1.1 sometimes clears it. The full mechanics live in the no-error companion post so this one doesn't re-run them.

On console, "Add Server" may not exist at all

Here's the platform blocker no Java-focused guide bothers to mention: on Xbox, PlayStation, and Switch, you often can't add a server by IP at all. By default those consoles only show Microsoft and Mojang "featured" servers, so a missing Add Server button, or an entry you add that simply never appears in the list, is expected behavior — not a bug. Re-copying the address a tenth time won't fix a restriction that isn't about the address.

The easiest way to prove this to yourself is to add and test the exact same server on a phone, tablet, or Windows PC first. If it connects there, the address is fine and you've isolated the block to the console itself. For the Xbox-specific side of this, the why you can't add a server on Xbox writeup goes deeper. There's an external DNS-based workaround called BedrockConnect floating around, but it changes often and sits outside what I'd rely on here, so I'll only note that it exists.

FAQ

I flipped the toggle and it still won't connect, is it broken?

Check which app you're running. If you're on Minecraft Preview, the Bedrock beta client, it runs ahead of the retail release, so its version won't line up with a normal server even when your account is perfectly fine. Switch to the regular Minecraft app and try the same address. Otherwise, give the permission change more time, since child-account changes especially can take hours to propagate.

Do I need Xbox Game Pass or PS Plus to join a Bedrock server?

No. The console's paid online membership is a separate thing from the free Microsoft account, and third-party Bedrock servers only care about the account plus the multiplayer privacy toggle, not the subscription. You sign in with the account, allow multiplayer, and connect. The paid tier matters for other online features, not for reaching a community server.

Does the screen ever fix itself if I just wait?

Sometimes, yes — but only for two causes. If the server is restarting, or a child-account permission is still propagating, waiting a few minutes genuinely resolves it. Look at the saved-server card's signal color before you keep retrying: grey or red means it's offline right then, so wait. If it's showing a live ping and others are clearly on it, waiting isn't your fix and you're back in the account section.

My friend connects to the same server on the same Wi-Fi, but I can't.

The privacy toggle is per-profile, so a second profile on the very same console can be blocked while the first one connects fine. Check that profile's own "You can join multiplayer games" setting. If both accounts are genuinely set up identically and only one connects, the split is usually a single device carrying Strict or Double NAT type while the other sits on a cleaner path to the router.