@hexparrot
I did that and I see that item…
This is my list (a part of it):
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT tcp – anywhere anywhere tcp dpt:8123
So it seems like it’s open then. What’s the error behavior you’re seeing?
How do you know it’s closed? From all appearances, the firewall isn’t the issue. Are you sure Dynmap isn’t the issue?
@hexparrot
I’m totally not sure that my firewall is the issue :P.
I checked it with http://www.yougetsignal.com/tools/open-ports/. It says it’s closed.
IP: play.dreamworld.cf Port: 8123
What can the problem be?
You can try literally any port and it will also say ‘closed’. Closed means ‘nothing is listening’. So if you tested port 3333, it’d also say ‘closed’ whether or not you fiddle with the firewall.
If you need further assurance, turn off the firewall.
iptables -P INPUT ACCEPT
iptables -F
If it still says ‘closed’, you know it’s not the firewall, it’s dynmap.
@hexparrot
When I do that, any cracked client will be able to join my server…
What can the problem with dynmap be?
I think you’re misunderstanding what a firewall does…it has absolutely nothing to do with allowing cracked clients.
@hexparrot
It will allow the access to my back-end servers for other players. They are in offline-mode for my bungeecord.
@hexparrot
When I try to start a minecraft server on port 8123, it says "Failed to bind port. Perhaps it’s already in use. ". Is that normal?
Why are you trying to start a minecraft server on your dynmap port?
Disabling the firewall will do the exact same thing and has no impact on which clients can connect.
And it has the benefit of not trying to have a Minecraft server and a dynmap server open on the same port.
I know but that was my alternative… I got my information here: https://www.spigotmc.org/wiki/firewall-guide/
@hexparrot
I’m trying to create a server on the 8124 port to test that port. When I enable it, I can’t access it. I opened the firewall up too in this case.
Hi @Christophe6.
Opening a port in a firewall is not equal of that being open (even though we are saying "Opening the port). It is merely you telling the operating system that you will allow connections through that port. You still need something listening on that port for it to actually be open.
so:
Firstly:
After opening the port, did you actually start a service listening on it as well? Is the server you configured to use that port, or dynmap, running?
Secondly:
Are your MineOS machine connected directly to the internet? Or is it connected to your LAN? Are you trying to connect with a local client on the same LAN that your server runs on?
If the server is placed on a LAN (with IP 10...* or IP 192.168.* *), and you are trying to connect from the internet you also need to configure port forwarding. The firewall in MineOS is not the only one, you have one in your Internet router as well.
OK.
As for your server connected through bungeecord, here’s a tip:
Since Bungee (as far as I know) relays connections, you can configure your other servers to allow connections from only Bungeecord. At leas if those servers are running on the same MineOS-installation. Just set them to only listen to 127.0.0.1 (localhost). This would allow bungeecord, and its connections through, but not anyone trying to connect directly.
I do this with my Dragonet - Minecraft connection when I test if they have released a working version yet. (Dragonet is a Minecraft Pocket Edition to Minecraft PC server bridge, working in prettty much the same way as bungeecord). My listening minecraft PC server is set to only accept connections from 127.0.0.1, and Dragonet is set to pass on connections to the local server. Since they communicate on the same server, all they need to talk is the localhost adress. Anyone else trying to connect will be ignored. (I do this because my some of my users are to young to have a xbox or Minecraft account, and only uses Minecraft Pocket Edition for iPad, and thus cannot log in on any other server than a “offline” server)
@iMelsom
That’s it! I forgot to portforward although I’m with a VPS host… How can I portforward there.
And why isn’t it possible to start a minecraft server on the for now not used dynmap port?
I can’t see why this should be a problem, as long as the port is open in FW, and is port forwarded. And that you specify the port in the client. If there are some limitations in the minecraft server jars, I have no Idea.
I found the issue! For some reason, port 8123 was already in use and I changed it to 8124.
I changed this line (#webserver-bindaddress: 0.0.0.0) to: webserver-bindaddress: 0.0.0.0! Thanks to everyone who helped me!
2 Likes