Fix "You Are Not Whitelisted on This Server" in Minecraft

That kick screen — "You are not whitelisted on this server" — means your exact account name was never added to the server's list of approved players, and that's the whole story. It isn't a bug or a crash, and it isn't a ban. The server's up and your version and network are fine — if any of those were off you'd get a different message. The only thing wrong is that your account isn't on the list yet.

So the fix here is social, not technical. There's nothing on your machine to repair — you confirm the right username and edition, then get one of the server's operators to add you. If you want the concept behind all this, what a whitelist is and why so many SMPs run one, what whitelisted means and how to get added covers it.

Decode the message: what it is and isn't

On Java the exact line, in red on the disconnect screen, is "You are not white-listed on this server!" — Java writes it with a hyphen, and most people retype it without one as "you are not whitelisted on this server." Same message either way. Bedrock refuses you the same way; it just keeps the list in a file called allowlist.json instead of whitelist.json, and the wording and tooling differ a little behind the scenes. As a player you can't tell the difference, because you get bounced at the join.

It helps to know what this message is not, since people often land here when they're actually hitting something else. A ban reads "You are banned from this server" and usually comes with a reason attached. A version mismatch is the one that says "Outdated client" or "Outdated server." And a server that's genuinely down won't even let you click join — you'll see a grey or red connection signal next to it in your multiplayer list first. If you're not sure which one you're getting, how to join a Minecraft server walks through the other connection errors. But if the words say "whitelisted," there's nothing to troubleshoot on your end, so move straight to confirming your name.

Step 1: Confirm your exact current username and edition

The single most common reason for this kick is a name that doesn't match. The operator added a username, but not the one your account actually connects with, so the list never lines up with you. Give staff your current username, character for character, copied rather than typed from memory. On an online-mode server the add command resolves that name to your account, but if a typo or an old name got handed over, they've approved the wrong account, or no account at all.

Edition is the trap beginners miss. A Java username and a Bedrock gamertag are two separate identities, not two spellings of the same one. Send a Bedrock gamertag to a Java server, or the reverse, and you'll be added to a list that can never match the account you log in with. Always give the username for the edition you actually play on.

Quick self-check: open your launcher or account screen and copy your name straight from there, then confirm that exact string is what the owner has. That one habit clears most of these kicks before they start.

Step 2: Why a recent name change can lock you out

Normally a rename is fine. On an online-mode server — the standard for any listed server — approvals are keyed to your account's UUID, not the text of your name, so changing your username keeps your access automatically. You don't need re-adding.

The trouble starts in a few specific cases. If you or the owner used your old username when you were added, the entry points at the wrong identity. If it's an older or offline ("cracked") setup that keys off the name text instead of a stable UUID, the generated UUID stops matching the moment you rename. Or you were added a long time ago and the name you remember handing over is stale. Any of those, and the rename can drop you onto this kick screen.

The fix is one line: give staff your exact new username and ask them to re-add it. Don't assume the old approval carried over, especially if you're getting bounced right after a change. And you never run anything yourself here — the whitelist lives with the server's operators.

Step 3: The Bedrock and crossplay gamertag wrinkle

This one is for Bedrock players joining a Java server through Geyser and Floodgate, the bridge that lets the two editions share a world. What Geyser and Floodgate are explains the setup if it's new to you.

Here's why it breaks. A Bedrock player has no Java account, so a plain /whitelist add <name> can fail outright — the classic "could not request xuid" error — or quietly store the wrong entry. Either way you stay kicked while the owner thinks they added you. Floodgate has its own command for exactly this, and the owner runs /fwhitelist add <bedrock_gamertag> instead. Two naming quirks are worth flagging so the add actually matches you. Floodgate puts a "." in front of Bedrock names by default, to keep them from colliding with a same-named Java player, and it swaps spaces in gamertags for underscores, so "Steve Builder" goes in as Steve_Builder.

So tell the owner up front that you're on Bedrock, give them your exact gamertag, and ask them to use the Floodgate command rather than the plain whitelist one.

Step 4: The exact thing to ask the owner to do

Start by finding the server's published join process. Whitelisted communities rarely add a stranger on sight — they post an application form, a Discord, or an in-game request on the listing or a linked community page. Follow it as written. Then hand the owner two things: your exact current username and which edition you play. The command they run is /whitelist add <YourName> on Java, or /fwhitelist add <gamertag> for a Bedrock player on a crossplay server.

A few things about timing. Adding you doesn't require you to be online, and it won't kick anyone already connected. But on a server that's been running a while, the change may need a /whitelist reload before it takes effect. A real person often reads applications by hand too, so approval can take anywhere from a few minutes to a few days, and pestering staff tends to slow that down rather than speed it up.

If you were supposedly added and you're still kicked, it's almost always one of four things: a wrong or old username, the wrong edition, the command never actually got run, or the list wasn't reloaded. Re-confirm your exact current username and edition before you assume anything's broken. One gotcha worth mentioning to the owner, lightly — operators bypass the whitelist by default, so their own account walks straight in even when a non-op friend can't. That's a common reason an owner doesn't realize the list is blocking people; they never feel it themselves. If they want to tighten the whole thing up, how to whitelist a server the right way is for them.

Don't want to wait? Servers you can join right now

For a beginner who just wants to play tonight, an open server is usually the better call — there's no application and no wait, you just connect once you have the address. A whitelist gets you a more vetted community in exchange for filling out a form and waiting for an operator to approve you.

The monthly vote rankings on the homepage and the full server list show open servers with their address, supported version, and live status, so you copy the address and connect with no invite needed. If it's a community-style world you're after, the SMP listings are a good place to look — a lot of them post their join or whitelist steps right on the listing or a linked Discord, so you can find one worth the application before you bother filling one out.

The practical play is to start on an open server, learn what you actually enjoy, and apply to a whitelisted community once you know the kind of place you're looking for.

FAQ

Does it matter if I type my username in capitals or lowercase when I join?

How you type it at the multiplayer screen doesn't matter, because an online-mode server identifies you by your account, not by the casing of the text. What matters is the username the operator enters when they add you, and that it belongs to the right account and the right edition. So the useful thing isn't your capitalization — it's making sure staff have your exact current name for the edition you play. If a name change or an old username is in the mix, give them the new one and ask them to re-add it.