Updating the Panel

Updating the panel gets you bug fixes, security patches, and new features. Its web interface and API will be briefly unavailable while it restarts. An AIO update also restarts the bundled Wings, briefly interrupting console connections and server management.

Read the release notes and back up the Panel database, configuration, and encryption key before updating. Keep standalone Panel and Wings installations on compatible releases; see Versions and Clocks. AIO updates both components together.

Pick the method matching how you installed the panel:

1. Pull and restart

Return to the directory containing your existing compose.yml, then update the web service used by the supplied Compose files:

docker compose pull web
docker compose up -d --no-deps web
docker compose ps
docker compose logs --tail 50 web

This updates the Panel image, including bundled Wings for AIO. Database and cache updates are separate maintenance tasks. Keep your existing Compose file and encryption key.

2. Clean up old images (optional)

If you're on the :heavy image or have limited disk space, old image layers can pile up quickly. Remove unused ones:

docker image prune -a

3. Still on the old version? (heavy image only)

The heavy image keeps the last binary it built under ./build/binaries and keeps running it until extensions have been rebuilt. If the version shown doesn't change, or extensions fail to build against the new release, see Extensions troubleshooting.

After updating, sign in, check the Panel version in Admin, and open a server console to confirm its connection works.