Images

Beta

An image supplies the operating system used when creating a VPS. The available catalog depends on the installed release, hosting provider, location and plan. An operating system mentioned in these docs is not a guarantee that your provider offers it.

Choosing an Image

Before creating the VPS, check:

• Distribution and version, including whether it still receives security updates.
• Architecture and minimum disk size.
• The recommended resources for your applications.
• Default login username and supported login methods.
• Any documented requirements for first-boot setup or console access.

Use the choices shown for the selected plan and location. If the image you need is missing or unavailable, ask your hosting provider for supported alternatives. See Provisioning for the creation steps.

Login User

Use the username documented for the selected image, not an assumed root account. Common examples are:

Image	Common username
Ubuntu cloud image	ubuntu
Debian cloud image	debian
Custom image	As specified by the provider

Provider-customized images can use different usernames. Check SSH Access if authentication fails. Select only your public SSH key where key-based setup is offered; never upload the private key.

Updates and Reinstallation

A newer image offered for new VPSs does not update an existing VPS. Apply operating system and application updates inside your running guest. If a reinstall control is offered, read its data-loss warning and back up first. Do not reinstall just to troubleshoot a login problem before checking the username and key.

ISO Library

Use ISO mounting or boot options only when your installed release and provider enable them for your plan. Choose approved media compatible with the VPS and follow the provider's boot instructions. Installation tools can overwrite disks, so confirm the target and backups before continuing. After installation, follow the provider's instructions to remove installation media and boot from disk.

Safe Image Sources

If image or ISO import is offered, follow the provider's documented source and format requirements. Use trusted publishers and verify published checksums when available. Keep TLS certificate validation enabled; resolve certificate errors instead of bypassing them. Do not put credentials in download URLs or share private download links in public diagnostics.

For missing images, boot failures or login issues, see Troubleshooting. Send relevant, redacted details privately to your hosting provider.