Error since 1.19.50 update

[kr1s]

I cannot connect to a server in azure container instances since the 1.19.50 upgrade. Creating a container using the example az container create --resource-group rg-mine --name minecotainer --image itzg/minecraft-bedrock-server --dns-name-label minesvrbedrock --ports 19132 19133 --protocol udp --restart-policy OnFailure --environment-variables EULA=TRUE

And the container responds to pings but is not connectable. Rolling back to previous 1.18 version and world is connectable

[itzg]

I'm sorry, I don't think there's anything I can do about this. You may want to file an issue with Mojang.

[hatboyzero]

I'm experiencing the same with 1.19.51. Will update here if I happen to find a root cause.

[kr1s]

Thanks all, let me know if I can help in anyway. 1.19.51 server seems to run ok in an Azure VM for me, just not in container.

[itzg]

There does indeed seem to be something weird going on with their networking combined with Docker. Running with Docker Desktop connecting via LAN discovery works, but as a server configured explicitly to localhost it does not.

[itzg]

...nm, my issue was the loopback exemption thing. After determining the correct application identifier and adding exception I was able to connect:

CheckNetIsolation LoopbackExempt -a -n=Microsoft.MinecraftUWP_8wekyb3d8bbwe

[itzg]

If it helps for debugging the networking on Azure, here's a dissection of a wireshark cpature:

https://gist.github.com/itzg/73f615136bd0fee77dd3a654ef466b8d

[fuog]

having the same problem runing on local kubernetes 1.25, k3s (some Debian nodes with containerd ) it worked until recently. the funny thing is: only PC and Linux (androd version) have this issue. Our switch (with DNS-Override of featured-servers to self hosted) does work