Zum Inhalt springen
TutorialsErste SchritteAnfänger

How to Install Nextcloud with Docker

Deploy a private cloud for files, calendars and contacts using Docker Compose, with MariaDB, Redis, HTTPS and a solid backup plan.

von HomeServersGuide TeamAktualisiert 3. November 20266 Min. Lesezeit

What you'll build

Nextcloud is a self-hosted replacement for Google Drive, Dropbox, Google Calendar and Google Contacts rolled into one. By the end of this tutorial you'll have a private cloud running in Docker with a proper database (MariaDB), a caching layer (Redis), automatic HTTPS, and a backup routine so your data is safe.

This guide targets a typical home server running Linux with Docker and Docker Compose already installed. Plan for about 30 minutes.

Why the "full" stack instead of the all-in-one image

You can run Nextcloud from a single container, but for anything beyond testing you want:

  • MariaDB instead of the bundled SQLite — far better performance and reliability once you have real data and multiple users.
  • Redis for file locking and caching — this removes the "transactional file locking" warnings and makes the UI noticeably snappier.
  • A reverse proxy for TLS — so you connect over HTTPS with a clean hostname.

Step 1: Plan your storage

Decide where two kinds of data live:

  • Config and database — small, but critical. Keep it on your fast SSD.
  • User files — potentially large. This can live on a bigger drive or a mounted NAS share.

Create a folder structure:

mkdir -p ~/nextcloud/{db,redis,html,data}
cd ~/nextcloud

Step 2: Create the Docker Compose file

Create compose.yaml:

services:
  db:
    image: mariadb:11
    command: --transaction-isolation=READ-COMMITTED --log-bin=ROW
    restart: unless-stopped
    volumes:
      - ./db:/var/lib/mysql
    environment:
      - MARIADB_ROOT_PASSWORD=change-me-root
      - MARIADB_DATABASE=nextcloud
      - MARIADB_USER=nextcloud
      - MARIADB_PASSWORD=change-me-db
 
  redis:
    image: redis:7-alpine
    restart: unless-stopped
    volumes:
      - ./redis:/data
 
  app:
    image: nextcloud:29-apache
    restart: unless-stopped
    ports:
      - "8080:80"
    depends_on:
      - db
      - redis
    volumes:
      - ./html:/var/www/html
      - ./data:/var/www/html/data
    environment:
      - MYSQL_HOST=db
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud
      - MYSQL_PASSWORD=change-me-db
      - REDIS_HOST=redis
      - NEXTCLOUD_TRUSTED_DOMAINS=cloud.example.com

Replace the passwords with strong, unique values and set NEXTCLOUD_TRUSTED_DOMAINS to the hostname you'll use.

Step 3: Start the stack

docker compose up -d
docker compose logs -f app

The first start takes a minute while Nextcloud initializes the database. When the logs settle, open http://your-server-ip:8080 and create your admin account.

Step 4: Put it behind HTTPS

Never expose Nextcloud over plain HTTP. Publish it through a reverse proxy such as Caddy or Nginx Proxy Manager, which will obtain a free Let's Encrypt certificate automatically. With Caddy it's as little as:

cloud.example.com {
    reverse_proxy localhost:8080
}

Step 5: Fix the common warnings

Open Administration settings → Overview. Two fixes clear most warnings:

  • Missing indices / MIME types — run the maintenance commands via occ:
docker compose exec --user www-data app php occ db:add-missing-indices
docker compose exec --user www-data app php occ maintenance:repair
  • Phone region / default region — set default_phone_region in config.php.

Step 6: Install the apps that matter

From the app store, enable:

  • Calendar and Contacts for CalDAV/CardDAV sync with your phone.
  • Notes and Tasks if you want a Google Keep / to-do replacement.
  • Nextcloud Office (Collabora) for editing documents in the browser.

Connect your phone using the official Nextcloud app for file sync and the DAVx5 app (Android) for calendars and contacts.

Step 7: Back it up

Your Nextcloud is only as safe as your backups. Follow the 3-2-1 backup strategy:

  1. Put the instance in maintenance mode before backing up:
docker compose exec --user www-data app php occ maintenance:mode --on
  1. Back up the db, html, and data folders (or dump the database with mysqldump and copy the files).
  2. Turn maintenance mode off again.

Automate this with a nightly script and send the archive offsite with Restic or Duplicati.

Step 8: Background jobs, performance and tuning

Nextcloud runs maintenance tasks regularly. By default it uses "AJAX", which only runs when someone opens the web interface; switch to Cron for reliability. Under Administration settings → Basic settings, choose Cron, then add a host cron job:

*/5 * * * * docker compose -f /home/you/nextcloud/compose.yaml exec -T --user www-data app php -f /var/www/html/cron.php

To make the interface faster:

  • Keep the database and html folder on an SSD.
  • Make sure Redis is configured (the example does this) and PHP OPcache is enabled; the official image sets reasonable defaults.
  • Raise the PHP memory limit and upload limits for large files with environment variables (PHP_MEMORY_LIMIT, PHP_UPLOAD_LIMIT).
  • Use the Preview Generator app to pre-create thumbnails if a photo-heavy library feels slow, or use Immich for photos.

Step 9: Behind a reverse proxy: the settings people miss

When Nextcloud sits behind Caddy or Nginx Proxy Manager, tell it about the proxy so links and security checks work. In config/config.php set the trusted proxy and overwrite values, for example:

'trusted_proxies' => ['172.18.0.0/16'],
'overwriteprotocol' => 'https',
'overwrite.cli.url' => 'https://cloud.example.com',

Also redirect the CalDAV and CardDAV discovery URLs (/.well-known/caldav and /.well-known/carddav) to /remote.php/dav, which the admin overview will remind you about. Enable HSTS only after you are sure HTTPS works.

Step 10: Security hardening

  • Enable two-factor authentication (the TOTP app) for every user, and require it for admins.
  • Use unique, long passwords and consider app passwords for sync clients.
  • Keep Nextcloud, apps and the OS updated; subscribe to security announcements.
  • Don't expose the server directly if you can avoid it; use a VPN or a reverse proxy with Fail2ban. See the security checklist.
  • Review sharing settings: limit public links, set expiry dates and require passwords.
  • Consider server-side or end-to-end encryption only after reading the trade-offs, because it complicates recovery.

Step 11: Upgrading safely

Nextcloud upgrades one major version at a time. Never skip a major version.

  1. Back up the database, html and data folders (see Step 7).
  2. Change the image tag by one major version (for example from 29-apache to 30-apache).
  3. Run docker compose pull && docker compose up -d, and watch the logs.
  4. Check Administration → Overview and re-run the occ repair commands if needed.
  5. Check that your apps are compatible before upgrading.

Pin the tag instead of using latest; see Docker Compose best practices.

Alternatives: Nextcloud AIO and ownCloud

The official All-in-One image bundles everything with a web-based manager and automatic updates and backups; it's a good choice if you want less manual work. If you only need file sync, compare Nextcloud vs ownCloud.

Troubleshooting

  • "Access through untrusted domain" — add the hostname to NEXTCLOUD_TRUSTED_DOMAINS or trusted_domains in config.php.
  • Slow uploads of large files — increase client_max_body_size in your reverse proxy and PHP upload_max_filesize.
  • 502 from the proxy — confirm the app container is healthy and the proxy targets the correct port.

Next steps

Once Nextcloud is stable, explore external storage (mount a NAS share), enable two-factor authentication for every account, and consider Immich for a dedicated photo-backup experience alongside it.

Verwandte Artikel

AnleitungenErste SchritteAnfänger

Der komplette Heimserver-Leitfaden für Einsteiger

Von null zum laufenden Heimserver: Hardware wählen, Betriebssystem auswählen, erste Apps bereitstellen und alles sicher und gesichert halten.

5 Min. Lesezeit
AnleitungenErste SchritteAnfänger

Einsteigerleitfaden für Self-Hosting

Erfahre, welche Cloud-Dienste du durch selbst gehostete Alternativen ersetzen kannst und wie du startest.

4 Min. Lesezeit
VergleicheErste SchritteAnfänger

Nextcloud vs. ownCloud

Vergleiche die beiden Private-Cloud-Forks: Funktionen, Apps, Lizenzen und was ins Homelab passt.

5 Min. Lesezeit