- You must be running the latest patch of OnApp 4.1 version to upgrade to 4.2 version. If you are using an earlier version, please upgrade to 4.1. first.
- Check the Activity Log in your OnApp CP dashboard if there are no transactions running in your cloud. If so, wait until all transactions are complete.
Make sure no Control Panel files are open for editing under the root user account.
If you are using a third-party billing platform, please ensure that this is compatible with OnApp 4.2 before proceeding with the upgrade! The latest WHMCS modules can be found here.
If you are using WHMCS modules, make sure to update the PHP Wrapper after you update OnApp Cloud. Download the latest wrapper.
We strongly recommend that you test all your custom scripts before upgrading your production environment.
- To avoid VNC console issues, make sure that ServerName Apache settings match the SSL certificate.
- Note that if you are using Floating IPs in your environment or if you have VS with primary IPs which could respond to your Control Panel server from elsewhere on your network we would recommend to disable the new 'Ping hosted virtual servers before initiating failover' setting to avoid the possibility of a false-positive ICMP result.
- Be aware that OnApp does not support UEFI on static compute resources. You should disable UEFI on your compute resources before installing OnApp.
- Drives assigned for use by Integrated Storage are identified using a disk signature that is generated using SCSI page query mechanism to the device. Please note that disk signatures may change across different kernel versions following an upgrade and reboot. If this occurs, go to the compute resource edit page to re-identify and select the correct drives. Please contact support if you have any concerns regarding this operation.
- If you are a High Availability or Accelerator Beta customer, please contact OnApp support to discuss upgrading.