🌌
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
  • Why use reverse proxied URLs?
  • On to the next step!
  1. Pterodactyl Setup

02) Creating URLs

Previous01c) Launching PterodactylNext02a) Create URL for pt-panel

Last updated 1 year ago

Now we must create reverse proxied urls for our two main containers, the pt-panel and pt-wings. Fortunately, Cosmos Server makes it very simple.

We only need to tweak the pt-wings a little to get it to work properly.

Why use reverse proxied URLs?

Using reverse proxied URLs can be more secure than using the public IP and port assigned to the service you want to expose to the internet for several reasons:

  1. Reduced attack surface: By using a reverse proxy, you can limit the number of open ports exposed to the internet, reducing the attack surface. For example, instead of exposing each service on its own port, you can use a reverse proxy to expose all services on port 443 (HTTPS) or 80 (HTTP) and use URL routing to direct traffic to the appropriate service.

  2. SSL termination: SSL/TLS provides end-to-end encryption between the client and server, but if the server is directly exposed to the internet, it must handle SSL/TLS termination. This means the server has to manage the SSL/TLS decryption process, increasing the risk of exposing the private key. By using a reverse proxy, you can terminate the SSL/TLS connection at the proxy, reducing the risk of exposing the private key.

  3. Authentication and authorization: Reverse proxies can provide authentication and authorization mechanisms, such as user-based access control and two-factor authentication, that can add an additional layer of security to your services.

  4. Load balancing and scalability: Reverse proxies can also provide load balancing and scalability capabilities, allowing you to distribute incoming traffic across multiple servers and services.

Overall, reverse proxies can provide an additional layer of security and functionality to your services, making them a valuable addition to any security architecture.

As an addition, we can utilize Cosmos Server built-in !

On to the next step!

SmartShield