How to Update Pterodactyl 1.15 Safely

Pterodactyl 1.15.2 was released on 21 October 2026 as a security update for the 1.x panel. If you run 1.15.0 or 1.15.1, plan a maintenance window rather than waiting for a move to 2.0: the 2.0 line is still in open beta. The steps below are for 1.x to 1.x updates only.

Use the official 1.x update guide as the source of truth for commands and current requirements. Do not use its archive-over-existing-files procedure to move to 2.0; that has a separate upgrade path.

Before the maintenance window

1. Confirm the installed panel, Wings, PHP and Composer versions. Check the release notes for the target version.
2. Back up the panel database, .env, uploaded files, and any modified configuration. Verify that you can restore the backup.
3. Record custom code changes, themes and addons. An update can replace modified core files.
4. Check the panel-to-Wings compatibility requirements and reserve time to update Wings where necessary.
5. Warn users of a short maintenance window, especially if billing or automated provisioning calls the panel API.

Update the panel

Put the panel in maintenance mode with php artisan down. Follow the official update guide to download the specific 1.x release, install Composer dependencies, clear compiled views and configuration, and run migrations. Its example download URL names v1.15.2; avoid a generic latest URL that could eventually point at a different major version.

After updating files, set the webserver ownership and permissions required by your installation, restart the queue worker, and run php artisan up. Keep the release notes and the official guide open during the update instead of copying a command from an older article.

Verify before declaring success

Open the admin area and a customer server page. Check login, console connection, start/stop controls, backups, scheduled tasks and a real provisioning flow if you use a billing panel. Check the queue and webserver logs for new errors. Confirm that each node's Wings version meets the panel's requirements.

The 1.15.2 release notes also call out PHP package updates for installations outside Docker. Read that advisory against your own deployment and update all packages for the PHP version you use together, in a planned window. A panel update alone does not necessarily update the PHP runtime.

Planning for 2.0?

Keep this 1.x security update separate from your 2.0 decision. Build a copy of the panel, confirm billing-module support and review every theme and extension. Our v2 extension compatibility guide explains what to check, and our v2 overview covers the wider upgrade plan.

For managed panel updates, BuiltByOtte Cloud hosts the Pterodactyl panel for you; you connect your own Wings nodes.