Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minecraft Not broadcasting to LAN/ Unraid #59

Closed
torodiesel opened this issue Feb 7, 2021 · 4 comments
Closed

Minecraft Not broadcasting to LAN/ Unraid #59

torodiesel opened this issue Feb 7, 2021 · 4 comments
Labels
contribution welcome help wanted Extra attention is needed info-needed Further information is requested priority-low

Comments

@torodiesel
Copy link

I have noticed that everything I try to do on unraid to get the port 25565-25566 to broadcast to the local machines does not work. I have disabled firewalls and changed IP's but it still does not show. Is this not supported? I tried with a host and a Bonded interface.
Capture

@Joly0
Copy link
Contributor

Joly0 commented Jun 4, 2021

I have noticed that everything I try to do on unraid to get the port 25565-25566 to broadcast to the local machines does not work. I have disabled firewalls and changed IP's but it still does not show. Is this not supported? I tried with a host and a Bonded interface.
Capture

I dont know if this is still a problem for you, but i can definitly tell that amp on unraid is working perfectly regarding the network
image

There might be something wrong with your network setup, or your docker setup entirely

@byeuji
Copy link

byeuji commented Jul 4, 2021

I'm having this issue with the instances I've set up inside Amp-Dockerized (Minecraft and Valheim on default ports 25565-25575 and 5678-5688).
I opened the ports on the firewall using UFW initially, then disabled the firewall entirely. Then I installed GUFW and reset the rules, then I reviewed iptables, then I reviewed lsof -i -P -n and netstat -tulpn

image

In all cases, the instances inside Amp are invisible on the local network (including with the firewall off entirely). When I run an nmap scan of 25565, I get "25565/tcp closed minecraft".

I have 3 other containers (Plex, Portainer and Deluge) all working normally and visible outside my local network. Like Amp, I have integrated SSL with each of these services, and they're all certifying correctly (including Amp-Dockerized's WebUI). It's only the instances that aren't showing up.

Here are the ports in my Portainer container management for Amp-Dockerized:
image

image

The "Network" was set to "amp-dockerized_default" initially -- I've tested these scenarios on "bridge" as well.

I'm not sure if there's some network configuration I can do from within the instance to make it visible?
image

I'm not an expert with iptables, so I'm hoping there's something glaringly obvious with these screenshots.

@xannor
Copy link

xannor commented Jul 21, 2021

I could be wrong about current/future versions, but I believe the broadcast to lan is only a feature of the client, (and I think MineOS emulated) so unless AMP provides this ability, you will not get a broadcast from a stand-alone server.

(I found an old discussion talking about it https://discourse.codeemo.com/t/automatically-showing-server-in-lan/114/5 and in there is a link to a python script.)
So unless AMP implements this in their plugin it would not work, either by providing the broadcast as part of the manager (similar to MineOS), or running something with the instance.

@MitchTalmadge MitchTalmadge added contribution welcome help wanted Extra attention is needed info-needed Further information is requested priority-low labels Jan 19, 2022
@MitchTalmadge
Copy link
Owner

Unfortunately I don't think we can do this. But if someone can prove me wrong or provide some info on how to do it, please do & let me know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contribution welcome help wanted Extra attention is needed info-needed Further information is requested priority-low
Projects
None yet
Development

No branches or pull requests

5 participants