What should I verify on the first boot of a Linux VPS?
After the service reports ready, confirm the guest identity and baseline configuration before adding an application. First-boot tools may still be applying users, keys, packages or network settings, so distinguish successful SSH access from complete initialisation.
Instructions
1. Verify the host before entering credentials
Use the approved connection details and independently verify the initial SSH host fingerprint. Then confirm the remote identity.
hostname
whoami
cat /etc/os-releaseThese commands identify the selected guest, logged-in account and installed Linux distribution.
2. Compare the visible resources
Check whether the guest sees the allocation you expect.
lscpu
free -h
lsblk -o NAME,SIZE,TYPE,FSTYPE,MOUNTPOINTSCompare CPU, memory and virtual-disk capacity with the ordered plan. A filesystem can be smaller than the provider’s disk allocation until expansion completes.
3. Check initialisation before deployment
If the image uses cloud-init, inspect its status. Otherwise use the image’s documented first-boot mechanism.
cloud-init status --longRead the completed state and any reported errors. Do not assume that the presence of this command is universal across all images.
Check the result
- The guest identity, OS and resources match the intended service.
- Initialisation has completed successfully and the approved administration path works.
Troubleshooting
- cloud-init is not installed
- The image may use another provisioning mechanism; consult its actual documentation.
- The guest resource totals differ
- Check final provider operation status and whether the image still has an incomplete partition or resource-discovery step.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.
