🌌
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
  • Finding your Public IPv4
  • Checking if Cosmos Server is running
  • Heading into Cosmos
  • On to the next step!
  1. Cosmos Server setup

01) Initial launch of Cosmos Server

Previous03) QoL Docker Compose setupNext02) Initial setup of Cosmos Server

Last updated 1 year ago

Finding your Public IPv4

  1. We should first obtain your Public IPv4 address of your server. You can accomplish this by issuing the following command:

curl -4 icanhazip.com

  1. This will output your Public IPv4, which we will need when we first set up Cosmos Server.

Checking if Cosmos Server is running

  1. In the previous installation step, we ran the docker run command, which automatically started Cosmos Server.

  2. It should therefore already be running. You can confirm this by running:

docker ps -a

  1. The output should show Cosmos Server running:

CONTAINER ID   IMAGE                          COMMAND                  CREATED         STATUS         PORTS     NAMES
cb1e2031f830   azukaar/cosmos-server:latest   "sh -c './$(cat /bin…"   2 minutes ago   Up 2 minutes             cosmos-server

  1. From a console point of view, it should simply look like this:

Heading into Cosmos

  1. Enter your public IPv4 + port "80" into your browser to access your Cosmos instance. In my case, it looks like this:

89.33.85.247:80

  1. When you visit your URL, it should look like this:

  1. Yay! Now we're ready to continue!

On to the next step!