"Your version is not supported" when attempting to connect to servers

WIndows 10 Pro server, windows 11 client, iPad client, fresh setup server, nothing connecting, same error. All ports open and all clients on 1.21.100.

My best friend is also getting the same issue. Literally everyone except for her can join. Everyone is on 1.21.100

Server Version: 1.21.100.7
Server Build ID35767061
Server Branch: hotfix_21_u10
Server Commit ID: 98aaa32f94e0440ba67be562ccf07fefefbac0d9

Steps to Reproduce:

1 - Updated server to latest version of Minecraft Server 1.21.100.7
2a - Players logging in via Switch get the indicated error
2b - Players logging in via PC get the indicated error
3a - Switch version is set to 1.21.100
3b - PC Bedrock client is set to 1.21.100

Observed Results:

Switch/PC users get the above message.

Expected Results:

Switch/PC users should be able to join. Prior to this update, they were able to.

I have the same errors

Same issue

Can’t join friend’s server, even though we are both on same version (1.21.101)

Version: 1.21.101.1

Build ID: 36025734

Branch: r/21_u10

Commit ID: f92deb6312eef8b42c22b4c4d1970811bd5bfe51

Steps to Reproduce: 

1.  Run newest dedicated server version.

2.  Attempt to connect from any device.

3.  Observe “Your version is not supported. Unable to connect to world.“

Observed Results: 

Client is unable to connect to server running on the latest version.

Expected Results: 

Client should be able to connect to server running on the latest version.

Note:

This bug should be priority number one, a large majority of bedrock players cannot play multiplayer right now.

Same issue. My friends and I cannot join the server I pay for 😞

Client (Switch) on 1.21.101 and Server 1.21.201.1 now also have the issue. Before it was on 1.21.100

I meant 1.21.101.1 not 1.21.201.1

what os do you have?

Once I logged in directly without starting my server, and the game also showed that.

Having same issue this morning right after upgrading to 1.21.101 on my hosted server.

The issue has not resolved after upgrading to the 1.21.101.1 version of the Minecraft Bedrock Server download

Same, hosted server was updated to 1.21.101.1 without my knowledge. Now Mobile gives this error and PS5 won’t connect at all.

encountered issue with my self-hosted server

Minecraft bedrock version: 1.21.110.24

server version:

same issue, some stuff I found:

build IDs differ on the bedrock server binary, and on the IOS client, not sure if thats meant to be but it is:

bedrock server binary:

Version: 1.21.101.1

Session ID: c16ed244-0e33-4f1f-8298-7627b0372616

Build ID: 36025742

Branch: r/21_u10



Client:

Version: v1.21.101

Build: 36025726
Branch: r/21_u10
Protocol version: 827

I cant update ether anymore as there are both at there latest reaslese as of now

Still not working even after server updated to 1.21.102.1

same problem on console trying to connect to private bedrock server

workaround/fix - server needs a full reset. For some reason there is either an ID or update number issue which despite updating the server doesn't seem to align. Server owner needs to create backup of world, server.properties, world zip or whole server - anything of importance to you. Then reset entire server or delete server and reload. Then load back in backups of previous world and config files server.properties and whitelists etc. Backup is essential before reset.

continuing from above: if renting private server, make sure you download backups to your client side machines. Backups created on server hosting services will be deleted when server is reset. Use FTP to download backups of world files

This fix didn’t work for me unfortunately :c hopefully it works for others.

:c try creating a completely new server world just to check if that works? check the port address too, try different ones

remember to start your server after resetting, I forgot to

I changed which port I was using to connect to my server and it fixed the issue C:

My PC connects to my ububtu/docker Minecraft server just fine, but my daughter's switch will not. It receives the reported error message. Server/PC/Switch all running same version. Worked perfectly before this update

We are 6 people in total playing on my BDS. 5 of us can join easily and the last one always gets a message saying this.

Anyone found a solution?

@Tobizon I just switched to Endstone (nukkit fork) and it works fine now

see above comments for work around? what platform is the 6th person connecting via,

This is my situation: 1 of us on switch. 1 of us on Xbox and 1 of us on iPad. The one with the switch or iPad always gets this message.

Experiencing this again on PC after the update yesterday

Any update mods? It has been ages since I could last play with friends on our hosted server.

This was the information from my Survival server:

Survival
Version: 1.21.100.7
[2025-08-29 18:49:18:178 INFO] Session ID: 28d8b4a1-b5de-4d4e-bc53-7166b9664bb7
[2025-08-29 18:49:18:178 INFO] Build ID: 35767061
[2025-08-29 18:49:18:178 INFO] Branch: hotfix_21_u10
[2025-08-29 18:49:18:178 INFO] Commit ID: 98aaa32f94e0440ba67be562ccf07fefefbac0d9

This is after I updated survival today:
Version: 1.21.102.1
[2025-08-29 19:15:31:573 INFO] Session ID: e27fb2a4-b23e-4f13-a67a-401d8cc7bc10
[2025-08-29 19:15:31:573 INFO] Build ID: 36160546
[2025-08-29 19:15:31:573 INFO] Branch: r/21_u10
[2025-08-29 19:15:31:573 INFO] Commit ID: 468d0e14b95e8c003f79d1a82cdaa729522efab6

Still no change.

I spun up a new server without anything from the old one to see if the Switch would connect.

Version: 1.21.102.1
Build ID: 36160546
Branch: r/21_u10
Commit ID: 468d0e14b95e8c003f79d1a82cdaa729522efab6

Same error message.

I tried to change the port, with no effect on the Switch being able to connect.

This is still an issue.

Followed same steps as you Megan. I tried to connect to server via wan and lan and still not working.

I found something out. When you enter wrong IP or port, this message also pops up even though it doesn’t exist at all. Like it pops up instead of “Server not found”. But I found no solution for that. Maybe that can slightly help

Here I attached a video that shows joining to a completely made up IP and port. It say the same instead of “Server not found”. Normally (when the IP and port exists) it just joins me to the server without this message. So it’s problem in searching for the server or just wrong IP or port

I have the same issue. Server version is 1.21.102 and the Xbox and iOS clients are version 1.21.101. I can’t play on my server.

I’ve got the same issue as Jeff. Latest server version is 1.21.102 and latest client is 1.21.101. For some reason the local pc that hosts the server can join even though the client is at v1.21.101. I’ve tested 3 clients: 2 windows on same wifi and IOS on wifi and cellular with the same version not supported error. After letting this version mismatch go on for weeks and no official auto updates to match the client version, it seems like Mojang doesn’t want to support their free servers so a family can play together. I even tried rolling back the server to v1.21.101 but no luck possibly due to opening my world in 1.21.102 and not having a 1.21.101 world backup. That’s just a symptom though. Mojang shouldn’t have uploaded 1.21.102 server without a 1.21.102 client. This should be a simple fix and the top priority since many people can’t play on their small home servers.

Most likely unrelated but worth mentioning; I have Ubuntu installed as a WSL on the windows 11 host server. The bedrock server is running under windows. The server worked fine with this setup before the 1.21.102 update.

For everyone who noticed the server version is 1.21.102 and the client is 1.21.101: it doesn’t matter, we are playing 5 people on that server and it runs without any problems (except the 6th player cannot join due to this reported bug)

So that the server and client version is different is NOT the reason why this bug occurs

Try creating an entirely new instance of the server, a fresh install and fresh world to see if you can connect to that. What nations are people connecting from?

Canada here. And all of us are in the same house.

I did do a fresh world and didn't even import anything from the old one. I still got the same message.

It looks like some clients cannot find the private servers, it has somehow disabled to join the local private servers

I was having this issue with Linux Bedrock 1.21.101 and 1.21.102 using my Android phone connecting with 1.21.101 as well as the Linux Minecraft Launcher on my CachyOS desktop. It was persistent every time I tried to connect to my server using the LAN IP address.

This morning I created a new directory and ran a fresh version of 1.21.101, and the unsupported error continued happening. On a whim I updated my client to connect to the local hostname instead of the IP address (i.e. MSIB550.lan instead of 192.168.0.5) and that allowed my client to connect.

Well it looks like my success was short lived and I think I know why. After closing the client and attempting to connect a second time, the unsupported error began showing up again. I tried to delete the manually added server in my client and creating it fresh would solve the issue but it did not. My windows client is able to connect to this server just fine and always has been able to (it is not using the LAN IP address).

The linux server running my local world has multiple IP addresses on two connected ethernet ports. My firewall can see all of these and associates each IP with the hostname from my previous post (msib550.lan). I believe my initial success was not due to the fact that I used a local hostname instead of an IP but instead that the “round robin” nature of how that hostname resolves with my firewall DNS server meant that I just so happened to randomly “get” the IPv4 or IPv6 address the server was actually using.

So my next test was to go through each IP on this server to see if I could connect. Even though I avoid using IPv6 on my network, one of the two IPv6 assigned to the addresses reliably let me connect on port 19133. In addition one of the IPv4 addresses assigned to my server worked with 19132. That IP just so happend to not be the one I generally use as the primary address when connecting to local services.

It seems like the Minecraft Bedrock Linux server is finding one local IPv4 and one local IPv6 address to bind to and is not binding to any of the others. I believe this means the server.properties file needs a feature added to let us define which local IP to bind to for both protocols.

I find it very interesting that when I run “netstat -na | grep 19132” on my linux machine it shows that the port is supposedly bound to all local IP addresses. That is obviously not happening or I would be able to connect when my client specifies 192.168.0.5 as the server address.

~ netstat -na | grep 19132

udp        0      0 0.0.0.0:19132           0.0.0.0:*    

So how can other server operators see if this approach will work for them? My advice is to open a console on the system you run bedrock server on and list all of the IP addresses tied to your local network. With Ubuntu you can type “ip addr” in the console and it will spit out a list of every address associated with your system. This is going to include a lot of output and not all of it is relevant.

If your local firewall/gateway hardware has DNS running on it and your system is setup to use it, you could also just run “nslookup hostname.lan” or “nslookup hostname.local” (depends on how the local network DNS is setup – change “hostname” to the name you gave to your system when you set it up). nslookup should print a list of every IP your router considers related to your system. You can try each one in the client to see which ones will connect.

I succeeded in the following ways.You will need to exempt the Minecraft client from UWP loopback restrictions:CheckNetIsolation.exe LoopbackExempt -a -p=S-1-15-2-1958404141-86561845-1752920682-3514627264-368642714-62675701-733520436