🌌
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
  • Restarting the pt-wings
  • Check if the reverse proxy work
  • On to the next step!
  1. Pterodactyl Setup
  2. 04) Connecting the Wings

04b) Check if pt-wings work

Previous04a) Creating the config.ymlNext04c) Final touches

Last updated 1 year ago

In this section, we'll verify that our config.yml works as expected. Then we'll connect our 'pt-wings' container to the 'pterodactyl_nw' network we created in our config file.

Restarting the pt-wings

  1. Finally, we can restart our pt-wings container:

  1. We should now examine the container's logs. To do so, navigate to the Logs menu in the pt-wings container's Details.

  2. Something along the lines of this should be there:

2023-07-26 19:28:52
  INFO: [Jul 26 21:28:52.731] loading configuration from file config_file=/etc/pterodactyl/config.yml
2023-07-26 19:28:52
  INFO: [Jul 26 21:28:52.732] configured wings with system timezone timezone=Europe/Berlin
2023-07-26 19:28:52
  INFO: [Jul 26 21:28:52.733] configured system user successfully gid=988 uid=988 username=pterodactyl
2023-07-26 19:28:52
  INFO: [Jul 26 21:28:52.737] fetching list of servers from API
2023-07-26 19:28:53
  INFO: [Jul 26 21:28:53.051] processing servers returned by the API total_configs=0
2023-07-26 19:28:53
  INFO: [Jul 26 21:28:53.051] finished processing server configurations duration=467.113µs
2023-07-26 19:28:53
  INFO: [Jul 26 21:28:53.056] configuring system crons  interval=1m0s subsystem=cron
2023-07-26 19:28:53
  INFO: [Jul 26 21:28:53.057] starting cron processes   subsystem=cron
2023-07-26 19:28:53
  INFO: [Jul 26 21:28:53.058] configuring internal webserver host_address=0.0.0.0 host_port=443 use_auto_tls=false use_ssl=false
2023-07-26 19:28:53
  INFO: [Jul 26 21:28:53.059] updating server states on Panel: marking installing/restoring servers as normal
2023-07-26 19:28:53
  INFO: [Jul 26 21:28:53.062] sftp server listening for connections listen=0.0.0.0:2022 public_key=ssh-ed25519 AAAAC3NzaC1lZDIXNTE5AABAIGagsxnhw/CplLwwJVe/WhpiC4zybb66ZXI7Okjvmxdg

  2. Find the pterodactyl_nw network and select Connect.

Check if the reverse proxy work

  1. To see if the pt-wings reverse proxying is working as intended, load up your https://pt-wings.domain.com site up in a new tab in your browser.

  2. In my case, that would be https://pt-wings.engels.zip.

  3. It should give you this message:

"The required authorization heads were not present in the request."

  1. Oddly enough, this means that it's working as intended.

On to the next step!

Go to the Network tab of the pt-wings: