This documentation covers the process for updating within the 1.x
series of releases. This means updating from
β for example β 1.5.0
to 1.6.0
. Do not use this guide for upgrading from 0.7
.
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.
Panel Version | Wings Version | Supported | PHP Versions |
---|---|---|---|
1.0.x | 1.0.x | 7.3, 7.4 | |
1.1.x | 1.1.x | 7.3, 7.4 | |
1.2.x | 1.2.x | 7.3, 7.4 | |
1.3.x | 1.3.x | 7.4, 8.0 | |
1.4.x | 1.4.x | 7.4, 8.0 | |
1.5.x | 1.4.x | 7.4, 8.0 | |
1.7.x | 1.5.x | β | 7.4, 8.0 |
Minimum PHP Version Changed
If you are upgrading from a version of Pterodactyl prior to 1.3.x
you'll need to update your PHP
dependencies. The latest versions of Pterodactyl Panel require a minimum version of PHP 7.4 and
Composer v2.
7.4
or 8.0
(recommended)2.X
Previous versions of Pterodactyl allowed for you to be running PHP 7.3. However, due to dependency updates and the fact that 7.3 is now EOL we have bumped the minimum acceptable PHP version to 7.4 β PHP 8 is recommended. You will also need to be using Composer v2.
Before continuing, please ensure that your system and web server configuration has been upgraded to at least PHP 7.4 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 7.4 and Composer 2, you will need to upgrade by following
our PHP Upgrade Guide and return to this documentation afterward.
[email protected]:~/app$ php -v
PHP 8.0.1 (cli) (built: Jan 13 2021 08:22:35) ( NTS )
Copyright (c) The PHP Group
Zend Engine v4.0.1, Copyright (c) Zend Technologies
with Zend OPcache v8.0.1, Copyright (c), by Zend Technologies
[email protected]:~/app$ composer --version
Composer version 2.0.8 2020-12-03 17:20:38
If your version of Pterodactyl Panel is 1.3.2
or higher, you can simply run the following command to perform a
self-upgrade of the Panel. This will download all of the necessary files and perform all of the actions listed
in this upgrade documentation.
Note: You must have php-posix
extension for the self-upgrade to detect file ownership.
cd /var/www/pterodactyl && php artisan p:upgrade
If you prefer not to perform the automatic self-upgrade, or need to reference any upgrade steps you can follow the documentation below.
WARNING
If you've already performed the self-upgrade successfully you do not need to do anything else on this page.
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
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 most recent version of Pterodactyl, save it in the current directory and will automatically unpack the archive into your current folder.
curl -L https://github.com/pterodactyl/panel/releases/latest/download/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
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
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
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
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 or Apache (not on CentOS):
chown -R www-data:www-data /var/www/pterodactyl/*
# If using NGINX on CentOS:
chown -R nginx:nginx /var/www/pterodactyl/*
# If using Apache on CentOS
chown -R apache:apache /var/www/pterodactyl/*
After every update you should restart the queue worker to ensure that the new code is loaded in and used.
php artisan queue:restart
Now that everything has been updated you need to exit maintenance mode so that the Panel can resume accepting connections.
php artisan up