Fixing "Unable to Connect to World" on Bedrock (No Error Message)

Bedrock gives you almost nothing to work with when a connection fails — just "Unable to Connect to World" on a blank screen, no error code, no hint about what went wrong. Java at least tells you "Outdated client" or "you are not whitelisted" so you know where to look. On Bedrock a bad address, a wrong port, a version mismatch, a blocked account, and a network problem all land on that one identical message, so you're left guessing which of those it is.

This covers both sides of Bedrock: phones and tablets, and the consoles (Xbox, PlayStation, Switch). Consoles matter because they have a blocker that no Java troubleshooting guide will ever mention, and it's the reason a lot of console players think the game is broken when it's actually working as designed. The fixes below run from the most common to the most platform-specific, so you can work straight down the list instead of poking at random settings. If you're not fully sure how the add-server flow works in the first place, the full walkthrough on joining a server covers the basics for both editions.

Why Bedrock gives you a blank error

The screen says the same thing no matter what's wrong. All of those failures end at "Unable to Connect to World" with no code attached, so the message itself can't tell you which one you've hit. That's not a bug, it's just how Bedrock reports failures, and it's why you diagnose it by elimination instead of by reading the screen.

There's one quick check worth doing before anything else. Add a second server you know is online — grab one from the server list — and try to connect to that. If the second one loads, your device, network, and account are all fine, and the problem is specific to the first server's address, port, or version. If the second one fails too, the problem is on your end, and you'll spend your time in the network and account sections further down rather than re-checking an address that was never the issue.

Start here: address, port, and version

Re-copy the address from the listing instead of typing it. Bedrock fails silently on a single wrong character, so a capital O where there should be a zero, or a stray space on the end, gives you the same blank error as a server that's genuinely down. Every entry on bestminecraftservers.gg shows the exact address and port to copy, which takes the guesswork out of it.

The port is where Bedrock trips people up, because it splits Server Address and Port into two separate fields. The default Bedrock port is 19132, and it's filled in for you. If the listing names a different port, that number has to go in the Port field — if you leave 19132 sitting there while the server runs on something else, the game is trying a port the server isn't on, so it just times out.

Edition is the other thing to confirm. A Java-only address running on port 25565 will never connect from Bedrock, no matter how carefully you type it, because the two editions don't speak to each other directly. Check that the listing actually supports Bedrock, or that it's a crossplay server bridging both. The crossplay servers list is filtered to servers built to accept Bedrock clients alongside Java, so that's the safest place to pick one if you've been guessing.

Version is the sneaky one. On Java a version gap reads "Outdated client," but on Bedrock that same mismatch often shows up as the blank error with nothing to tell you that's what happened. Bedrock updates itself through the app or console store, so if your app is mid-update, or the server hasn't moved to the latest version yet, connections fail quietly. Make sure the app has finished updating and relaunch it fully before you assume the server is the problem.

Network fixes on phone, tablet, and Windows

Restart the app first. On mobile especially, just closing Minecraft fully and reopening it clears a surprising share of these blank-connect failures — it's worth doing before you touch anything more involved. Then restart your router or modem, which clears a stale connection or a cached DNS entry, and toggle Wi-Fi off and back on so the device picks up a fresh route.

DNS is the cause most people never think to check, and it's a real one on Bedrock. Your device can resolve a server's hostname to an IPv6 address and then try to reach it on port 19132 over IPv6 — but a Bedrock Dedicated Server uses IPv4 on 19132 and IPv6 on a separate port, 19133, by default. When that lines up wrong, the connection just times out with no error. Switching your device's DNS to a public resolver (Cloudflare's 1.1.1.1 is the common pick) often forces a working route. It won't fix every server, but it's a cheap thing to try when a specific server fails for no visible reason.

To find out whether your network is even the issue, connect your device to a different one. Switch from home Wi-Fi to a mobile hotspot, or the other way around, and try the same server. If it works on one network and not the other, the problem is your router or ISP, not the server. On Windows, there's one more thing: firewall or security software can block Minecraft without saying so. If every server fails on a Windows PC, allow the app through your firewall before you go further.

NAT type and Xbox account settings

Open the in-game Settings → Network menu and look at NAT Type. You want it to read Open. If it says Strict, Moderate, or Double NAT detected, that's blocking a lot of connections, and the fix is at your router — enable UPnP, or forward UDP 19132 to your device. This is about your own connection out to servers, not about hosting anything, so it's a router setting and nothing more.

Bedrock multiplayer is also gated behind a Microsoft account setting, and when it's switched off you get the same blank error as a dead server. 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. People hit this constantly without realizing a privacy toggle is the thing standing between them and every server they try.

Child accounts add a wrinkle. A parent or family organizer has to allow multiplayer in the Family safety settings, and the part that throws people is the delay: the change can take hours to propagate across Microsoft's services — in some documented cases close to 24 hours. So if you flipped the setting and it still won't connect, that doesn't mean the fix failed. Wait and retry later. And on any account, signing out of your Microsoft account inside Minecraft and back in (choosing "Save to Microsoft Account") can clear a stuck sign-in state that's quietly blocking you.

The console blocker Java guides skip

The console restriction is the big one, and no Java guide mentions it. On Xbox, PlayStation, and Nintendo Switch, Bedrock does not let you add a server by IP or address at all by default. These consoles can only join the Microsoft and Mojang "featured" servers listed in the Servers tab — there is no built-in Add Server option for a third-party address. That's a platform restriction, not a fault with the server or your setup.

So if you're on a console and there's no Add Server button, or you add the server and the entry simply never appears, you're not looking at a bug. The blank error or the missing entry is the expected behavior. No amount of re-copying the address or restarting the app changes it, because the console was never going to let that address in to begin with.

There is a known community workaround — it involves changing the console's DNS so an external connector service lists third-party servers, with BedrockConnect being the usual name people mention. It's a third-party setup done entirely outside the game, it changes often, and it's beyond what we'd point you at here. Worth knowing it exists, but it's not something to follow step by step from here.

The easiest path, if you've got the option, is to add and test the server on a phone, tablet, or Windows PC first, where Add Server works normally. Confirm the address and port actually connect there, and you've ruled out everything except the console restriction — which tells you the server is fine and the limit is the platform, not you.

Confirm it's the server, not you

The saved-server screen tells you a lot before you even connect. The live ping and player count are right there, and a grey or red signal means the server is offline or restarting at that moment. Wait a few minutes and retry rather than tearing through your own settings for a problem that's on their end.

Cross-check the server's uptime and current version on its listing too. A server that's mid-restart, or one that updated to a new version recently, can refuse connections for a short while until it settles. That's temporary, and it's not anything you can fix from your side.

If several servers you know are good all fail, stop chasing addresses — the problem is local, and it's one of the things from the earlier sections: network, NAT, DNS, or account privacy. Loop back and work through those. And when you're picking a server to test against in the first place, use the live monthly rankings and the category pages to find one that's clearly online and populated. Troubleshooting against a dead or empty server just wastes the time you spend on it.

FAQ

My friend can connect but I can't, same server — what's different?

It's almost always your account or your home network, since the server is clearly accepting them. Check the "You can join multiplayer games" permission on your own Microsoft account first, then your NAT type. If you're on the same Wi-Fi as your friend and only you fail, a single device having Strict or Double NAT is the thing that splits two players on one network like that.

Where do I actually see my Bedrock version number?

It's printed in tiny text in the bottom corner of the main menu, on the same screen as the Play button. Match that against the version on the server's listing. There's no in-game "update" button — Bedrock updates through your app store or console store, so if the numbers don't line up you update there and relaunch, you don't patch it from inside the game.

Do I need to buy anything beyond the game to join a server?

No. A normal copy of Minecraft is all it takes to join any public server in this directory — you add the address and connect. There's no separate purchase or pass involved in getting onto a listed server.

Does the "Unable to Connect" screen ever fix itself if I just wait?

Sometimes, yes — if the cause is the server restarting or finishing an update, or a child-account permission still propagating, retrying in a few minutes (or later, for the account case) connects you with no other change. If a retry minutes apart keeps failing and the saved-server screen shows a live ping and players for everyone else, the wait isn't the answer and it's worth working back through the address, port, and account steps.