Getting started with an Ingen VPS: First login and setup
Getting started with an Ingen VPS means confirming your assigned server and login details, connecting through SSH, updating the operating system, and testing a recovery route before deploying software. Keep portal credentials separate from the guest login. Available images and controls depend on your service, so follow the details supplied for your own VPS.
By Drew F. · Last updated: November 17, 2026
What you need
Have the provisioning information, your portal login, the assigned public IP or hostname, and a terminal ready. Windows users can use an installed OpenSSH client in PowerShell; macOS and Linux users can use their terminal. Initial usernames, authentication methods, and SSH ports depend on the image and its configuration.
The package and service examples below target Ubuntu Server 24.04 LTS. Confirm your installed OS before using them; they are not an assertion that this image is offered with every service. Use another distribution's own documentation if your image differs.
In this guide
- Access the right portal
- Confirm the server details
- Connect with SSH
- Prepare the operating system
- Understand power actions
- Keep a recovery route
- Check resources
- Protect your data
- Troubleshoot access
- Check readiness
1. Access the right portal
The Ingen Client area is the entry point for account and service matters. Use the Ingen VPS Portal for the server controls available to your service. Neither portal password should be assumed to be your Linux password.
Select the server and compare its label and assigned address with your provisioning information. If it is missing, check the account you signed in with before making changes elsewhere. Enable account two-factor authentication if offered, and avoid sharing a personal login between administrators.
2. Confirm the server details
Record the installed OS, login username, SSH port, public address, and allocated resources. Compare the allocation with your service confirmation and the relevant VPS specifications. Wait for an installation task to finish before using power controls. A running status means the virtual machine has power; it does not prove that SSH or your application is healthy.
A label in a management interface is not necessarily the Linux hostname or a DNS record. Point DNS records at the address assigned to the service, and check any existing IPv6 record as well as IPv4 when troubleshooting a domain.
3. Make your first SSH connection
Run SSH on your local computer. This documentation example uses root and 203.0.113.10; replace both with the supplied username and actual address. Root access may be disabled on your image.
ssh root@203.0.113.10
For a custom port, use the command builder below. On a first connection, verify the host key fingerprint through a trusted independent channel, such as a console you have authenticated to, before accepting it. Do not type a password until you have confirmed the destination. The OpenSSH client manual explains host authentication and connection options.
Build your SSH command
InteractiveEnter the details from your server overview. This creates a command locally; it does not connect to a server or send your entries anywhere.
ssh root@203.0.113.10203.0.113.10 is a documentation example, not your VPS. Use the login supplied for your chosen image; root login may be disabled. Port 22 is the default unless you changed it.
Successful authentication should open a shell on the VPS. Commands entered there run on the remote system. End the session with exit when finished. Never paste passwords, private keys, or tokens into a support ticket.
4. Prepare the operating system
Inside the VPS, identify the distribution:
cat /etc/os-release
Expect fields such as NAME and VERSION_ID. On an Ubuntu 24.04 server with administrative access, refresh package information and review available upgrades:
sudo apt update
sudo apt upgrade
Read the prompts and resolve repository errors before proceeding. Upgrades can restart services. Schedule any required reboot and expect SSH to disconnect during it. Do not interrupt a package operation with a forced power action.
Create and test an administrative account, configure SSH keys, and restrict exposed services before deployment. Test the new login in another terminal before disabling a working authentication method. The VPS security checklist explains this order; the Ubuntu OpenSSH documentation covers distribution-specific configuration.
5. Understand power actions before using them
An application error is not automatically a reason to restart the entire server. Check its process and logs first. When you do need a power action, verify the selected server, notify affected users, and wait for one operation to finish before sending another.
Choose the right power action
ExplainerSelect an action to understand its effect. These controls are examples and never change your VPS.
Boot
Starts a stopped server. It does not reinstall the operating system. Once the server reports running, allow time for its services to start before trying SSH.
Before you continueConfirm that this is the server you intend to start.
Stopping a server is not the same as cancelling a service. Confirm billing and cancellation terms in your agreement. The explainer describes common meanings; it does not guarantee that a particular control is available or behaves identically on every service.
6. Keep a recovery route open
If your service offers a browser console, test it before changing SSH or firewall settings. A console can work when the guest's network login is unavailable, but it still requires the operating system's credentials. It does not bypass guest authentication.
For Ubuntu, inspect the SSH service from an authenticated console:
sudo systemctl status ssh
Look for an active service or a specific error. Press q if a pager opens. A different distribution can use the unit name sshd. If there is no unit, confirm whether the SSH server is installed. Restore the last known working configuration rather than reinstalling just because a network login fails.
7. Read resource usage in context
An installation spike differs from sustained pressure during normal use. Check the guest alongside any portal metrics; allocation charts do not necessarily show filesystem free space, and chart updates may lag.
| Resource | Read-only command | What to inspect |
|---|---|---|
| CPU and processes | top |
Busy processes during slow periods; press q to quit |
| Memory | free -h |
Available memory, swap activity, and application failures together |
| Disk space | df -h |
Use percentage on the filesystem holding your data |
| Inodes | df -i |
Exhausted file entries even when disk bytes remain |
Linux uses memory for cache, so little completely free RAM is not itself a fault. For capacity planning, the RAM and CPU guide explains how to use observations rather than a single dashboard reading.
8. Protect data before a rebuild
Keep application files, configuration, and database backups independently of the VPS. Confirm what the service actually includes rather than assuming backups or snapshots are enabled. Test restoration somewhere safe and record how long it takes.
Before rebuilding, identify exactly which disks will be replaced, copy essential data away, and verify credentials and recovery instructions. Use the database's supported backup procedure for active databases. A live file copy can miss the consistency required for recovery.
After installation, verify the new SSH host key through a trusted channel, update the OS, and restore the application. Confirm the assigned IP and DNS; do not assume they changed or stayed the same.
9. Troubleshoot the symptom
| Symptom | First checks |
|---|---|
| SSH times out | Assigned address, port, power status, firewall rules, and console access |
| Connection refused | Correct server and port, SSH installation, and listening service |
| Permission denied | Image username, selected key, and accepted authentication method |
| Website down but SSH works | Application service, its logs, DNS, and required ports |
| Missing or stalled portal action | Current task, selected server, and available service features |
Do not bypass a changed-host-key warning without investigating it. A rebuild can legitimately change a key, but so can connecting to the wrong machine. If you need help, include the server identifier, time with time zone, exact error, and recent changes. Remove credentials from logs before sharing them.
10. Check readiness before deployment
The checklist records progress for this visit only. It is not a scan of the VPS and does not configure anything. Ensure another administrator can find the recovery instructions if you are unavailable.
Ready for your first deployment?
0 of 6 completeA personal checklist for this visit. Refreshing the page resets your selections.
When access, updates, backups, and recovery are ready, return to your server and deploy a small test of the application before routing production traffic to it.