🌌
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
  • IP and Port allocation
  • On to the next step!
  1. Pterodactyl Setup
  2. 03) Setup of the Panel

03d) IP and Port allocation

Previous03c) Setting up the nodeNext04) Connecting the Wings

Last updated 1 year ago

The IP and Port allocation is where you specify which Public IPv4 addresses the game servers should connect to and which ports they can use. You may also be able to use hostnames or local IP addresses, but I haven't tested that.

IP and Port allocation

  1. You're now in the Allocation menu after selecting the Create Node () option in the previous step.

  2. Another box with the title Assign New Allocations can be found to the right.

  3. Enter your public IPv4 address in the IP Address field. It is in my case 89.33.85.247.

  4. If you want, you can enter an IP Alias. This is mostly useful if you have multiple IPv4s connected to your system/network and need to tell them apart. I'm going to leave mine blank, since I don't really care.

  5. You should select a range of ports that are not currently in use for the Ports option. I usually use ports in the 35000 range. You can always add more and remove the allocated ports later if you want.

  6. For now, I'll stick with 35001-35020. This will give me 19 ports that I can use for game servers.

  2. It'll give you a list of the IPv4 + the ports alllocated. Now we can continue!

On to the next step!

Select the Submit button: