Mine has updated to version 1.21.100.
My PC is on this version, and so is my phone.
When you download the server from the official website, it comes at 1.21.100.7.
So, when I log in from my phone, it works, but when I log in from my PC, it says the version is incompatible.
Linked issues
is duplicated by 29
BDS-22820
Latest BDS says 1.21.100 is incompatible.
Resolved
MCPE-226314
Unable to join world
Resolved
MCPE-226300
"Version not supported" despite both server & player being on same version
Resolved
MCPE-226351
Can't join minecraft servers because of "unsupported version" even though it is supported
Resolved
MCPE-226427
Can’t log into multiplayer server
Resolved
Attachments
Comments 52
I’m having the same issue, this is my info:
Build ID: 35767063
Branch: hotfix_21_u10
Commit ID: 98aaa32f94e0440ba67be562ccf07fefefbac0d9
same issue when installing brand new linux based bedrock server.
seems like up to date server is running on 1.21.100.7 whilst all other up to date clients are running on 1.21.100
Steps to Reproduce:
1, download Minecraft Dedicated Server Software for Ubuntu (Linux)
2, set up using default settings including port forwarding so its accessable via wan
3, try connect to server and encounter version issue
Observed Results:
when connecting to server other WAN get a unsupported version error. however when connecting via lan i have no issues
Expected Results:
Connect with no issues
Version: 1.21.100.7
Build ID: 35767061
Branch: hotfix_21_u10
Commit ID: 98aaa32f94e0440ba67be562ccf07fefefbac0d9
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
Still having this bug with my minecraft bedrock server. Weird how it seems to work for some people but not for others. Can't connect locally or publicly still and server was working before client update 1.21.101. Java server still works fine java clients can connect but bedrock players can't even tho I'm running a mcpaper/spigot server.
Hi!
Thank you for your report, however, this issue has been temporarily closed as Awaiting Response.
Could you please provide more details or/and media files. As such we have no repro of this issue.
Can you provide the server’s Build ID, Branch and Commit ID? You can find it in the console after the server have been opened.
Also, just a reminder, to make your bug report as effective as possible, please try and include the following steps to reproduce the problem:
Steps to Reproduce:
Observed Results:
(Briefly describe what happens)
Expected Results:
(Briefly describe what should happen)
If your ticket does not look like the this example, then it's likely to be closed as incomplete.
This ticket will automatically reopen when you reply. Thanks!
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki