Merge pull request #64 from pterodactyl/community/bungeecord

add minecraft server networks to community section
This commit is contained in:
Dane Everitt 2019-01-29 09:20:39 -08:00 committed by GitHub
commit 6b92bd98ba
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 44 additions and 0 deletions

View File

@ -293,6 +293,13 @@ module.exports = {
'/community/install/daemon/debian9.md',
]
},
{
title: 'Minecraft',
collapsable: false,
children: [
'/community/minecraft/networks.md',
],
},
]
}
},

View File

@ -0,0 +1,37 @@
# Server Networks
[[toc]]
:::warning
This guide was written with BungeeCord in mind, but should work for Waterfall and Hexacord as well.
For the setup described below, it is necessary that all servers are on the same node.
:::
## Setting up a BungeeCord network
The ideal setup with BungeeCord is a seperated internal network with only one access point which is the BungeeCord server. Pterodactyl provides this with Docker.
In order to create a BungeeCord network you'll have to add an allocation with which the BungeeCord server should be reachable. Add an allocation with the IP address of the node and the desired port (e.g. 25565, the default Minecraft port) to your node first.
Then create a new BungeeCord server and use the allocation you just created.
### Adding servers to the BungeeCord network
All the other servers that should be part of the BungeeCord network don't require external ports. Create new allocations on the localhost IP address `127.0.0.1` with some ports for the servers to use. You can also enter a port range, e.g. `30000-30010` which will get you 11 ports.
Now create new servers and be sure to use `127.0.0.1` allocations for each of them. To add the servers to your BungeeCord network, use `172.18.0.1:<port of the internal server>` (not 127.0.0.1) as the IP addresses of the servers to add in your configuration file.
## Notes
* **Only** the proxy (Waterfall / Hexagon / Bungee) has to be bound to an external IP.
* **No modifications to iptables should be done**
* all servers behind the proxy are safe.
### UFW Firewall
If you are using the ufw firewall, it might be necessary to allow access to specific host ports. The following command allows incoming requests to `172.18.0.1`, which is the IP of the actual host server within the docker network. Replace `<LOCALHOST_PORT>` with any port you want to be accessible. In this case use the port you assigned to the minecraft server you want to add.
```
ufw allow in on pterodactyl0 to 172.18.0.1 port <LOCALHOST_PORT> proto tcp
```
:::warning
The ports you open with this command will be accessible by any server on the same node.
:::