Pterodactyl

Pelican Panel

I have moved over to Pelican, which is essentially Pterodactyl 2.0, though it is in beta release. This documentation will stay online but is legacy and not 'in use' anymore in my homelab anymore Please look at my guide

Total Time Required

1 Hour

Difficulty

Moderate

Required Knowledge

Docker, Docker Compose, Reverse Proxies, DNS, Dockflare

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

Further testing has confirmed the panel will ONLY talk to DB's on 3306

Prerequisites

• A machine to host the panel

  • Docker and compose installed

  • Port 3306 to be available

    Further testing has confirmed the panel will ONLY talk to DB's on 3306

• A machine to host the wings node

  You can create multiple node machines and load balance your servers, our scale outwards in the future

  • Docker and Compose installed

  • A high performance, well spec'd machine;

    • Lots of RAM

    • High single thread passmark CPUs (required for Minecraft)

    • SSD storage

• A Domain that's managed by Cloudflare

• Cloudflare Zero Trust tunnel

• Dockflare container

• A Cloudflare DDNS container

  • With Proxy disabled

Recommended

• Portainer & GitOps

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

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