Config help for Docker Nextcloud AIO

ℹ️ Support
, , , ,
1

Hi all,

after my last question (seperate nextcloud and nginx/php docker) I wanted to test the Nextcloud AIO docker package, but I’m facing some problems.

Situation:
I want to use Nextcloud AIO only in my local network on my rpi4, no access from Internet. And no NGinx Proxy manager or similar.
Only the AIO package.

I’ve taken the example docker-compose and adjusted it on my setup (or what I think it could be right).
But it’s not working and I don’t know what is wrong.

Sometimes I could start the install, but nextcloud itself was not reachable. Also the certificate seems to be wrong created (everytime detected as not safe certificate)
Before I start the next try. It is possible that somechecks my configs, if there are any mistakes? Or what could be improved?

compose.yaml

services:
  nextcloud:
    image: nextcloud/all-in-one:latest
    init: true
    restart: always
    container_name: nextcloud-aio-mastercontainer
    volumes:
      - nextcloud_aio_mastercontainer:/mnt/docker-aio-config
      - /var/run/docker.sock:/var/run/docker.sock:ro
    ports:
      - 8080:8080
    environment:
      - APACHE_PORT=11000
      - APACHE_IP_BINDING=127.0.0.1
      - NEXTCLOUD_DATADIR=/home/pi/docker/nextcloud/nextcloud-data
      - SKIP_DOMAIN_VALIDATION=true

  caddy:
    image: caddy:alpine
    container_name: caddy
    restart: always
    ports:
      - 80:80
      - 443:443
    volumes:
      - /home/pi/docker/nextcloud/caddy-files/caddy:/usr/bin/caddy
      - /home/pi/docker/nextcloud/caddy-certs:/certs
      - /home/pi/docker/nextcloud/caddy-config:/config
      - /home/pi/docker/nextcloud/caddy-data:/data
      - /home/pi/docker/nextcloud/caddy-certs:/srv
      - /home/pi/docker/nextcloud/caddy-files/Caddyfile:/etc/caddy/Caddyfile
    environment:
      DOMAIN: "xxx.duckdns.org"
      EMAIL: "xxx@googlemail.com"
      DUCKDNS_TOKEN: "xx-xx-xx-xx-xx"
      LOG_FILE: "/data/access.log"

volumes:
  nextcloud_aio_mastercontainer:
    name: nextcloud_aio_mastercontainer

Caddyfile:

xxx.duckdns.org:443 {
	tls {
		dns duckdns xx-xx-xx-xx-xx
	}
  reverse_proxy localhost:11000
}

The caddy file was downloaded from the caddy homepage and should work (executing is possible).

Shouldn’t be a problem, that I created another certificate at a duckdns-subdomain with my email-address?

Thanks for your support :slightly_frowning_face:

Best regards,
Dominik

2

Hi, please check and adjust this:

3

Thanks for your fast help :slight_smile:
After adding “network_mode: host” to my caddy part it is directly working.
Seems that also a certifcate was generated before

Thanks, thanks, thanks

1 Like
4

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.