Pterodactyl

Time Required

1 Hour

Difficulty

Easy

Required Knowledge

Docker, Reverse Proxies

Come across an issue with this documentation? You can make an edit request yourself, using the 'Submit Change' button on the left, or report it on our Discord

The Scenario

Our goal is to create a new Pterodactyl Panel and Wings node for hosting game servers.

This documentation is NOT intended for a professional / reseller environment. Please do not follow this guide if you intend on selling or publicizing your server resources, as

• Proxy / Tunnelling wings and panel is NOT supported by Pterodactyl developers

• This guide is provided with best effort support

Panel

The Pterodactyl Panel is the front end gui for managing your servers. The panel can be connected to multiple Wings nodes (or hosts), which this documentation is written for.

Wings

Wings hosts the game server compute (CPU) and storage. As this machines job is to process data, a lot of high performing single thread cores are required as well as a lot of RAM.

Flowchart

As you can see, Wings and Panel communicate via Cloudflare, over the internet. This is not great but OK for a homelab

Prerequisites

• Panel machine

  • Docker and compose installed

  • Port 3306 to be available Further testing has confirmed the panel will ONLY talk to DB's on 3306

• 1 machine to install the Wings node on (can be the same as the panel machine but not recommended) You can create multiple node machines

  • Docker and Compose installed

  • A high performance, well spec'd machine;

    • Lots of RAM

    • High single thread passmark CPUs

    • SSD storage

• A Domain that's managed by Cloudflare

• A Cloudflare Tunnel

• A Cloudflare DDNS container with proxy turned off (this address will be your game server IP. Eg play.yourdomain.com)

Recommended

• Portainer & GitOps

• A separate server for the Panel and each Wings node (if setting up more than 1)