🌌
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
  • SSL Wildcard setup
  • Setup an "A" record
  • Setup a "CNAME" record
  • GIF Guide
  • On to the next step!
  1. Cosmos Server setup
  2. 04) DNS Challenge setup (CF)

04b) SSL Wildcard setup

Previous04a) SSL/TLS settingsNext04c) Creating a DNS Zone API Key

Last updated 1 year ago

SSL Wildcard setup

To ensure that SSL Wildcards work with Cosmos, we must configure the DNS settings correctly. When you know what to do, it's fairly easy.

SSL Wildcards are clever because they use the root domain's SSL certificate for all subdomains. As a result, you do not need to create separate A or CNAME records for each subdomain you wish to create. You simply create URLs with Cosmos, and it will automatically work with SSL encryption/HTTPS. I promise it's fantastic!

Setup an "A" record

  1. Head to DNS

  2. Setup a A name record:

  3. Select "(+) Add Record"

  4. For Type, select "A"

  5. For Name, type in your web domain. In my case, it's engels.zip.

  6. For IPv4 address, type in your Public IPv4 of the server hosting Cosmos Server

  7. Turn off Cloudflare's Proxy Tunnel. It messes up certain things unfortunately.

  8. Press Save

Setup a "CNAME" record

  1. Head to DNS

  2. Setup a CNAME record:

  3. Select "(+) Add Record"

  4. For Type, select "CNAME"

  5. For Name, type in * and nothing else.

  6. For "Target", type in your web-domain of the server hosting Cosmos Server

  7. In my case, it would be engels.zip

  8. Turn off Cloudflare's Proxy Tunnel. It messes up certain things unfortunately.

  9. Press Save

GIF Guide

Here's the whole process in a GIF, should you prefer that:

On to the next step!