Het algemene Nextcloud topic

[WheeleE]

Na tig keer proberen een simpele lokale Nextcloud op te zetten sta ik op het punt om de boel permanent af te schrijven.
Ik heb een Caddy Proxmox LXC en een Docker host met daarop meerdere werkende apps benaderbaar via reverse proxy. Aan de hand van de Nextcloud documentatie en een deel van deze YT video vervolgens deze compose gefabriceerd (niet gebruikte regel verwijderd voor het overzicht:

code:

name: nextcloud-aio # Add the container to the same compose project like all the sibling containers are added to automatically.
services:
  nextcloud-aio-mastercontainer:
    image: ghcr.io/nextcloud-releases/all-in-one:latest # This is the container image used. You can switch to ghcr.io/nextcloud-releases/all-in-one:beta if you want to help testing new releases. See https://github.com/nextcloud/all-in-one#how-to-switch-the-channel
    init: true # This setting makes sure that signals from main process inside the container are correctly forwarded to children. See https://docs.docker.com/reference/compose-file/services/#init
    restart: always # This makes sure that the container starts always together with the host OS. See https://docs.docker.com/reference/compose-file/services/#restart
    container_name: nextcloud-aio-mastercontainer # This line is not allowed to be changed as otherwise AIO will not work correctly
    volumes:
      - nextcloud_aio_mastercontainer:/mnt/docker-aio-config # This line is not allowed to be changed as otherwise the built-in backup solution will not work
      - /var/run/docker.sock:/var/run/docker.sock:ro # May be changed on macOS, Windows or docker rootless. See the applicable documentation. If adjusting, don't forget to also set 'WATCHTOWER_DOCKER_SOCKET_PATH'!
    network_mode: bridge # This adds the container to the same network as docker run would do. Comment this line and uncomment the line below and the networks section at the end of the file if you want to define a custom MTU size for the docker network
    # networks: ["nextcloud-aio"]
    ports:
    #  - 80:80 # Can be removed when running behind a web server or reverse proxy (like Apache, Nginx, Caddy, Cloudflare Tunnel and else). See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md
      - 8099:8080 # This is the AIO interface, served via https and self-signed certificate. See https://github.com/nextcloud/all-in-one#explanation-of-used-ports
    #  - 8443:8443 # Can be removed when running behind a web server or reverse proxy (like Apache, Nginx, Caddy, Cloudflare Tunnel and else). See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md
    # security_opt: ["label:disable"] # Is needed when using SELinux. See https://github.com/nextcloud/all-in-one#are-there-known-problems-when-selinux-is-enabled
    environment: # Is needed when using any of the options below
      # AIO_DISABLE_BACKUP_SECTION: false # Setting this to true allows to hide the backup section in the AIO interface. See https://github.com/nextcloud/all-in-one#how-to-disable-the-backup-section
      APACHE_PORT: 11000 # Is needed when running behind a web server or reverse proxy (like Apache, Nginx, Caddy, Cloudflare Tunnel and else). See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md
      APACHE_IP_BINDING: 0.0.0.0 #127.0.0.1 # Should be set when running behind a web server or reverse proxy (like Apache, Nginx, 
      #Caddy, Cloudflare Tunnel and else) that is running on the same host. See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md
      SKIP_DOMAIN_VALIDATION: true # This should only be set to true if things are correctly configured. See https://github.com/nextcloud/all-in-one#how-to-skip-the-domain-validation

volumes: # If you want to store the data on a different drive, see https://github.com/nextcloud/all-in-one#how-to-store-the-filesinstallation-on-a-separate-drive
  nextcloud_aio_mastercontainer:
    name: nextcloud_aio_mastercontainer # This line is not allowed to be changed as otherwise the built-in backup solution will not work

en deze caddyfile entry:

code:

https://nextcloud.<mijndomein>.<tld>:443 {
    tls internal
    reverse_proxy 192.168.1.123:11000
}

Hiermee kom ik voorbij de doeinvalidatie (die geskipt wordt, zoals bedoeld).
Na het maken en starten van de diverse containers eindig ik hier:

In Docker zijn alle nextcloudcontainer healthy, m.u.v. de domaincheck, die is exited.
Klikken op "Open you Nextcloud" geeft in Firefox een "Did Not Connect: Potential Security Issue" error waar ik niet omheen kan. In andere browsers is de error "This page isn't working right now", met een http error 502.

Ik heb vanalles geprobeerd maar mijn Caddy & Docker kennis blijkt niet toereikend genoeg. Waarschijnlijk kijk ik ergens strak overheen of haal ik dingen door elkaar...maar wat en waar?