[BDS-18536] Not invited to play on server, but on the allowlist.json

I have a hosted BDS server and I have players whitelist/allowlisted within the alllowlist.json file, but the issue I'm seeing is if the don't have their XUID within the file they are unable to connect to the server. Usually, to my knowledge, the allowlist.json auto-populates the XUID information after the first connection made by the player without that in the file. This isn't happening because it tells them they are not invited and blocks that connection.

Microsoft/Xbox gamertags are correct and cased correctly, so that's not the issue. It was doing it to me in testing with correct casing.

Comments 18

migrated 2023-07-13T08:59:47Z

Can they connect when you add them via "whitelist add Gamertag" server console command?

This ticket will automatically reopen when you reply.

migrated 2023-07-15T00:31:13Z

They cannot. If I add someone fresh they get the "not invited to play" message. However, when I add their XUID manually, they are able to connect without issue. Seems like whatever gathers the XUID information upon the users first connect, isn't and preventing the user from joining with that message.

migrated 2023-07-15T12:30:46Z

Just had it happen again. Let one without an XUID within the allowlist.json stay since they were off for a few weeks and before this update it would have allowed them on and then added their XUID into that file, but it said they weren't invited and never added their XUID. I then pulled there XUID # from a website, added it to the allowlist.json into the file and it allows them to connect without issue.

migrated 2023-07-15T13:04:33Z

Guess for replication, add a user through the console and have they try to connect, it will tell them that they are not invited, even know Xbox Gamertag is correctly put and cased as it needed for be.

For example, my Xbox gamertag is "IRL Dave" so I'll so whitelist add "IRL Dave" (since I have a space in my name I need to use quotes), it will add the line {"ignoresPlayerLimit":false,"name":"IRL Dave"}, to the allowlist.json. When I try to connect, I'm not invited. Manually update the allowlist.json to include my XUID to appear like this: {"ignoresPlayerLimit":false,"name":"IRL Dave","xuid":"2535458138542642"}, on that line, and I'm able to connect without issue.

So somewhere in that Online mode player authentication, where it would usually add the XUID, it is not, and in turn it is blocking their connection by saying they are not invite to play, until their XUID is manually put it.

silentwisperer 2023-07-16T23:03:07Z

can confirm for 1.20.11. Severely affecting our servers where we have hundreds of people whitelisted.
even if a player is the ONLY thing in the whitelist file they cannot join. It's seriously busted.
if they are in the file and can't connect you need to make sure their xuid is there and/or remove from whitelist using the console command "whitelist remove name" then "whitelist add name" and sometimes that'll work.

8 more comments

migrated 2023-07-17T02:23:21Z

Adding to this. This happened yesterday on a server I help to admin. Confirming that XUIDs need adding to the allowlist. Furthermore, even with the XUIDs added, players were still receiving “Not invited to the server” until the allowlist.json was flattened and the XUIDs were made a string.

For additional information, the server I help to admin uses Nodecraft for server hosting.

migrated 2023-07-17T02:24:27Z

This only way I and and another server I was talking with got our allowlist.json working has is it was flattened and one entry per line:

[
{"ignoresPlayerLimit":falce,"name":"Player 1","xuid":"###############"},
{"ignoresPlayerLimit":false,"name":"Player 2","xuid":"###############"},
{"ignoresPlayerLimit":false,"name":"Player 3","xuid":"###############"}
]

That doesn't display the format right on this post, but just one entry per line and so on and MUST include the XUID if not known, I've had to look them up.

migrated 2023-07-27T12:17:18Z

Did this issue occur for you on Windows or Linux BDS?

This ticket will automatically reopen when you reply.

PlodPlod 2023-09-04T11:19:32Z

Hi, I have the same issue.

The answer is no, using the command doesn't solve the issue. It had the effect of:

adding the new player without their XUID (so they still can't connect as the XUID is missing)
deleting all the other players in the allowlist.json file that don't have an XUID specified

To make matters worse, the public service most people used to obtain XUIDs has now closed so it's now almost impossible to add new players to BDS servers, or for existing players without an XUID in the allowlist.json file to play on the server.

As far as I know the only way to obtain an XUID now is for the player themselves to visit their xbox.com profile and search for "xuid" in the page source.

migrated 2023-09-18T09:06:26Z

Does this issue still occur after updating to 1.20.15?

This ticket will automatically reopen when you reply.

PlodPlod 2023-09-18T17:59:24Z

Yes, I tried with both the server and client on 1.20.15 and the issue persists.

migrated 2023-09-28T10:47:40Z

Can you please verify if issue still occurs after updating to 1.20.31? Im unable to reproduce it, after adding player via console i can connect without issues and XUID adds automatically.

This ticket will automatically reopen when you reply.

PlodPlod 2023-10-21T12:29:39Z

I've now upgraded the server to 1.20.32.03 and had the same problem again. In particular, when editing allowlist.json manually or using our host's control panel, the new player could not access the game.

Similarly when I used the console command whitelist add [name] the player could not join - BUT if I run allowlist reload afterwards it seems to have the desired effect.

So it seems the bug is still there but reloading the allowlist before they attempt to join seems to act as a workaround.

migrated 2023-10-23T12:44:12Z

Do you use Windows or Linux BDS?

This ticket will automatically reopen when you reply.

PlodPlod 2023-10-24T08:50:51Z

Linux - hosted by Nodecraft if that helps.

migrated 2024-01-08T12:59:08Z

Hi!
XUID is generated after the user selects and validates their gamertag. This site allows to show xuid for specified gamertag: https://www.cxkes.me/xbox/xuid.
Please do these steps:

Fill allowlist.json manually with xuids and let us know if players are able to enter server after this step is done?
Be sure firewall does not block the server and Minecraft on both sides
Be sure Minecraft license is added to the Account that wants to connect to server

This ticket will automatically reopen when you reply.

migrated 2024-02-14T18:53:08Z

Can confirm it is still doing this on 1.20.60.1

I'm running the server on Windows 11

I have other users on the server who connected previously and it populated their XUIDs when they first connected. Now new users get "Not invited" unless their XUID is populated.

kiizde 2024-05-14T16:14:07Z

Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki