🌌
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
  • My Panel login page is blank! Help!
  • Option 1: Recreate the PHP/Laravel cache
  • Option 2: Delete everything
  1. Troubleshooting
  2. 00) Overview

02) My Panel login page is blank

Previous01) The Node shows up as offlineNext03) "x509: certificate signed by unknown authority" error (RHEL/CentOS/Fedora)

Last updated 1 year ago

My Panel login page is blank! Help!

If your Panel does not appear after you , there could be a number of reasons for this. You must ensure that you have carefully followed all of the steps up until the point where you create the URLs for the Panels.

After you've double-checked that you've completed , you can try one of the following options. Try them one at a time; they don't require you to try them in any particular order, and the order doesn't matter.

Option 1: Recreate the PHP/Laravel cache

  1. If the database connected to the Panel behaves strangely, you can refresh its cache. This is fairly straightforward. If this works for you but you have to do it after each restart, something else is wrong with your setup. But for now, let's give it a shot!

  2. Head to your favourite SSH terminal, and connect to your server.

  3. Execute the following command:

docker exec -it pt-panel /bin/sh
  1. This allows you to enter the docker container pt-panel and run bash commands from within it.

  2. Execute this command:

php artisan optimize
  1. This will clear the cache, and you should be able to access your Panel via the reverse proxy URL .

  2. Exit the docker container by typing exit in the terminal.

Option 2: Delete everything

This is more of a last resort. But if nothing works, or if you have to run php artisan optimise after every reboot, something probably went wrong during the installation of Pterodactyl. And you would sadly have to delete everything and try once more.

  1. Turn off your pt-panel, pt-database and pt-redis container. You can do this through the Cosmos Server UI.

  2. Head to your favourite SSH terminal, and connect to your server.

  3. Execute the following command:

sudo rm -rf /srv/pterodactyl/*

Be aware! This will delete everything connected to the Pterodactyl Panel. This means all the settings and users will get deleted. You will still keep your Game Server files, as they are located elsewhere (/var/lib/pterodactyl).

  1. Turn on your containers in the following order - and wait a few seconds between them so they have time to create the necessary files.

    1. pt-redis

    2. pt-database

    3. pt-panel

You should now be able to proceed with the guide from the "" step.

If it still doesn't work, I'd suggest asking for assistance on the .

Creating URLs
Pterodactyl discord server
😭
create the URL for it
all of the steps
you created
asciicast