Updating

Only panel administrators should update PteroCloud. VPS users should follow their host's maintenance notices and keep their own application and data backups current.

Compatibility

Read the target release's compatibility list and upgrade instructions before changing anything. Confirm support for your current PteroCloud version, panel, Blueprint, PHP, database, Redis and Proxmox environment.

Check whether the release requires a different PHP loader or accompanying services. Do not assume that an installation command, upgrade path or optional flag works across all releases. Ask support before proceeding if your combination is not listed.

Before Updating

1. Obtain the update from your trusted Krapple Studios customer channel.
2. Review required intermediate updates and any manual steps in the release instructions.
3. Back up the panel database, files and configuration together, including .env, and verify restoration.
4. Keep the previous package and backups in private storage outside the public web directory.
5. Back up affected VPS data separately; panel backups do not contain guest disks.
6. Arrange a maintenance window, notify users and let active VPS operations finish.

Test the update in a non-production environment where practical and permitted by your license. Do not copy live credentials or customer data into an unsecured test system.

Updates

Apply the package using the method specified for that release. The supported method may use the customer installer or Blueprint; Installation describes those entry points but does not replace release-specific upgrade instructions.

Enter a license key only through the supplied private prompt or setup form, never as a command-line argument. Apply any required service changes exactly as documented. If an update stops with an error, preserve the output and resolve it before continuing.

After Updating

Confirm that required background services are running. From the panel directory, using the PHP executable and account configured for your installation, run:

php artisan pterocloud:compatibility
php artisan pterocloud:verify
php artisan pterocloud:setup:verify
php artisan pterocloud:health

• Review all failures and warnings in the output or Support Center available in your release.
• Repeat the Proxmox connection test.
• Check that an existing test VPS shows the correct status and remains accessible.
• Test available console and ordinary VPS actions using a non-production workload.
• Confirm that customer access and permissions remain correct before ending maintenance.

Recovery

Do not copy older addon files over an updated database or assume that uninstalling will restore the previous version. Follow the release's recovery instructions; a restore may require matching panel files, configuration and database backups.

Contact [email protected] if the recovery path is unclear. Include versions, the failed step and reviewed diagnostics privately. Never send credentials or an unredacted .env file.