Updating the Panel

This documentation covers the process for updating within the 1.x series of releases. This means updating from — for example — 1.11.x to 1.12.x.

Panel Version Requirements

Each version of Pterodactyl Panel also has a corresponding minimum version of Wings that is required for it to run. Please see the chart below for how these versions line up. In most cases your base Wings version should match that of your Panel.

Update Dependencies

• PHP 8.2, or 8.3 (recommended)
• Composer 2.X

Before continuing, please ensure that your system and web server configuration has been upgraded to at least PHP 8.2 by running php -v and Composer 2 by running composer --version. You should see an output similar to the result below. If you do not see at least PHP 8.2 and Composer 2, you will need to upgrade by following our PHP Upgrade Guide and return to this documentation afterward.

vagrant@pterodactyl:~/app$ php -v
PHP 8.3.30 (cli) (built: Dec 21 2022 10:32:13) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.3.30, Copyright (c) Zend Technologies
    with Zend OPcache v8.3.30, Copyright (c), by Zend Technologies

vagrant@pterodactyl:~/app$ composer --version
Composer version 2.8.12 2025-09-19 13:41:59

Upgrade Steps

Follow the steps below to upgrade your Panel to the latest version.

Enter Maintenance Mode

Whenever you are performing an update you should be sure to place your Panel into maintenance mode. This will prevent users from encountering unexpected errors and ensure everything can be updated before users encounter potentially new features.

cd /var/www/pterodactyl

php artisan down

Download the Update

The first step in the update process is to download the new panel files from GitHub. The command below will download the release archive for the latest 1.x release (1.15.1 at the time of writing) and will automatically unpack the archive into your current folder. Do not replace the version with latest: once 2.0 is published, latest points at 2.0.

curl -L https://github.com/pterodactyl/panel/releases/download/v1.15.1/panel.tar.gz | tar -xzv

Once all of the files are downloaded we need to set the correct permissions on the cache and storage directories to avoid any webserver related errors.

chmod -R 755 storage/* bootstrap/cache

Update Dependencies

After you've downloaded all of the new files you will need to upgrade the core components of the panel. To do this, simply run the commands below and follow any prompts.

composer install --no-dev --optimize-autoloader

Clear Compiled Template Cache

You'll also want to clear the compiled template cache to ensure that new and modified templates show up correctly for users.

php artisan view:clear
php artisan config:clear

Database Updates

You'll also need to update your database schema for the newest version of Pterodactyl. Running the command below will update the schema and ensure the default eggs we ship are up to date (and add any new ones we might have). Just remember, never edit core eggs we ship! They will be overwritten by this update process.

php artisan migrate --seed --force

Set Permissions

The last step is to set the proper owner of the files to be the user that runs your webserver. In most cases this is www-data but can vary from system to system — sometimes being nginx, caddy, apache, or even nobody.

# If using NGINX, Apache or Caddy (not on RHEL / Rocky Linux / AlmaLinux)
chown -R www-data:www-data /var/www/pterodactyl/*

# If using NGINX on RHEL / Rocky Linux / AlmaLinux
chown -R nginx:nginx /var/www/pterodactyl/*

# If using Apache on RHEL / Rocky Linux / AlmaLinux
chown -R apache:apache /var/www/pterodactyl/*

Restarting Queue Workers

After every update you should restart the queue worker to ensure that the new code is loaded in and used.

php artisan queue:restart

Exit Maintenance Mode

Now that everything has been updated you need to exit maintenance mode so that the Panel can resume accepting connections.

php artisan up

Telemetry

Since 1.11, Pterodactyl will collect anonymous telemetry to help us better understand how the software is being used. To learn more about this feature and to opt-out, please see our Telemetry documentation. Remember to continue with the rest of the upgrade.