RunbookDay-zeroUpdated 2026-11-06

UpCloud setup: choose Starter, Premium, or Cloud Native, then harden SSH

Build the server from the live Control Panel—not from memory—then discover the OS before you harden SSH.

Workload before headline price — verify the plan, terms and recovery path
How to use this. Steps reflect common operator problem-handling patterns and public UpCloud flows. Follow your live Control Panel labels; discover actual OS, services, and paths on your host before production changes.

Fresh / occupied gate and prerequisites

If the host already holds production data, workflows, or TLS material, stop. Follow the billing export → verify restore → delete gate before rebuild. Do not “fix” a live automation host from memory.

Private procurement record

  • Family hypothesis: Starter / Premium / Cloud Native.
  • Size hypothesis (RAM/CPU/disk)—conditional, not a tested minimum.
  • Datacenter preference (latency / residency).
  • Native only: storage tier (MaxIOPS / Standard / Archive) and size.
  • Simple Backup tier intent (or explicit none).
  • OS choice; SSH key ready in your password manager.
  • Prepaid balance / trial status; planned delete calendar if this is an experiment.

You perform signup and payment in your own browser. AiXVPS does not purchase or log into your Control Panel.

Build the server in the live Control Panel (not from memory)

Follow live labels. Captured flows change.

FieldVerifyFail if
LocationMatches users/data residency; plan available thereDC missing for chosen family
FamilyStarter vs Premium vs Native matches shut-down intentUsing discontinued Developer/GP/Flexible names
Plan sizeConditional envelope from reviewBuying Max RAM “just in case” with no observe plan
Storage (Native)Tier + GB attached intentionallyCompute-only Native with forgotten disk
OSSupported Linux you can operateWindows on docs trial quotas
Simple BackupDay/Week/Month/Year chosen knowinglyAssuming free Day backup on current Starter/Premium
SSH keysYour key uploaded before first loginPassword-only root left forever

Starter 1×1 concurrency limit

Pricing capture notes the cheapest 1 GB × 1 CPU Starter shape is limited to about five concurrent deployments per customer. If you need many tiny labs, confirm the live limit before spamming creates.

Read the bill before first login (balance, backups, transfer)

  • Confirm prepaid balance or trial credit state. If still on trial, write the live offer (homepage marketing vs docs 7-day/€10 conflict) into your notes.
  • Confirm Simple Backup percentage or per-GB line if enabled.
  • Note Fair Transfer TB row for the plan code—do not invent overage math.
  • Native: confirm storage and IPv4 lines separate from compute.
  • Save a private summary (screenshot/PDF). Never publish secrets.
Cash trap. Deploying Premium and “shutting down overnight to save money” does not stop plan billing. Delete when you mean stop spend.

First login: discover, then harden

Discovery first

Use the credentials/SSH path actually delivered. Marketplace-style defaults are UNKNOWN without deploy—do not invent passwords from blogs.

# illustrative discovery only — adjust to your OS
uname -a
cat /etc/os-release
ss -tulpn
df -h
ip -br a

SSH and firewall baseline

  1. Create a sudo admin user with your SSH key.
  2. Open a second working session before narrowing password/root login.
  3. Keep Control Panel console recovery available.
  4. Host firewall: intentional 22/80/443 only unless the app needs more—document exceptions.
  5. If still on trial, remember documented port locks; do not fight SMTP 25 with evasion tricks.

If any app image appears later

Research1 did not capture an official UpCloud n8n one-click. If you install from any image or tutorial later: record version paths, admin URL, and listening ports; never leave admin UIs world-open. Prefer the DIY Compose path for production ownership.

Day-zero acceptance receipt (then hand off)

  • Family, size, DC, storage, Simple Backup lines recorded.
  • Prepaid balance alert / auto top-up decision written.
  • SSH key-only path working; second session tested.
  • Firewall map documented; unexpected listeners closed.
  • Optional on-demand backup before first risky change—and a plan to delete leftovers.
  • Application export destination chosen (even if empty today).

Stop conditions: unexpected public listeners; unpaid backups you did not intend; Native disks left after a “temporary” stop; trial quota surprises; treating Fair Transfer as unlimited forever.

Hand off: AI apps · n8n · billing / delete discipline.