How to self-host Nextcloud

Your own private cloud for files, calendar and contacts (has its own setup on first open). Cresdock runs it on a server you own, from a catalogue, with no Docker and no reverse proxy to configure.

What Cresdock does for you with Nextcloud

Its configuration is written before the container ever starts, so Nextcloud comes up already set up rather than showing you a blank first-run form.
Given its own web address, with its own login seeded in advance. Nextcloud can't live under a shared path, and apps like this are reached by clients that don't carry a browser session — so it gets a real password rather than being left open.
Gets its own web address and a generated admin password on install — shown once on the app card, so there's no shared or default credential.
Configures itself automatically on first boot (admin account, database, trusted domain) — you sign in and it's ready, no setup wizard to run through by hand.

Why run Nextcloud yourself

Cloud storage is rented, priced per month forever, and readable by whoever runs it. The same files on a server you own cost what the disk cost.

It is also how you retire Dropbox or Google Drive — one line in replacing cloud subscriptions, app by app.

What kind of server Nextcloud needs

Light on power, heavy on disk — sizing is really a question of how much you want to keep. If your library outgrows the server, Cresdock can put it on cloud storage and keep it looking like a normal folder.

Cresdock itself is undemanding — it runs on a small rented server, an old desktop or a mini PC, on Ubuntu or Debian. Everything it installs shares that machine, so the honest question is not "will this app run" but "how much am I going to put on here in total".

Where to run Nextcloud

Nextcloud runs wherever Cresdock runs, and the choice is about the machine, not the app:

At home, on hardware you already own. A mini PC, an old desktop or a NAS that can run Debian. Cresdock works behind a home router with no port forwarding and no domain, so Nextcloud is reachable on your own network first and from outside only if you choose.
On a rented server. A small VPS is enough for most apps and is the usual answer when Nextcloud should be reachable from anywhere. The setup guide covers the specs and the one-command install.
Through a provider that runs Cresdock. Hosting companies deploy Cresdock workspaces for their customers, so Nextcloud can come with a server you rent rather than one you set up — ask your provider, or see how providers offer it.

Installing Nextcloud

Put Cresdock on a server
One line on any Ubuntu or Debian machine — a rented VPS, a spare PC, a home server. It sets itself up.
Pick Nextcloud from the catalogue
Click Install. The panel pulls the image, writes the configuration, gets a certificate and starts it.
Open it from your dashboard
Its address and any login details are on its card. Start, stop, update, roll back or remove it from the same place, any time.

What's left for you to do

Cresdock does not pretend to do the parts that are genuinely yours to decide. After it's running:

Open Nextcloud and sign in with the admin details on this tile

What this replaces

Doing it by hand means writing something like this, then keeping it working:

services:
  nextcloud:
    image: nextcloud:34
    restart: unless-stopped
    ports:
      - "80:80"
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
    volumes:
      - ./nextcloud/config:/config

And that is the easy half. Still to do:

Install a reverse proxy and write a server block for it
Get a TLS certificate and set up automatic renewal
Create the folders above with the right ownership, or it will not start
Point a DNS record at the server, because Nextcloud cannot run under a shared path
Repeat all of it for the next app, and again on every server rebuild

On Cresdock, Nextcloud is one click and none of the above exists.

Common questions

Do I need to know Docker to run Nextcloud?

No. Cresdock installs Nextcloud in one click from its catalogue: it pulls the image, writes the configuration, gets an HTTPS certificate and starts it. Nextcloud gets its own web address and its own certificate, because it cannot run under a shared path.

What happens to my Nextcloud data when it updates?

Cresdock updates the Nextcloud image and leaves its stored data in place. Nextcloud keeps its own files in its own folder, which survives an update, a rebuild and a reinstall — and Cresdock never writes into it.

How is Nextcloud protected if it isn't behind the panel login?

It gets its own password, generated and set before it first starts, shown on its card in your dashboard. Apps end up here when they are reached by programs rather than a web browser, so a shared login can't be used.

Who can see the files I put in Nextcloud?

Only you. Your folders belong to your account, other people on the server have their own, and each account's apps run on a private network of their own. Updates and reinstalls never touch what you have stored.

Can I run Nextcloud at home instead of on a VPS?

Yes. Cresdock runs on a mini PC, an old desktop or anything that boots Debian, behind a normal home router with no port forwarding, and Nextcloud is reachable on your own network first. A rented server is only needed when Nextcloud must be reachable from anywhere without a VPN.

Can I remove Nextcloud later?

Yes. Cresdock removes Nextcloud in one click, and asks whether to keep its configuration for a future reinstall. Nothing else you have installed is affected.

Looking for what Nextcloud itself can do? That lives in its own documentation — this page is only about running it.

Pairs well with: File Browser Quantum · Rclone · NZBHydra2

Before you start: where to rent a server · what it needs to run · Cresdock vs CasaOS