Self Managed
Cloud killer time
Start replacing cloud services with services you understand and control.
Can the Quick Start server handle it?
Once the Quick Start is complete, Nextcloud is a useful next project for files, calendars, and contacts. Add one service, learn to update and restore it, then decide what else to move.
The HP ProDesk 600 G1 with an i5-4590T, 8 GB of RAM, and a 500 GB SSD is a reasonable starting point for an estimated two to four light users of basic file sync, calendars, and contacts. This is a planning estimate, not a tested capacity guarantee. Large photo imports, simultaneous uploads, office collaboration, and indexing can change the workload substantially.
Watch memory, CPU, and disk use in Beszel. Leave headroom for Ubuntu, databases, and the tools already running. Add services gradually and measure their effect before moving important data.
What to move first
| Need | Starting point | What to expect |
|---|---|---|
| Files and folders | Nextcloud Files | Sync selected folders and share files from your own server. |
| Calendar and contacts | Nextcloud Calendar / Contacts | Use compatible CalDAV and CardDAV clients. Test every device before retiring the old service. |
| Photo backup, later | Immich, optionally | A separate workload. Current documentation recommends 8 GB RAM, so a shared 8 GB host may need more memory or fewer competing services. |
A manageable rollout
- Start with a test library. Use copies of noncritical files and keep your existing service while testing.
- Choose a supported installation. Follow the official Nextcloud installation guide for your chosen method. Containers simplify packaging, but you still own updates, storage, and recovery.
- Plan private access. Keep using your tailnet. Follow the documented HTTPS and reverse proxy setup for your installation; a Tailscale IP alone does not configure trusted domains or certificates. Avoid opening router ports just to finish a tutorial.
- Create separate accounts. Give each person their own login, enable multi-factor authentication where supported, and share only the folders they need.
- Test the clients. Upload, edit, delete, and restore a test file from each device. Test contacts and calendars separately.
- Back up, then migrate in batches. Prove that you can restore both data and application state before moving the only copy of anything.
Storage and backups
A 500 GB SSD fills quickly when it holds the operating system, containers, a database, and everyone’s photos. Budget for existing data, growth, previews, and spare capacity. Add a NAS on your network or storage connected directly to the server when needed.
Use a stable mount and the storage method supported by your installation. Storage must be available before its containers start. The database and configuration matter too: copying only the files directory is not a complete restore plan.
A NAS or second drive in the same machine is not, by itself, a backup. Keep a separate recovery copy and a copy away from the server. Test restoration, and encrypt backups that leave your control.
Security update: October 21, 2026
Apply the PHP security updates promptly. PHP released fixes on October 21, 2026 for CVE-2026-109618 and CVE-2026-109619, critical vulnerabilities that can allow unauthenticated remote code execution. They affect PHP itself and can affect Nextcloud using a vulnerable runtime; they are not limited to Nextcloud.
The upstream fixes were released in PHP 8.2.35, 8.3.36, 8.4.27, and 8.5.12. Use a supported patched release compatible with your Nextcloud version, or a vendor package with the fixes backported. For containers, update through your image provider’s supported process and recreate the affected containers. Updating host PHP alone does not patch PHP inside a container.
Verify the runtime that actually serves Nextcloud; host command-line PHP may differ. A VPN or login screen is not a substitute for installing the fix.
PHP release announcement · CVE-2026-109618 · CVE-2026-109619