I tried this guide but sadly it did not work.

https://jamesachambers.com/minecraft-bedrock-server-resource-pack-guide/

Hi All,

Hoping someone can help me out.

I generally just use my unraid server as somewhere to store my media files but as my son is having issues with his minecraft games I thought having the server as a backup at home may help.

 

The problem is I have no idea how all these things fit together. His amazon fire tablet wont update minecraft, so i think i need to install an older version of the server (1.21.1). If i can do this and then get his tablet to connect, can i transfer the 520 worlds he cant live without, to the server? Is this the best option or is there another way?

I think what i need to do is backup what i can from his tablet , then do a factory reset, and then re-install the latest version. Then would he be able to access his worlds from the server, or would there be another step in getting the versions to match again?

 

I'm sorry if this question is not in the right place, but thought someone here would be my best bet. Thanks in advance.

help, I created a bedrock server which seems to start up just fine, but on my android phone, it can see the server and have a online status with ping, but connection to it fails with message

 

Unable to connect to world

 

all the docker setting is default other than the web ui password.

 

I also have a java server from binhex which cannot even ping the server locally but can connect remotely, I asked in the unraid forum and end up giving up, but maybe related?

 

I do use pfsense + unify wifi 6 AP, but really doesn't have much complicate settings, no vlan.

 

 

Hi,

 

It appears there has been another build failure with the latest release.

 

https://github.com/binhex/arch-minecraftbedrockserver/actions/runs/11110996214/job/30869951983

6 hours ago, lrussell887 said:

Hi,

 

It appears there has been another build failure with the latest release.

 

https://github.com/binhex/arch-minecraftbedrockserver/actions/runs/11110996214/job/30869951983

fixed up, new image has been built, please pull down.

Is there anyway to allow this app to use my gpu i got a 4090 installed and everything even using it for plex

 

@binhex

Hi,

I entered “gamerule showcoordinates true” in the container variable STARTUP_CMD.
This worked wonderfully so far, but now I get an error message at startup. Can someone please help me?
 

2024-10-27 11:26:04,730 INFO success: start-script entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-10-27 11:26:04,836 DEBG 'start-script' stdout output:
[info] Starting Minecraft Bedrock process...

2024-10-27 11:26:04,866 DEBG 'start-script' stdout output:
[info] Minecraft Bedrock process is running

2024-10-27 11:26:04,867 DEBG 'start-script' stdout output:
[info] Executing startup Minecraft command 'gamerule showcoordinates true'

2024-10-27 11:26:04,869 DEBG 'start-script' stderr output:
*** buffer overflow detected ***: terminated

2024-10-27 11:26:04,870 DEBG 'start-script' stderr output:
/home/nobody/start.sh: line 54:   129 Aborted                 screen -S minecraft -p 0 -X stuff "${startup_cmd_item}^M"

 

42 minutes ago, Skibinator said:

but now I get an error message at startup. Can someone please help me?

i am running the same command on startup and i see the same buffer overflow message, not sure exactly when this started but it seems, for now at least, to not cause any side effects that i have noticed, i shall do some more digging, for now ignore it.

Starting in early October, the container's automatic backup has stopped working.

 

I filed an issue in Github with the details here:

backup script stopped running - "*** buffer overflow detected ***: terminated"

 

I haven't yet tried to debug this, but from some earlier posts it sounds like I'm not the only one.

On 10/27/2024 at 12:18 PM, binhex said:

i am running the same command on startup and i see the same buffer overflow message, not sure exactly when this started but it seems, for now at least, to not cause any side effects that i have noticed, i shall do some more digging, for now ignore it.

Hi, it works with the new version. Thank you! 😊

On 11/3/2024 at 4:45 PM, kmwoley said:

Starting in early October, the container's automatic backup has stopped working.

 

I filed an issue in Github with the details here:

backup script stopped running - "*** buffer overflow detected ***: terminated"

 

I haven't yet tried to debug this, but from some earlier posts it sounds like I'm not the only one.

Please pull down latest, i have a workaround in place for now (the issue is with screen v5)

21 hours ago, binhex said:

Please pull down latest, i have a workaround in place for now (the issue is with screen v5)

Thanks! This resolved the issue.

Heya! I've been using this successfully with my kiddo for some time, but we're starting to run into some performance issues. Is there any way for me to edit/manage core/thread allocations for this container? I have this running on a 32c64t server, but 1 thread is consistently maxing out at a time (it does keep changing, mind you, but very clearly just 1 being maxed while we play) causing a fair bit of lag in the game.

1 hour ago, EposVox said:

Heya! I've been using this successfully with my kiddo for some time, but we're starting to run into some performance issues. Is there any way for me to edit/manage core/thread allocations for this container? I have this running on a 32c64t server, but 1 thread is consistently maxing out at a time (it does keep changing, mind you, but very clearly just 1 being maxed while we play) causing a fair bit of lag in the game.

This is a minecraft limitation sadly, the core of minecraft is single threaded only, thus a lot of people who wish to run minecraft with a lot of users tend to go with processors with high clock speeds as opposed to lots of cores, see here.

Okay I've been going back and forth on Google, forums, and AI chat trying to figure this out but seem to be having issues with UDP connectivity. I had a summary of what I've done so far below. Any help would be greatly appreciated.

 

Minecraft Bedrock Server on Unraid Not Responding on UDP Ports (Host Mode)

 

 

---

 

Environment Overview:

 

Platform: Unraid running binhex-minecraftbedrockserver Docker container

 

Networking Mode: Host mode

 

Server Properties Config (Current):

 

server-port=19135 (IPv4)

 

server-portv6=19136 (IPv6)

 

 

Port Forwarding: Configured on ISP-provided router to forward UDP ports 19135 and 19136 to Unraid.

 

 

 

---

 

Steps Taken:

 

1. Initial Setup on Default Ports

 

Initially tried to use the default Bedrock ports 19132 (IPv4) and 19133 (IPv6).

 

Despite correct router forwarding and open iptables rules, the server was inaccessible externally and locally.

 

Suspecting a conflict with the default ports, switched to custom ports 19135 and 19136.

 

 

2. Networking Configuration

 

Verified Unraid has no restrictive firewall rules.

 

Manually added iptables rules to allow UDP traffic on 19135 and 19136:

 

iptables -A INPUT -p udp --dport 19135 -j ACCEPT  

iptables -A INPUT -p udp --dport 19136 -j ACCEPT

 

Confirmed rules with:

 

iptables -L -n | grep 19135  

iptables -L -n | grep 19136

 

 

3. Server Bind Verification

 

Checked if the Bedrock server is binding to the ports:

 

netstat -tuln | grep 19135  

netstat -tuln | grep 19136

 

Result: Both ports are listed as listening (udp for 19135, udp6 for 19136).

 

 

4. External Port Tests

 

Verified router port forwarding by successfully connecting to a Java Minecraft server on a different port.

 

Used online port check tools, which report 19135 and 19136 as timing out.

 

 

5. Local Testing

 

Installed and ran Netcat inside the Unraid environment (via nicolaka/netshoot container) to test connectivity:

 

nc -u -z 127.0.0.1 19135

 

Result: No response received on the ports.

 

 

6. Bedrock Server Logs

 

Logs indicate the server starts successfully and binds to the correct ports:

 

IPv4 supported, port: 19135  

IPv6 supported, port: 19136

 

 

 

---

 

Issues Encountered:

 

1. Ports Timing Out:

 

UDP ports 19135 and 19136 are not accessible externally, despite being forwarded on the router and open in iptables.

 

 

 

2. No Response Locally:

 

Netcat tests show no response from the server on 19135.

 

 

 

 

 

---

 

Remaining Questions:

 

1. Could there be a permissions issue or an internal misconfiguration in the Bedrock server container preventing UDP traffic handling?

 

 

2. Is there any additional Docker or Unraid configuration required for the server to respond to traffic on these ports, even in host mode?

 

 

3. Are there known issues with the Bedrock server when using non-default ports like 19135 and 19136?

 

 

 

 

---

 

Request for Help:

 

Looking for guidance on:

 

1. Debugging why the Bedrock server is not responding to UDP traffic, even though the setup appears correct.

 

 

2. Identifying any additional steps required to verify or resolve the issue.

 

 

3. Understanding if this is a known issue with the Bedrock server container or Unraid networking.

 

 

 

Any insights or recommendations would be greatly appreciated!

 

Edited December 3, 20241 yr by Dwk001

4 hours ago, Dwk001 said:

1. Could there be a permissions issue or an internal misconfiguration in the Bedrock server container preventing UDP traffic handling?

not that im aware of no, and i use this container myself with android minecrft pe and xbox minecraft, no issue seen.

 

4 hours ago, Dwk001 said:

2. Is there any additional Docker or Unraid configuration required for the server to respond to traffic on these ports, even in host mode?

no

 

4 hours ago, Dwk001 said:

3. Are there known issues with the Bedrock server when using non-default ports like 19135 and 19136?

ive never used non default ports but there are no restrictions in the container, i make NO use of iptables or any other firewall mechanism.

 

4 hours ago, Dwk001 said:

Manually added iptables rules to allow UDP traffic on 19135 and 19136:

 

iptables -A INPUT -p udp --dport 19135 -j ACCEPT  

iptables -A INPUT -p udp --dport 19136 -j ACCEPT

So im assuming by this that you do have iptables in place somewhere?,  if so make sure you also have OUTPUT rules too otherwise communication will not work.

Hi. I am running this bedrock server and i want to add the module server-net in the permission file. But when i delete the file you need to delete to add new config. It overwrites the new config with the old one instead. A bug or is it that server-net dont work on this Docker?

I'm having an issue with external access to the server.  I'm fairly confident the issue is not with my port forwarding, as I will explain.

I have installed the binhex-minecraftbedrockserver docker container with all the default settings, (except for WEBUI_USER and WEBUI_PATH).  And I have forwarded ports 19132, 19133, and 8222 in my router, and restarted my router.

 

When I use port checker tools, the ports for `Port: Minecraft Server connection IPv4 (TCP):` and `Port: Minecraft Server connection IPv4 (UDP):` always show up as Closed.  (canyouseeme.org specifies it as "Connection refused")

At the same time, the port for `Port: Web Interface:` shows as open.

 

Here's the kicker.  It doesn't matter what port I use for the server connection or for the web UI, the server connection port always returns closed/connection refused, and the web UI port returns open.

When I forwarded 8222 (which was the web connection,) and saw the test said it was open, the first thing I did was swap that port with the server connection port.  (So I set the web UI to 19132, and I set the server connection to 8222.)
But then when I tested them, 8222 (now the server) was showing closed/connection refused.  And now the previously "closed" 19132 was testing as open, now that it was the port for the web UI.

Am I right to assume at this point that it is the server or docker image that is actually refusing the incoming traffic?
For the record, when connecting to the server using my local IP address of unRAID on the same port, there is no issue.

Edit: I should also mention, I have Plex running in another docker, with its port forwarded and showing as open when I test it with the same tools.

Edited December 16, 20241 yr by Th3Element05
add additional info

11 hours ago, Th3Element05 said:

Am I right to assume at this point that it is the server or docker image that is actually refusing the incoming traffic?

Unlikely unless you have implemented some sort of firewall on your unraid server (no firewall exists in the minecraft bedrock image).
 

 

11 hours ago, Th3Element05 said:

When I use port checker tools, the ports for `Port: Minecraft Server connection IPv4 (TCP):` and `Port: Minecraft Server connection IPv4 (UDP):` always show up as Closed.  (canyouseeme.org specifies it as "Connection refused")

Have you setup a port forward on your router for both TCP and UDP?

p.s. just to confirm i also use this image myself and frequently have people accessing the server remotely via a port forward on my router, so the issue is definitely not with the image.

4 hours ago, binhex said:

Have you setup a port forward on your router for both TCP and UDP?

Yes, both.  I might add forwarding for each of them separately instead, just to see if it makes a difference. 
I am currently stuck using a NOKIA BGW320-505 router/modem combo from AT&T Fiber.  Its plausible that it is the problem, but I find it strange that the port forwarding (the same port numbers) is working for other things, but when I put the minecraft server connection on a port, it suddenly doesn't work anymore.
I am running into problems with other things I'd like to run, like pi-hole, which aren't playing nice with some of the limitations of this AT&T junk.  So I'm going to need to see if another router I have can do what I need if I can just pass my public IP through the AT&T router.

Any idea why pale garden biome doesnt load?
I have the latest version of the docker image running.
I can input the /locate biome command and it tells me where to go, but when i get there its literally an empty area.
Heres my seed if that helps: 6562713170907580554

20 hours ago, Sacharian said:

Any idea why pale garden biome doesnt load?
I have the latest version of the docker image running.
I can input the /locate biome command and it tells me where to go, but when i get there its literally an empty area.
Heres my seed if that helps: 6562713170907580554

Is this a world you’ve already been playing in then updated?  If so, you would have to reset that chunk (complicated) or find a biome you haven’t been to. 

I'm trying to use Tailscale with this container and keep getting this error when I start:

=======================

Executing Unraid Docker Hook for Tailscale

Detecting Package Manager...
ERROR: Detection from Package Manager failed!
ERROR: Unraid Docker Hook script throw an error!
       Starting container without Tailscale!

Starting container...

=======================

Where would I find logs for tailscaled and dockerd so I can see why it might be failing? I checked /var/log/ but couldn't find anything relevant.

2 hours ago, lazant said:

I'm trying to use Tailscale with this container and keep getting this error when I start:

=======================

Executing Unraid Docker Hook for Tailscale

Detecting Package Manager...
ERROR: Detection from Package Manager failed!
ERROR: Unraid Docker Hook script throw an error!
       Starting container without Tailscale!

Starting container...

=======================

Where would I find logs for tailscaled and dockerd so I can see why it might be failing? I checked /var/log/ but couldn't find anything relevant.

this MAYBE related to the missing 'which' command which i subsequently included in the base image, ive now rebuilt the image, please pull down and let me know.

 

p.s. no idea where the tailscale log is (assuming there is one), i would love to know that too @ich777 any ideas?.

3 hours ago, lazant said:

Where would I find logs for tailscaled and dockerd so I can see why it might be failing?

30 minutes ago, binhex said:

i would love to know that too @ich777 any ideas?

The default path in the container is /var/log/tailscaled by default and will be displayed when the integration is working right at the beginning:

 

30 minutes ago, binhex said:

which

Thanks for rebuilding @binhex the container is now working with the Unraid Tailscale Integration.