Lodehost
"That player does not exist": why /whitelist add fails for Bedrock players
/whitelist add MossyOtter fails with That player does not exist because a Java server looks every name up among Java Edition accounts, and a Bedrock player signs in with an Xbox account that is not on that list. The whitelist itself handles Bedrock players fine. It just cannot find them by name.
There is a worse result than the error. If a Java player somewhere owns the name MossyOtter, the command succeeds and whitelists that stranger. Your friend still cannot get in, and you have let in someone you never meant to.
Floodgate gives every Bedrock player two things a Java server understands: a name with a dot in front, .MossyOtter, and a UUID built from their Xbox ID. That UUID always starts with 00000000-0000-0000, which is how you spot a Bedrock player in whitelist.json:
whitelist.json, one Bedrock player
[
{
"uuid": "00000000-0000-0000-0009-01ff240c1915",
"name": ".MossyOtter"
}
]The server checks the UUID when someone joins; the name is only a label. To build that UUID you need the player's Xbox ID, and looking it up is exactly what Floodgate's command does.
Floodgate whitelist command: fwhitelist add and remove
fwhitelist add MossyOtter looks up the Xbox ID behind the gamertag at GeyserMC's Global API and puts the player on the normal whitelist with the right name and UUID. fwhitelist remove takes them off again.
Console; in game, as an operator, start with /
fwhitelist add MossyOtter
fwhitelist add "Mossy Otter"
fwhitelist remove MossyOtterA few details save you a second try. The dot is optional: Floodgate removes its own prefix before the lookup, so fwhitelist add .MossyOtter works too. A gamertag with a space goes between quotes. In game you need the permission floodgate.command.fwhitelist, which operators have by default. And instead of a name, the command also takes a Bedrock player's UUID.
| What Floodgate answers | What it means | What to do |
|---|---|---|
MossyOtter has been added to the whitelist! | Done | Make sure the whitelist itself is on |
Nothing has changed. MossyOtter was already whitelisted | The player was already on it | If they still cannot join, check which gamertag they really use |
We were unable to find any existing account with the given username. Try it again later if the account was just created | The lookup has no Xbox ID for this gamertag | Check the spelling, then see the next section |
The Global API is temporarily unavailable | GeyserMC's lookup did not answer | Try again later, or use the join method below |
The given username is too short or too long | The name was empty or longer than 16 characters | Type the gamertag again |
No fwhitelist on a proxy
Floodgate only adds the command on the game server, because Velocity and BungeeCord have no whitelist of their own. On a network, run fwhitelist on every backend server that has its whitelist on.
Floodgate whitelist not working: "unable to find any existing account"
Floodgate answers We were unable to find any existing account with the given username when the Global API has no Xbox ID for that gamertag. The API answers from a cache of players it has already seen, so a friend who has never joined a server through Geyser is often simply not in it yet.
Check the spelling first, spaces included, since a gamertag is not always what people think it is. Then let the player try to join once and run fwhitelist add again. That is enough for some players. We have also seen it fail after a join attempt, and for that case there is a method that skips the lookup completely:
Turn the whitelist off
Type
whitelist offin the console.Let the player join
They connect with the address and the Bedrock port, as usual. Wait until they are in the world.
Whitelist them while they are online
Type
whitelist add .MossyOtter, with the dot. Now that the player is on the server, the normal command finds them by their in-game name and stores the right UUID.Turn the whitelist back on
Type
whitelist on. The player stays, and from now on they can join like anyone else on the list.
Keep the gap short. While the whitelist is off, anyone who knows your address can walk in, so do this when you are at the console and switch it back on straight away.
How to whitelist Bedrock players on Lodehost
On Lodehost you whitelist a Bedrock player in the Players tab without a command: click Add to whitelist and type a dot followed by the gamertag, like .MossyOtter. The panel looks up the Xbox ID the same way Floodgate does and writes the entry into whitelist.json.
When the server is running, the panel reloads the whitelist so the change counts at once. When it is off, the entry is there at the next start. The whitelist itself is switched on in Settings. If the panel cannot find the player, it tells you to check the gamertag and let them try to join once. When that does not help either, use the join method above.
The Floodgate prefix and gamertags with spaces
Floodgate puts a dot in front of every Bedrock name by default and turns spaces into underscores, so the gamertag Mossy Otter plays as .Mossy_Otter. Both are settings in plugins/floodgate/config.yml:
plugins/floodgate/config.yml, the defaults
username-prefix: "."
replace-spaces: trueThe prefix exists so a Bedrock player can never end up with the same name as a Java player, and Floodgate's own config recommends a prefix that is not a letter or a digit for that reason. Leave it as it is. Whitelist and op entries would survive a change, because they go by UUID, but plugins that keep players by name would treat every Bedrock player as someone new.
For the lookup it is the real gamertag that counts, with its space. That is why fwhitelist wants the name in quotes. The Lodehost panel takes either spelling and tries the space first.
Written and checked by the Lodehost team, last reviewed on 7 November 2026.
