pterodactyl/documentation
1
0
Fork 0
mirror of https://github.com/pterodactyl/documentation.git synced 2025-12-10 09:17:40 -06:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'master' of https://github.com/pterodactyl/documentation

Browse Source
This commit is contained in:
Dane Everitt 2020-06-29 21:05:20 -07:00
commit fbd1d19f05
No known key found for this signature in database
GPG Key ID: EEA66103B3D71F53
2 changed files with 55 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
.vuepress/theme/styles/text.css
View File

@ -76,6 +76,14 @@ h2 {
@apply .text-2xl .pb-2 .border-b .border-grey-light;
}
h3 {
@apply .text-xl;
}
h4 {
@apply .text-lg;
}
p {
@apply .my-4;
line-height: 1.7;

68
community/games/minecraft.md
View File

@ -2,55 +2,81 @@
[[toc]]
## Network Configuration
This guide was written for Minecraft Proxy Servers (BungeeCord, Waterfall, HexaCord, etc).
## Configuring a Server Network (BungeeCord, Waterfall, HexaCord, etc.)
If you want to operate Minecraft proxy servers like BungeeCord, Waterfall, HexaCord, etc. securely, you can do so with pterodactyl alone as long as you stay on the same node. It differs from a traditional setup in a few ways and might require additonal firewall rules, which is what this guide is for.
:::warning
For the setup described below, it is necessary that all servers are on the same node.
:::
::: danger
If you are a host you should limit it to a single proxy network on a node if you are selling them to customers.
If you are a hosting provider, you should only allow a single proxy network per node, if you are selling them to customers.
:::
### Setting up the Network
#### Allocations in panel
When setting up a minecraft network in the panel you will need to add allocations for bungee (external IP 10.1.70.62 in the example), and the game servers (127.0.0.1).
#### example allocations in panel
### Allocations in the Panel
Create a regular allocation for the proxy server which uses the external IP of the node, so users can reach it.
The actual game servers behind the proxy should use allocations with `127.0.0.1` as the address, so they are only reachable on the node, and not from the public.
#### Example
![](../../.vuepress/public/community/games/minecraft/proxy/node-allocations.png)
#### proxy settings
##### bungeecord/waterfall config
This will differ for other proxy software
`10.1.70.62` is an example, replace it with your own public IP address.
### proxy server settings
As the proxy server, like all servers, is running in a docker container with network isolation, `localhost`/`127.0.0.1` doesn't refer to the node, but to the container. The node can be reached from within the container using `172.18.0.1` (unless the pterodactyl network is configured differently) instead. You therefore need to use this IP in your proxy server configuration.
#### bungeecord/waterfall configuration
This will be different for other proxy servers, please refer to their documentation.
![](../../.vuepress/public/community/games/minecraft/proxy/bungee-config.png)
#### paper/spigot/bukkit settings
This will differ for other server software
### paper/spigot/bukkit settings
The servers itself require the regular config options required by server proxies, which usually comes down to disabling online mode. This will differ for other server software, please refer to their documentation.
#### server.properties
##### server.properties
set online-mode `false`
![](../../.vuepress/public/community/games/minecraft/proxy/paper-server.properties.png)
##### spigot.yml
#### spigot.yml
set bungeecord to `true`
![](../../.vuepress/public/community/games/minecraft/proxy/paper-spigot.yml.png)
### Firewalls
If you are using a firewall, additional rules might be required to allow servers to reach each other on the node. In this case the proxy server needs to reach all of the game servers behind it. Therefore we need to allow traffic from the pterodactyl network to the server ports on localhost.
You can use the following commands as an example. `172.18.0.1` is the default address referring to the node within the pterodactyl network. Replace `<LOCALHOST_PORT>` with the allocated localhost ports of the game servers.
:::warning
The ports you open with the following will be accessable by all minecraft servers on the node.
The following commands will allow any server on the node to access the opened ports.
:::
The following commands are to allow access on `<PTERODACTYL_NET>` (default is 172.18.0.1).
#### UFW (ubuntu)
#### UFW (Ubuntu)
Allow access to the pterodactyl pterodactyl0 network on a specific port.
``` bash
ufw allow in on pterodactyl0 to <PTERODACTYL_NET> port <LOCALHOST_PORT> proto tcp
ufw allow in on pterodactyl0 to 172.18.0.1 port <LOCALHOST_PORT> proto tcp
```
#### Firewalld (centos)
#### Firewalld (CentOS)
Allow access to pterodactyl0 from the pterodactyl0 network.
:::warning
This command will allow any server to access all other servers as well as all ports on the node.
:::
``` bash
firewall-cmd --permanent --zone=public --add-source=<PTERODACTYL_NET>
```
firewall-cmd --permanent --zone=public --add-source=172.18.0.1
```