Requirements

Introduction

The Panel needs the software below. The Docker image includes everything except the database and Redis.

Panel Requirements

Your server needs:

• PHP 8.3 or 8.4
• Composer 2
• MariaDB 10.11 or 11, or MySQL 8 or 9
• Redis
• A web server, such as NGINX, that serves the Panel's public directory
• A queue worker and a cron entry for the scheduler

The Panel is tested against each of these PHP and database versions. Other databases, such as PostgreSQL and SQLite, are not supported.

PHP Extensions

Most PHP installations include some required extensions, such as OpenSSL, Sodium, and Tokenizer. These usually need a separate install:

• BCMath
• Intl
• Mbstring
• PDO MySQL
• XML
• Zip

On Ubuntu and Debian, install PHP 8.3 with every required extension. Debian, Ubuntu 26.04 and Ubuntu 22.04 first need a PHP repository from Getting Started:

apt -y install php8.3 php8.3-{common,cli,gd,mysql,mbstring,bcmath,xml,fpm,curl,zip,intl}

To check that PHP has everything, run this from the Panel directory:

composer check-platform-reqs --no-dev

If PHP-FPM uses a different PHP installation than the command line, give it the same extensions.

Building From Source

Release downloads and the Docker image include the built frontend. A Panel installed from a branch or a source checkout has to build it, which needs Node.js 22.12 or newer. From the Panel directory, run:

npm ci
npm run build:production

Operating Systems

Pterodactyl officially supports two ways to run the Panel:

• A native installation on Ubuntu 22.04, 24.04 or 26.04, or Debian 12 or 13. See Getting Started.
• The Docker image, which supports AMD64 and ARM64.

Other Linux distributions may work, but often need changed installation steps, and we cannot help with them. The upgrade from 1.x was tested on Ubuntu 24.04.

Wings

Wings runs on each node and manages your game servers with Docker. Install it separately. It is not part of the Panel image.

There is no Wings version table for 2.0 yet. Wings 1.13.2 and 1.13.3 work with the 2.0 Panel, and handled all of this in testing without changes:

• Power actions and server status.
• Files and the console.
• SFTP, with passwords and with SSH keys.
• Schedules.
• Backups.