Bedrock version is constantly disconnected about docker-minecraft-bedrock-server HOT 10 OPEN

Sorry to resurrect this old issue, but it's the only reference I've been able to find to the issue I'm running into. I'm running the itzg/docker-minecraft-bedrock-server image as a StatefulSet on Ubuntu Server with Microk8s. As long as I expose the Service with NodePort everything works great on the port I've assigned. However, I'd like to run it on the usual port 19132, so I'm trying to do it with nginx ingress and UDP stream.

I can connect via 19132 using the nginx ingress addon in Microk8s, however, after just a few moments the Minecraft client will give the "Disconnected from server" error message. It does seem like the issue is Nginx in this case, but I'm wondering if anyone knows of any configuration or setting that could be breaking the Nginx UDP Stream capability with Minecraft Bedrock Server. I've even used Wireshark at this point to see if I can notice anything strange. Wireshark recognizes the Minecraft Bedrock UDP traffic as the RakNet game networking protocol but only shows that after a few moments the server (probably Nginx) stops responding completely while the client continues sending data. Eventually the client determines that the server must have disconnected and displays the message.

I'm mentioning this in the hopes that maybe someone else has solved this issue.

from docker-minecraft-bedrock-server.

It seems like IPV6 needs to be there. How do i do that?

from docker-minecraft-bedrock-server.

If you want to take a look here is the setup. https://github.com/marcusjwhelan/minecraft_docker/tree/master/k8s/prod-azure-multi-pod-node

from docker-minecraft-bedrock-server.

Your issue inspired me to update the example here in the repo to use a StatefulSet. The example works on a Linux server on my LAN using microk8s and there's a few specific things you may want to try in yours:

• set protocol to UDP in container->ports
• set service ipFamily to IPv4

The BDS process also binds IPv6 to 19133, so if your Azure deployment insists on IPv6 then you can add the port bits for 19133 also.

I'm hoping one or all of the above help your setup.

from docker-minecraft-bedrock-server.

@itzg It looks like it still instantly disconnects the server once connected. I am trying to avoid using a load balancer because I am testing out a process to have 1000 or more servers up on one IP. I am using Ingress-nginx.

Any suggestions with that?

from docker-minecraft-bedrock-server.

Tried running this version just with docker or the kubernetes example on my local computer (Windows10) neither worked. The kubernetes version didn't have an exposed IP. I followed the commands and even added a volume for the docker version but no dice.

from docker-minecraft-bedrock-server.

That's strange the local usage didn't work for you. I used:

kubectl apply -f https://github.com/itzg/docker-minecraft-bedrock-server/raw/master/examples/kubernetes.yml
kubectl patch svc bds -p '{"spec":{"type":"LoadBalancer"}}'

and I was able to see the server in "LAN Games" section.

I only use nginx-ingress for the standard HTTP/HTTPS ingress support, so I haven't tried out their UDP extension. That would be the most likely culprit IMHO.

from docker-minecraft-bedrock-server.

@itzg I don't know which version you are using. I am using the Microsoft Minecraft for windows 10. There is no "LAN Games" section I can find. Just servers.

from docker-minecraft-bedrock-server.

Sorry, I lost track of your reply in my other emails. Confusingly enough, the LAN games show up in the "Friends" tab:

from docker-minecraft-bedrock-server.

I'm having a similar issue. I'm although I'm using playit.gg to tunnel my udp and port to play with some friends. After a few hours the game would just randomly disconnect.

I have another game running with playit (valheim), it doesn't disconnect so I now the tunnel client is not the issue. I've tried to reserved the port for game and machine as well. I'm hitting a snag 😂

from docker-minecraft-bedrock-server.