🌌
Cosmos Guides
  • Cosmos Guides
  • Docker & Compose Setup
    • 01) Docker installation
    • 02) Cosmos Server setup
    • 03) QoL Docker Compose setup
  • Cosmos Server setup
    • 01) Initial launch of Cosmos Server
    • 02) Initial setup of Cosmos Server
    • 03) Cosmos hostname setup
    • 04) DNS Challenge setup (CF)
      • 04a) SSL/TLS settings
      • 04b) SSL Wildcard setup
      • 04c) Creating a DNS Zone API Key
    • 05) Finishing hostname setup
    • 06) Admin account setup
    • 07) Final Steps
  • Pterodactyl Setup
    • 00) Information about Pterodactyl
    • 01) Installing Pterodactyl
      • 01a) Creating a network for Pterodactyl
      • 01b) The Docker Compose example
      • 01c) Launching Pterodactyl
    • 02) Creating URLs
      • 02a) Create URL for pt-panel
      • 02b) Create URL for pt-wings
      • 02c) Setting up CORS
        • 02ca) CORS Option 1 (secure)
        • 02cb) CORS Option 2 (failsafe)
    • 03) Setup of the Panel
      • 03a) Creating the first user
      • 03b) Setting up a location
      • 03c) Setting up the node
      • 03d) IP and Port allocation
    • 04) Connecting the Wings
      • 04a) Creating the config.yml
      • 04b) Check if pt-wings work
      • 04c) Final touches
  • Using Pterodactyl
    • 00) Overview
    • 01) Setting up a game server
      • 01a) Creating a server
        • 01aa) Core Details
        • 01ab) Allocation Management
        • 01ac) Application Feature Limits
        • 01ad) Resource Management
      • 01b) Game server configuration
        • 01ba) Startup Configuration
        • 01bb) Service Variables
      • 01c) Final Steps
        • 01ca) The Pterodactyl Terminal
        • 01cb) Accessing the SFTP server
    • 02) Importing new eggs
      • 02a) Locating the egg
      • 02b) Downloading the egg
      • 02c) Creating a Nest
      • 02d) Importing the egg to the nest
    • 03) Setting up a SteamCMD server
      • 03a) Creating a server
      • 03b) Game server configuration
        • 03ba) Allocation Management
        • 03bb) Nest Configuration
      • 03c) Service Variables
      • 03d) Final Steps
  • Troubleshooting
    • 00) Overview
      • 01) The Node shows up as offline
      • 02) My Panel login page is blank
      • 03) "x509: certificate signed by unknown authority" error (RHEL/CentOS/Fedora)
Powered by GitBook
On this page
  • What is Pterodactyl?
  • What is the difference between Pterodactyl Panel and Wings?
  • Why is this guide necessary?
  1. Pterodactyl Setup

00) Information about Pterodactyl

Previous07) Final StepsNext01) Installing Pterodactyl

Last updated 1 year ago

What is Pterodactyl?

Pterodactyl® is a free, open-source game server management panel built with PHP, React, and Go. Designed with security in mind, Pterodactyl runs all game servers in isolated Docker containers while exposing a beautiful and intuitive UI to end users.

What is the difference between Pterodactyl Panel and Wings?

Pterodactyl is divided into two sections: the Panel (frontend) and the Wings (backend).

The Panel is essentially just a web interface with some dependencies. It employs'mariadb' as its database and'redis' as its cache.

Pterodactyl's Wings are its backbone. Pterodactyl's server control plane is Wings, which creates servers and manages their individual SFTP servers. It's all very cool!

Why is this guide necessary?

Because it's a huge PITA to setup, if you don't know where to begin, and know the weird quirks of setting Pterodactyl up, using Docker.

Ideally, both the Panel and the Wings should be behind Reverse Proxy. In my experience, it works best this way. So that's what we'll be doing in this guide.

It requires some effort, but once set up, it's a very useful tool. It should work if you follow this guide and the previous steps.

I'll also demonstrate how to import different game servers, known as "eggs," and how to set up game servers in general using Pterodactyl. This will be covered in the section.

Disclaimer: This guide was created with a cheap Ubuntu 22.04LTS VPS and a brand new domain.

I'm using Cloudflare as my DNS provider, with a Wildcard SSL certificate. I've tested the steps multiple times, formatting and starting over, and they should work across multiple systems.

Your mileage of success might vary. But it has worked for me and a few others, so hopefully it'll work for you to.

But please do not skip any of the steps, or something might break along the ride!

Using Pterodactyl