SSD Nodes Learn Hosting plans →
How to do am Matt ConnorBy Matt Connor

How to Install Cloudron on Ubuntu VPS

Install Cloudron on a fresh Ubuntu VPS with the wildcard DNS record, setup script and reboot. Check the 2 GB RAM minimum, mail, TLS certificates and backups.

Cloudron install for VPS: short version

To install Cloudron for VPS, you need fresh Ubuntu server, at least 2 GB RAM, and domain wey you fit edit im DNS records. The install itself na three commands and one reboot. Almost everything wey fit go wrong dey happen before this step (wrong base image, wrong virtualisation type) or after am (DNS, mail, backups).

wget https://cloudron.io/cloudron-setup
chmod +x cloudron-setup
sudo ./cloudron-setup

Cloudron dey install, update, back up, and issue TLS (transport layer security) certificates for self-hosted apps. Every app dey run inside Docker, nginx dey in front of all of dem, and every app get im own subdomain for your domain. Na this last detail make the DNS work come first here.

Why Cloudron dey fussy about the base OS

The setup script dey check the server before e install anything, and if any check fail, you go need order another server. Read dem before you pick an image. The installer checks wey this section quote come from October 13, 2026; the current installation documentation dey ask for fresh Ubuntu 26.04 server.

  • Na Ubuntu only, and na just three releases. Anything else go exit with Cloudron requires Ubuntu 22.04, 24.04, 26.04. Ubuntu 20.04 no pass, and the install documentation now dey ask for fresh Ubuntu 26.04 server. Debian, Rocky and Alpine no dey supported. Ubuntu 24.04 need Cloudron 8 or newer, and the script go check that for you.
  • Na 64-bit Intel or AMD only: Error: Cloudron only supports amd64/x86_64. ARM VPS no fit run am.
  • Na full hardware virtualisation only. For container-based VPS, the script go stop with Error: Cloudron does not support lxc, only runs on bare metal or with full hardware virtualization, because e dey detect the container with systemd-detect-virt --container. KVM dey okay. OpenVZ and LXC no dey supported.
  • The root filesystem must be ext4 or xfs. For anything else, you go get Error: Cloudron requires '/' to be ext4 or xfs, and na so btrfs and zfs images dey fail.
  • You need at least 941 MB RAM, measured with free -m, and 18 GB on /, measured as the root filesystem size. The error message dey ask for 20GB, but the check itself accepts 19 GB root filesystem.
  • The server must genuinely fresh. If nginx, docker or node don already install, the script go refuse with Error: Some packages like nginx/docker/nodejs are already installed.

Na this last check people dey argue about pass, so make we explain why. Cloudron dey install pinned versions of Docker, nginx, Node.js and MySQL, write the nginx configuration for every app wey e host, and manage the iptables firewall rules by itself. Docker wey you install yesterday fit be the wrong version, so the script go exit without changing anything and tell you make you start with fresh Ubuntu install. Cloudron dey control the whole machine, so give am dedicated VPS.

Another check easy to miss. For older CPU wey no get AVX (advanced vector extensions), the script go print CPU has no AVX support. MongoDB will be disabled, and every app wey need MongoDB go become uninstallable. Check the CPU before you commit with grep -m1 -o avx /proc/cpuinfo, wey go print avx for capable host and nothing for old one.

Cloudron need how much RAM?

The October 13, 2026 installer check no gree run under 941 MB, with Error: Cloudron requires atleast 1GB physical memory; the current documentation dey ask for 2 GB of RAM and 20 GB of disk. Both numbers na the minimum for the platform, not for the platform plus your apps. Cloudron dey run Docker, nginx, e own box service and the mail stack, and e dey provision shared database services as you deploy apps. Run docker ps for fresh install and count dem.

App memory limits dey add on top of that base. Each app package dey come with small default limit, and you fit increase am with the slider for the app's Resources view. When app pass its limit, e restart and send you OOM (out of memory) notification. So if one box dey restart one app again and again, na usually limit problem, no be bug.

This na the sizing I go order. Dem na recommendations for server wey you no go need rebuild next month. Dem no be measured benchmark results.

ChartCloudron VPS sizing floor by number of apps
Di data wey dey behind dis chart
[
  {
    "label": "2 apps (free tier)",
    "vcpu": 2,
    "ram_gb": 4,
    "disk_gb": 60
  },
  {
    "label": "5 apps",
    "vcpu": 4,
    "ram_gb": 8,
    "disk_gb": 120
  },
  {
    "label": "10 apps",
    "vcpu": 6,
    "ram_gb": 16,
    "disk_gb": 240
  }
]

Two apps dey comfortable on 4 GB of RAM and 60 GB of disk. Around ten apps need 16 GB and 240 GB, because the platform base no dey reduce and every app dey add one Docker image, one database and e own data. Disk dey fill faster than people expect: images, app data and local backups dey share one volume until you move backups comot from the box.

Cloudron dey give every app unlimited swap, so the memory limit wey you set na for RAM only. For VPS image wey no get swap file, swapon --show no dey print anything, and memory pressure dey turn directly to OOM restarts instead of making the app slow. Adding 2 GB of swap na cheap insurance, but e no replace real memory. The gap between VPS plans small compared with the hours you go spend tuning limits, so see wetin VPS really cost and buy the next size up.

DNS: wildcard record wey make app subdomains work

Cloudron dey put dashboard for my.example.com and every app for im own subdomain, so DNS na requirement, no be step wey you go do later. Point these records to the server public IP address before you open the dashboard for the first time:

  • my.example.com as an A record. Na the dashboard be this.
  • *.example.com as an A record. Na this one dey make app subdomains work, so wiki.example.com and git.example.com go resolve immediately once you install those apps.
  • example.com as an A record, only if you want app for the bare domain.

Wildcard record get lower precedence than explicit record, so existing www.example.com wey dey point somewhere else go continue to work.

During setup, you go choose how Cloudron go handle DNS from that point:

  • An API provider. Cloudron go store token for Cloudflare, DigitalOcean, Route53, Hetzner, Porkbun, Linode, deSEC, Gandi, Namecheap, Hostinger DNS, Scaleway DNS and others (22 API DNS integrations altogether, excluding Wildcard, Manual and No-op), then e go write every record by itself, including mail records.
  • Wildcard. You go add * record by hand and Cloudron no go write anything.
  • Manual. Cloudron go show you each record and wait while you add am, before every single app installation.

Wildcard DNS record no be wildcard certificate. The default certificate provider na Let's Encrypt Prod - Wildcard, wey dey prove ownership through DNS, so e only works with API provider. For Wildcard or Manual backends, Let's Encrypt dey issue individual certificates wey HTTP validates, and this one requires inbound port 80 for issuance and renewal. You fit disable Let's Encrypt integration instead and upload custom wildcard certificate, so port 80 no go remain permanent requirement for certificate validation. If your registrar or DNS host dey for the API list, use am: mail records and certificates both no go remain your responsibility.

Verify before you continue. dig +short my.example.com and dig +short anything.example.com suppose both print your server IP address. For Wildcard backend, if wildcard query print nothing, apps go fail later while the dashboard dey work fine.

If the domain dey behind Cloudflare, set the records to DNS only. The proxy dey forward only HTTP and HTTPS, so mail ports go break. For proxied web apps, Cloudron Network view supports trusting Cloudflare published IP ranges, so e fit recover visitor address from forwarded headers.

Run setup script

wget https://cloudron.io/cloudron-setup
chmod +x cloudron-setup
sudo ./cloudron-setup

Run am as root or through sudo, because the first thing e go print otherwise na This script should be run as root.. Installation fit take several minutes, and e no go print much while e dey work, because apt output and Docker pulls dey go log file. Monitor am from another SSH session:

tail -f /var/log/cloudron-setup.log

For the October 13, 2026 installer check, e print After reboot, visit one of the following URLs and accept the self-signed certificate to finish setup. followed by the server address, then ask The server has to be rebooted to apply all the settings. Reboot now ? [Y/n]. Answer yes. That installer also provide --skip-reboot flag wey fit defer the restart.

First boot: domain, DNS backend and the admin account

Open https://<server-ip> and accept the browser warning. The certificate na self-signed because Cloudron never know your domain yet, so e no get anything to ask certificate authority for. For Chrome, click Advanced, then Proceed to <ip> (unsafe). For Firefox, click Advanced, then Accept the Risk and Continue.

The first screen go ask for your domain. Enter example.com and the dashboard go settle for my.example.com. You fit use subdomain like cloudron.example.com instead, then the dashboard go dey for my.cloudron.example.com. Choose the DNS backend, paste the API token if you get one, and create the admin account with email address wey you dey really read: password reset and platform notifications go use am.

When you save, Cloudron go request certificates and move the dashboard go https://my.example.com. The IP address URL go stop working then, so bookmark the new one.

Certificates: wetin dey renew, and when e go stop

Certificate renewal dey happen automatically and e follow ACME Renewal Information (ARI), wey be the schedule certificate authority publish. For practice, renewal dey happen about one month before certificate expiry. If renewal fail, admin account go receive email. If certificate expire, system go fall back to the built-in self-signed one. Na this fallback browser warning dey mean when site wey work yesterday suddenly show warning.

Two causes dey responsible for most cases. HTTP validation need inbound port 80. So, if you close 80 because "everything na HTTPS anyway", renewal go fail for apps wey use Let's Encrypt HTTP validation with Wildcard or Manual DNS backend. DNS validation need API token wey still get write access. If you rotate or reduce the token access, renewal go fail silently until the warning email arrive.

The Domains view get a Renew All button wey fit force the attempt immediately, plus a Let's Encrypt Staging provider for testing. Browsers no trust Staging certificates deliberately. Na the purpose be that: testing no go use production rate limits. Staging get separate limits, including 200 authorization failures per identifier per account per hour.

You suppose use the built-in mail server?

Cloudron releases complete mail stack with IMAP mailboxes, submission, sieve filters and DKIM (domainkeys identified mail) signing. You enable am for each domain under Email for the dashboard. The hard part na to make mail deliver, and Cloudron no cause any of the difficulty.

  • Most VPS providers block outbound port 25 to control spam. Some go unblock am after you open support ticket. Test am from the server with nc -zv aspmx.l.google.com 25 (install netcat-openbsd if the command no dey). Open ports go report succeeded, and blocked port go hang until e timeout.
  • Your VPS provider sets the PTR record (reverse DNS), not your DNS host. E must match the mail hostname when you send directly from the server. Smart host go remove this PTR requirement.
  • For API DNS backend, the system go write SPF, DKIM and DMARC records for you. For Wildcard or Manual backend, you must add dem by hand. If DKIM record dey missing, nobody fit verify any message you sign.

The setup wey work for most people na to receive mail on Cloudron and send through relay like SendGrid, Postmark, Mailgun or Amazon SES, configured for the Email view. The relay must allow sending as any address for your domain. Otherwise, e go reject app notifications from different senders. If mail na the main reason you dey buy the server, run dedicated mail server like Mailcow for its own box with its own IP reputation.

If you no use Cloudron Email at all, block ports 25, 465, 587, 993 and 4190 for your provider's firewall. Do am there, not for the server, because Cloudron dey write the iptables rules by itself and expects to own dem. This one different from plain VPS, where you manage ufw rules by yourself.

Set up backup target before you need am

Backups dey default go local filesystem for /var/backups, for the same disk wey everything dey use. Documentation talk am direct: "E dangerous make backups dey for the same physical disk with the platform server." One disk failure fit carry apps and backups together.

Open Backups, then Backup Sites, and point am go another place from day one. S3-compatible object storage na the usual answer (Backblaze B2, Wasabi, Cloudflare R2, DigitalOcean Spaces, or a MinIO bucket for another server), and SSHFS, NFS, CIFS plus plain filesystem targets dey supported too.

Three settings decide whether that backup get value:

  • Format. tgz dey write one compressed archive for each app and re-upload everything every run. rsync dey upload only files wey change, so e cheaper for large Nextcloud, but e go make more requests go storage API.
  • Encryption. Optional AES-256 wey cover both file contents and filenames. Cloudron no keep copy of the password, so if you lose am, nobody fit decrypt the backups, including you. Store am for self-hosted password manager before you click save.
  • Retention. Dem dey write am as counts like 7 daily and 4 weekly. Long retention for object storage go bill you every month, so choose number wey you ready continue to pay for.

Then test restore. Install small app, restore am from dashboard, and monitor am as e come back with the data. Backup wey nobody don ever restore na just guess.

Wetín the free tier dey limit

As of October 2026, the free plan get limit of two installed apps. Everything else dey included: app updates, backup for each app, firewall, mail server, and single sign-on. Na the third app be the point wey you need licence. The paid plans remove the app limit, and the higher plan add user groups and roles, directory server, and multiple backup sites. Prices fit change, so check Cloudron pricing page instead of relying on number wey tutorial write.

One licence cover one Cloudron install, so two small servers go cost twice wetin one bigger server cost. This pricing make most people use one bigger VPS, but e go against the usual advice to spread services across different machines. Size the server with this one for mind, because if you split am later, you go pay twice.

When something break

Start with the built-in check. E go check DNS, certificates, disk, memory and each service one after another, then tell you which test fail:

sudo cloudron-support --troubleshoot

After that, use the normal systemd (system and service manager) tools. systemctl status box go show the Cloudron service itself, journalctl -u box -n 100 go show the recent logs, and journalctl -u docker go cover the container runtime underneath. Anything wey go wrong during installation dey inside /var/log/cloudron-setup.log.

If dashboard no load, na usually DNS or provider firewall, no be Cloudron. Run dig +short my.example.com from your laptop and confirm say ports 80 and 443 dey open for provider network firewall. This firewall control separate from the server own rules. For the October 13, 2026 installer check, second run was refused with Error: Cloudron is already installed. To reinstall, start afresh; rebuilding the server na the clean answer.

Cloudron no be the right fit

Cloudron dey work well when you want applications, no be infrastructure. E no dey work well when you want run your own containers your own way, because e dey control nginx, Docker and firewall, and e go overwrite anything wey you put there. If your plan na folder of compose files, Traefik in front of your own Docker Compose stacks go give you the same automatic TLS and subdomain routing without any platform on top. If you never choose yet, Cloudron, CasaOS and Coolify compared go show dem side by side, while the wider list of what to self-host na better place to start than install guide.

FAQ

How much RAM Cloudron need for VPS?

The October 13, 2026 installer check no gree run under 941 MB; the current documentation dey ask for 2 GB, but na the minimum for the platform when no app dey inside. Cloudron dey run Docker, nginx, im own box service and mail stack, and e dey provision shared database services as you deploy apps. Plan 4 GB for two apps and 16 GB for around ten apps, then add swap file, because Cloudron dey give apps unlimited swap and server wey no get swap fit turn memory pressure to restarts.

I fit install Cloudron for Debian, or for server wey already dey run Docker?

Neither one go work. For the October 13, 2026 installer check, the script stop for unsupported releases with Cloudron requires Ubuntu 22.04, 24.04, 26.04 and e reject servers wey already get nginx, docker or node. The current installation documentation require fresh Ubuntu image and e exclude Debian, Rocky and Alpine. Start with fresh Ubuntu image for KVM VPS.

Why my app subdomains dey fail while dashboard dey work?

For Wildcard backend, check wildcard DNS record. Setup dey create or require A record for my.example.com, so dashboard dey resolve, while wiki.example.com dey return NXDOMAIN and browser dey report say e no fit find the site. Add A record for *.example.com wey point to server IP, then confirm with dig +short wiki.example.com before you install the app.

I must use Cloudron mail server?

No. You fit leave incoming email off and send through external relay like Postmark, Mailgun or Amazon SES. This one safer when your provider dey block outbound port 25 or the IP address no get mail reputation. If you skip Cloudron Email completely, close ports 25, 465, 587, 993 and 4190 for provider firewall instead of server.

Wetin go happen when I reach two-app limit for free plan?

You need paid subscription to install third app. Apps wey you already dey run no go change: dem go continue to update, continue to get backed up and keep their certificates. When you add subscription, e go remove the limit without reinstalling anything. So free plan na fair way to test the platform for real domain first.

Dis article help you?