Skip to main content
OSSAlt

Self-Host Nextcloud: Cloud Storage & Collaboration 2026

·OSSAlt Team
nextcloudcloud-storagegoogle-driveself-hostingdocker2026
Share:

TL;DR

Nextcloud (AGPL 3.0, ~27K GitHub stars, PHP) is the most comprehensive self-hosted collaboration platform — Google Drive + Calendar + Contacts + Docs editing + Video calls, all in one. Google Workspace charges $6/user/month. Nextcloud replaces it entirely: file sync across all devices, real-time document editing (via Collabora or OnlyOffice), CalDAV/CardDAV sync to iOS/Android/macOS, and Nextcloud Talk for video calls. 300,000+ installs worldwide — used by the German government, universities, and enterprises.

Key Takeaways

  • Nextcloud: AGPL 3.0, ~27K stars, PHP — most feature-complete self-hosted Google alternative
  • Nextcloud Office: Real-time collaborative editing of DOCX/XLSX/PPTX via Collabora Online
  • CalDAV/CardDAV: Native calendar and contacts sync to iOS, Android, macOS, Thunderbird
  • Talk: Video calls, chat, screen sharing — Zoom/Teams alternative built-in
  • 250+ apps: Extend with Notes, Deck (kanban), Whiteboard, AI Assistant, etc.
  • External storage: Mount Google Drive, Dropbox, S3, SMB as external folders

Part 1: Docker Setup

# docker-compose.yml
services:
  nextcloud:
    image: nextcloud:latest
    container_name: nextcloud
    restart: unless-stopped
    ports:
      - "8080:80"
    volumes:
      - nextcloud_html:/var/www/html
      - nextcloud_data:/var/www/html/data
    environment:
      POSTGRES_HOST: db
      POSTGRES_DB: nextcloud
      POSTGRES_USER: nextcloud
      POSTGRES_PASSWORD: "${POSTGRES_PASSWORD}"
      NEXTCLOUD_ADMIN_USER: "${ADMIN_USER}"
      NEXTCLOUD_ADMIN_PASSWORD: "${ADMIN_PASSWORD}"
      NEXTCLOUD_TRUSTED_DOMAINS: "cloud.yourdomain.com"
      REDIS_HOST: redis
      SMTP_HOST: "smtp.yourdomain.com"
      SMTP_SECURE: "tls"
      SMTP_PORT: 587
      SMTP_NAME: "${SMTP_USER}"
      SMTP_PASSWORD: "${SMTP_PASS}"
      MAIL_FROM_ADDRESS: "cloud"
      MAIL_DOMAIN: "yourdomain.com"
    depends_on:
      db:
        condition: service_healthy
      redis:
        condition: service_started

  db:
    image: postgres:16-alpine
    restart: unless-stopped
    environment:
      POSTGRES_DB: nextcloud
      POSTGRES_USER: nextcloud
      POSTGRES_PASSWORD: "${POSTGRES_PASSWORD}"
    volumes:
      - db_data:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U nextcloud"]
      interval: 10s
      start_period: 20s

  redis:
    image: redis:7-alpine
    restart: unless-stopped

  # Cron job for background tasks:
  nextcloud-cron:
    image: nextcloud:latest
    container_name: nextcloud_cron
    restart: unless-stopped
    volumes:
      - nextcloud_html:/var/www/html
      - nextcloud_data:/var/www/html/data
    entrypoint: /cron.sh
    depends_on:
      - db
      - redis

volumes:
  nextcloud_html:
  nextcloud_data:
  db_data:

# .env
POSTGRES_PASSWORD=your-db-password
ADMIN_USER=admin
ADMIN_PASSWORD=your-admin-password

docker compose up -d

Part 2: HTTPS with Caddy

cloud.yourdomain.com {
    # CalDAV/CardDAV redirects (required for iOS/macOS auto-discovery):
    redir /.well-known/carddav /remote.php/dav 301
    redir /.well-known/caldav /remote.php/dav 301

    reverse_proxy localhost:8080
}

Part 3: Essential Configuration

After setup, run these optimizations:

# Add Nextcloud recommended settings:
docker exec -u www-data nextcloud php occ config:system:set default_phone_region --value="US"
docker exec -u www-data nextcloud php occ config:system:set maintenance_window_start --type=integer --value=1
docker exec -u www-data nextcloud php occ config:system:set log_type --value=file
docker exec -u www-data nextcloud php occ config:system:set loglevel --type=integer --value=2

# Enable Redis caching:
docker exec -u www-data nextcloud php occ config:system:set redis host --value=redis
docker exec -u www-data nextcloud php occ config:system:set redis port --type=integer --value=6379
docker exec -u www-data nextcloud php occ config:system:set memcache.local --value='\OC\Memcache\Redis'
docker exec -u www-data nextcloud php occ config:system:set memcache.locking --value='\OC\Memcache\Redis'

# Run initial maintenance:
docker exec -u www-data nextcloud php occ maintenance:repair
docker exec -u www-data nextcloud php occ db:add-missing-indices

Part 4: Nextcloud Office (Collabora)

Real-time collaborative document editing — edit DOCX, XLSX, PPTX in browser:

# Add to docker-compose.yml:
services:
  collabora:
    image: collabora/code:latest
    container_name: collabora
    restart: unless-stopped
    ports:
      - "9980:9980"
    environment:
      aliasgroup1: "https://cloud.yourdomain.com:443"
      username: admin
      password: "${COLLABORA_PASSWORD}"
      extra_params: "--o:ssl.enable=false --o:ssl.termination=true"
    cap_add:
      - MKNOD

# Add to Caddy:
office.yourdomain.com {
    reverse_proxy collabora:9980
}

In Nextcloud:

  1. Apps → Nextcloud Office → Install
  2. Settings → Administration → Nextcloud Office
  3. Use your own server → https://office.yourdomain.com

Now clicking any DOCX/XLSX opens the Collabora editor in your browser.

Part 5: Desktop Sync Clients

Desktop client setup

  1. Download Nextcloud Desktop (Windows/Mac/Linux)
  2. Log in → Server: https://cloud.yourdomain.com
  3. Choose sync folders

Mobile apps

iOS: Install Nextcloud from App Store → add server URL → auto-upload photos
Android: Install from Google Play or F-Droid → same setup → enable automatic photo upload

Part 6: Calendar (CalDAV)

iOS / macOS Calendar

  1. Settings → Calendar → Accounts → Add Account → Other → CalDAV
  2. Server: https://cloud.yourdomain.com
  3. Username: your Nextcloud username
  4. Password: your password (or create an App Password)

Android

Use DAVx⁵ (free on F-Droid):

  1. Install DAVx⁵
  2. + → Login with URL: https://cloud.yourdomain.com/remote.php/dav
  3. Username + password → sync calendars and contacts

Thunderbird

  1. Calendar → New Calendar → On the Network → CalDAV
  2. URL: https://cloud.yourdomain.com/remote.php/dav/calendars/username/personal/

Part 7: Nextcloud Talk (Video Calls)

Built-in video conferencing — Zoom alternative:

  1. Apps → Talk → Install
  2. Create a conversation → Video call icon

High-performance backend (for large calls, 5+ participants):

# Add Coturn TURN server for calls through NAT:
services:
  coturn:
    image: coturn/coturn:alpine
    network_mode: host
    volumes:
      - ./coturn.conf:/etc/coturn/turnserver.conf:ro

# In Talk admin settings:
# STUN server: stun.yourdomain.com:3478
# TURN server: turns:turn.yourdomain.com:3478 [shared secret]

Part 8: Notable Apps

Install from Apps in Nextcloud admin:

AppFunction
Nextcloud NotesMarkdown notes, iOS/Android sync
DeckKanban project boards
WhiteboardCollaborative infinite canvas
MailWeb email client (IMAP)
ContactsFull CardDAV address book UI
MusicSubsonic-compatible music player
PhotosAI photo management (basic)
External storageMount S3, Google Drive, Dropbox, SMB
SocialActivityPub-federated social network
CirclesTeam groups and sharing
Two-Factor TOTP2FA for accounts
Nextcloud AILLM assistant (configurable backends)

Part 9: User Management

# Create a user:
docker exec -u www-data nextcloud php occ user:add alice \
  --display-name "Alice Smith" \
  --group "users"

# List users:
docker exec -u www-data nextcloud php occ user:list

# Set storage quota:
docker exec -u www-data nextcloud php occ user:setting alice files quota 50GB

# Disable a user:
docker exec -u www-data nextcloud php occ user:disable alice

# Reset password:
docker exec -u www-data nextcloud php occ user:resetpassword alice

Maintenance

# Update Nextcloud:
docker compose pull
docker compose up -d
# Then run upgrade:
docker exec -u www-data nextcloud php occ upgrade
docker exec -u www-data nextcloud php occ db:add-missing-indices
docker exec -u www-data nextcloud php occ maintenance:mimetype:update-db

# Backup:
docker exec nextcloud-db-1 pg_dump -U nextcloud nextcloud \
  | gzip > nextcloud-db-$(date +%Y%m%d).sql.gz
tar -czf nextcloud-data-$(date +%Y%m%d).tar.gz \
  $(docker volume inspect nextcloud_nextcloud_data --format '{{.Mountpoint}}')

# Fix file permissions:
docker exec nextcloud chown -R www-data:www-data /var/www/html

# Logs:
docker compose logs -f nextcloud
docker exec -u www-data nextcloud php occ log:tail

Why Self-Host Nextcloud?

The case for self-hosting Nextcloud comes down to three practical factors: data ownership, cost at scale, and operational control.

Data ownership is the fundamental argument. When you use a SaaS version of any tool, your data lives on someone else's infrastructure subject to their terms of service, their security practices, and their business continuity. If the vendor raises prices, gets acquired, changes API limits, or shuts down, you're left scrambling. Self-hosting Nextcloud means your data and configuration stay on infrastructure you control — whether that's a VPS, a bare metal server, or a home lab.

Cost at scale matters once you move beyond individual use. Most SaaS equivalents charge per user or per data volume. A self-hosted instance on a $10-20/month VPS typically costs less than per-user SaaS pricing for teams of five or more — and the cost doesn't scale linearly with usage. One well-configured server handles dozens of users for a flat monthly fee.

Operational control is the third factor. The Docker Compose configuration above exposes every setting that commercial equivalents often hide behind enterprise plans: custom networking, environment variables, storage backends, and authentication integrations. You decide when to update, how to configure backups, and what access controls to apply.

The honest tradeoff: you're responsible for updates, backups, and availability. For teams running any production workloads, this is familiar territory. For individuals, the learning curve is real but the tooling (Docker, Caddy, automated backups) is well-documented and widely supported.

Server Requirements and Sizing

Before deploying Nextcloud, assess your server capacity against expected workload.

Minimum viable setup: A 1 vCPU, 1GB RAM VPS with 20GB SSD is sufficient for personal use or small teams. Most consumer VPS providers — Hetzner, DigitalOcean, Linode, Vultr — offer machines in this range for $5-10/month. Hetzner offers excellent price-to-performance for European and US regions.

Recommended production setup: 2 vCPUs with 4GB RAM and 40GB SSD handles most medium deployments without resource contention. This gives Nextcloud headroom for background tasks, caching, and concurrent users while leaving capacity for other services on the same host.

Storage planning: The Docker volumes in this docker-compose.yml store all persistent Nextcloud data. Estimate your storage growth rate early — for data-intensive tools, budget for 3-5x your initial estimate. Hetzner Cloud and Vultr both support online volume resizing without stopping your instance.

Operating system: Any modern 64-bit Linux distribution works. Ubuntu 22.04 LTS and Debian 12 are the most commonly tested configurations. Ensure Docker Engine 24.0+ and Docker Compose v2 are installed — verify with docker --version and docker compose version. Avoid Docker Desktop on production Linux servers; it adds virtualization overhead and behaves differently from Docker Engine in ways that cause subtle networking issues.

Network: Only ports 80 and 443 need to be publicly accessible when running behind a reverse proxy. Internal service ports should be bound to localhost only. A minimal UFW firewall that blocks all inbound traffic except SSH, HTTP, and HTTPS is the single most effective security measure for a self-hosted server.

Backup and Disaster Recovery

Running Nextcloud without a tested backup strategy is an unacceptable availability risk. Docker volumes are not automatically backed up — if you delete a volume or the host fails, data is gone with no recovery path.

What to back up: The named Docker volumes containing Nextcloud's data (database files, user uploads, application state), your docker-compose.yml and any customized configuration files, and .env files containing secrets.

Backup approach: For simple setups, stop the container, archive the volume contents, then restart. For production environments where stopping causes disruption, use filesystem snapshots or database dump commands (PostgreSQL pg_dump, SQLite .backup, MySQL mysqldump) that produce consistent backups without downtime.

For a complete automated backup workflow that ships snapshots to S3-compatible object storage, see the Restic + Rclone backup guide. Restic handles deduplication and encryption; Rclone handles multi-destination uploads. The same setup works for any Docker volume.

Backup cadence: Daily backups to remote storage are a reasonable baseline for actively used tools. Use a 30-day retention window minimum — long enough to recover from mistakes discovered weeks later. For critical data, extend to 90 days and use a secondary destination.

Restore testing: A backup that has never been restored is a backup you cannot trust. Once a month, restore your Nextcloud backup to a separate Docker Compose stack on different ports and verify the data is intact. This catches silent backup failures, script errors, and volume permission issues before they matter in a real recovery.

Security Hardening

Self-hosting means you are responsible for Nextcloud's security posture. The Docker Compose setup provides a functional base; production deployments need additional hardening.

Always use a reverse proxy: Never expose Nextcloud's internal port directly to the internet. The docker-compose.yml binds to localhost; Caddy or Nginx provides HTTPS termination. Direct HTTP access transmits credentials in plaintext. A reverse proxy also centralizes TLS management, rate limiting, and access logging.

Strong credentials: Change default passwords immediately after first login. For secrets in docker-compose environment variables, generate random values with openssl rand -base64 32 rather than reusing existing passwords.

Firewall configuration:

ufw default deny incoming
ufw allow 22/tcp
ufw allow 80/tcp
ufw allow 443/tcp
ufw enable

Internal service ports (databases, admin panels, internal APIs) should only be reachable from localhost or the Docker network, never directly from the internet.

Network isolation: Docker Compose named networks keep Nextcloud's services isolated from other containers on the same host. Database containers should not share networks with containers that don't need direct database access.

VPN access for sensitive services: For internal-only tools, restricting access to a VPN adds a strong second layer. Headscale is an open source Tailscale control server that puts your self-hosted stack behind a WireGuard mesh, eliminating public internet exposure for internal tools.

Update discipline: Subscribe to Nextcloud's GitHub releases page to receive security advisory notifications. Schedule a monthly maintenance window to pull updated images. Running outdated container images is the most common cause of self-hosted service compromises.

Troubleshooting Common Issues

Container exits immediately or won't start

Check logs first — they almost always explain the failure:

docker compose logs -f nextcloud

Common causes: a missing required environment variable, a port already in use, or a volume permission error. Port conflicts appear as bind: address already in use. Find the conflicting process with ss -tlpn | grep PORT and either stop it or change Nextcloud's port mapping in docker-compose.yml.

Cannot reach the web interface

Work through this checklist:

  1. Confirm the container is running: docker compose ps
  2. Test locally on the server: curl -I http://localhost:PORT
  3. If local access works but external doesn't, check your firewall: ufw status
  4. If using a reverse proxy, verify it's running and the config is valid: caddy validate --config /etc/caddy/Caddyfile

Permission errors on volume mounts

Some containers run as a non-root user. If the Docker volume is owned by root, the container process cannot write to it. Find the volume's host path with docker volume inspect VOLUME_NAME, check the tool's documentation for its expected UID, and apply correct ownership:

chown -R 1000:1000 /var/lib/docker/volumes/your_volume/_data

High resource usage over time

Memory or CPU growing continuously usually indicates unconfigured log rotation, an unbound cache, or accumulated data needing pruning. Check current usage with docker stats nextcloud. Add resource limits in docker-compose.yml to prevent one container from starving others. For ongoing visibility into resource trends, deploy Prometheus + Grafana or Netdata.

Data disappears after container restart

Data stored in the container's writable layer — rather than a named volume — is lost when the container is removed or recreated. This happens when the volume mount path in docker-compose.yml doesn't match where the application writes data. Verify mount paths against the tool's documentation and correct the mapping. Named volumes persist across container removal; only docker compose down -v deletes them.

Keeping Nextcloud Updated

Nextcloud follows a regular release cadence. Staying current matters for security patches and compatibility. The update process with Docker Compose is straightforward:

docker compose pull          # Download updated images
docker compose up -d         # Restart with new images
docker image prune -f        # Remove old image layers (optional)

Read the changelog before major version updates. Some releases include database migrations or breaking configuration changes. For major version bumps, test in a staging environment first — run a copy of the service on different ports with the same volume data to validate the migration before touching production.

Version pinning: For stability, pin to a specific image tag in docker-compose.yml instead of latest. Update deliberately after reviewing the changelog. This trades automatic patch delivery for predictable behavior — the right call for business-critical services.

Post-update verification: After updating, confirm Nextcloud is functioning correctly. Most services expose a /health endpoint that returns HTTP 200 — curl it from the server or monitor it with your uptime tool.

See all open source cloud storage tools at OSSAlt.com/categories/storage.

See open source alternatives to Nextcloud on OSSAlt.

The SaaS-to-Self-Hosted Migration Guide (Free PDF)

Step-by-step: infrastructure setup, data migration, backups, and security for 15+ common SaaS replacements. Used by 300+ developers.

Join 300+ self-hosters. Unsubscribe in one click.