Provisioning Your First Server
What happens after you order a Cloud Cube, how to find your credentials, and the first things to do when your server is ready.
This guide covers what happens after you order a Cloud Cube, where to find your credentials, and the first steps to take when your server is ready.
What happens after you order
- Payment is processed: you receive an order confirmation email immediately
- Server is provisioned: our automation creates your VM, installs the OS, installs your chosen control panel, and configures the managed services (firewall, antispam, backups)
- Welcome email is sent: typically within 2-5 minutes of payment. Contains everything you need to log in
- Monitoring starts: your server appears in our monitoring system and is watched from minute one
Finding your credentials
Your welcome email contains:
| Item | What it is |
|---|---|
| Server IP | The public IP address of your Cloud Cube |
| Root password | SSH root login password |
| Control panel URL | Link to cPanel, DirectAdmin, RemarkablePanel, etc. |
| Control panel credentials | Username and password for the panel |
| Hostname | Your server’s default hostname |
You can also find all of this in your client area: Services → My Services → click your Cloud Cube → service details.
Logging in via SSH
ssh root@YOUR_SERVER_IP
Enter your root password when prompted. On first login you’ll see the server’s message of the day (MOTD) with basic system information.
First things to do
passwd to set a strong root password and store it in a password manager.server1.yourdomain.com.Server specifications
To see your server’s resources at any time:
# CPU info
nproc && cat /proc/cpuinfo | grep "model name" | head -1
# RAM
free -h
# Disk
df -h /
# OS version
cat /etc/os-release
Or from your control panel: WHM → Server Status → Server Information gives a full overview.
Checking included features
All Cloud Cubes come pre-configured with:
# Verify Imunify360 is running
systemctl status imunify360
# Verify LiteSpeed (if applicable)
systemctl status lsws
# Verify mail relay
exim -bp | head -5
If anything looks off, open a support ticket: our team will check the configuration.