🌌
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
  • Cosmos hostname setup
  • Hostname setup
  • On to the next step!
  1. Cosmos Server setup

03) Cosmos hostname setup

Previous02) Initial setup of Cosmos ServerNext04) DNS Challenge setup (CF)

Last updated 1 year ago

Cosmos hostname setup

You'll need to set up your hostname/domain. In my case, I'm using Cloudflare and a "proper" domain, so this guide will be written from that perspective. I apologize if your DNS service looks drastically different.

You may not need a literal domain; instead, enter your local IPv4 address.

I'm also going to configure my domain with a wildcard certificate because I don't want to create A and/or CNAME records for each subdomain - and because Cloudflare actually supports it quite well

However, in this guide, I'll be using my newly purchased testdomain www.engels.zip.

Remember to keep the Cosmos Server setup tab open, until you're finished. Open a new tab, if you need to configure Cloudflare or other DNS providers.

Hostname setup

  1. You can enter either a domain that you own, or your local IP address as your domain. In my case, I'm going to use my domain engels.zip.

  2. Select the Let's Encrypt option, if you got a web-domain. Otherwise, you should select "Generate self-signed certificate".

  1. After that, I'm going to select Cloudflare as my DNS provider.

  1. For the next part, I'll need to do the "DNS Challenge setup". All this is not needed, if you don't have a web-domain. So you can skip the DNS Challenge part, if you just use your local IP.

You should keep the Cosmos Setup tab open, while you configure Cloudflare and the parts needed for the DNS Challenge!

On to the next step!

😇