🌌
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
  • Setting up the node
  • GIF Guide
  • On to the next step!
  1. Pterodactyl Setup
  2. 03) Setup of the Panel

03c) Setting up the node

Previous03b) Setting up a locationNext03d) IP and Port allocation

Last updated 1 year ago

In this section, we will set up the node for the first time. First and foremost, we must create the node using the Panel. When the node is created, it will provide us with a 'config.yml' template to use for our actual 'pt-wings' container.

Don't worry if it sounds complicated; I'll walk you through the process.

Setting up the node

  1. Head to the Nodes menu in the Panel web UI:

  2. Select the Create New button:

  3. Again, you are free to name it whatever you want. In my case, I'll simply call it EuVPSNode01.

  4. You can leave the Description field blank or fill it with whatever information you think is necessary.

  5. The Location should be set to the one you .

  6. The Node Visibility should be set to Public (at least for now).

  7. Set the FQDN to the reverse proxied URL we created for the pt-wings container. That would be pt-wings.engels.zip in my case.

  8. For the Communicate Over SSL, set it to Use SSL Connection.

  9. For the Behind Proxy, set it to Behind Proxy.

  10. The Daemon Server File Directory should be left at its default value of /var/lib/pterodactyl/volumes. This is where all of the game server data will be stored, in separate folders. This is set in the .

  11. The Total Memory setting should be set to the total amount of RAM you want to dedicate to game servers. This can be changed later, so don't be concerned if you set it too high or too low. Because I'm using a low-cost VPS with 8GB of RAM total, I'll go with 4GB, which is 4096MB.

  12. The Memory Over-Allocation percentage is the percentage by which you will allow the Total Memory limit to be exceeded. I'm going to set mine at 0%.

  13. The Total Disk Space should be set to the amount of disk space you want to dedicate to your game servers. This can also be changed later, so don't be concerned if it's too high or too low. I'm going to set mine to 20GB, which is 20480MB.

  14. The Disk Over-Allocation percentage is the percentage by which you will allow the Total Disk Space limit to be exceeded. I'm going to set mine at 0%.

  15. The Daemon Port should be changed from 8080 to 443, since we're going to run the node from behind a reverse proxied URL, that uses SSL. And for basically all SSL things, it uses 443 as the default port. It's very important to make this change.

  16. The Daemon SFTP Port should remain at its default value of 2022. This is the port that every SFTP server created by Pterodactyl Wings will use.

  17. Now you select Create Node:

  18. After that, it'll continue to - so you can go ahead to the next step in this tutorial

GIF Guide

On to the next step!

👍
just created
docker compose example
IP and Port allocation