Check the service details
Confirm the assigned server address, operating system, username, and recovery method through your trusted service channel. Never share your password or private SSH key in a public chat or support message.
Establish and verify your access
Use the connection method provided with your order. Check the host identity using a trusted channel before accepting a new or changed SSH host key. Set up a separate administrative account and SSH-key access where appropriate.
Keep a tested recovery path and an existing session available before changing remote access settings.
Plan updates and network access
Follow your distribution’s documentation for security updates and firewall rules. Allow only required application ports and trusted administration access. Confirm access still works before ending your original session.
Do not expose a database or an administrative panel to the whole internet without considering authentication and network restrictions.
Create an independent backup strategy
Choose what data and configuration must be backed up, how often copies are taken, and where they are stored. Keep a copy outside the server and test that you can restore it. A second disk or a RAID array is not an independent backup.
Monitor and document the environment
Track storage capacity, service health, and the resources your workload uses. Keep a record of installed services and recovery steps without putting secrets in ordinary notes. Review updates and restore procedures as your project changes.
Use your operating system’s official instructions
For Ubuntu-based environments, consult the official server documentation for OpenSSH, firewalls, software updates, and backups.
Ubuntu Server documentation