Reinstall a Lightsail server in Blesta with its original OS
Use Reinstall when your customer deliberately wants a fresh copy of the server's original operating system, for example when repurposing a server after moving its application elsewhere. It replaces the contents of the system disk. It does not restore a saved snapshot or choose a different operating-system image.
Prepare the service
Agree the maintenance window and the files, databases and application settings the customer needs to keep. Copy required data somewhere independent of the system disk and confirm that it can be recovered before proceeding.
For Linux servers, review the public keys saved on the service's SSH Keys page. The module reapplies the current saved keys to the fresh system. The product's initial startup script is not replayed, so plan any application installation and configuration needed afterwards.
Customer steps: reinstall
- Open the correct Lightsail service in the Blesta client area and its Information page.
- Find Reinstall and check the original operating system shown there.
- Type the server hostname exactly as shown in the confirmation field.
- Choose Reinstall server. Read the confirmation that all data on the server disk will be erased; confirm only after the required backups are ready.
- Follow progress in Activity and wait for the reinstall to complete before reconnecting.
Check the fresh server
Review the firewall rules for the fresh server, then use the updated connection details on the service page. Confirm that the server runs the intended operating system and that authorised users can connect. Reinstall the application's packages and restore only the data intended for this fresh installation.
An attached extra-storage disk is carried over in its current state. Reinstalling the system disk does not roll that disk's data back or configure the fresh operating system to mount it. Identify and mount existing data carefully; do not format it as a new blank disk.
A static IP is carried over by the reinstall workflow. Review the connection details and any DNS records after completion, particularly for a service without a static IP.
