Summary of the issue I am facing:
After more than a month of trying (on and off), I still get stuck trying to install Nextcloud on my Synology NAS. It seems different Nextcloud containers cannot see each other, but I do not understand what I am doing wrong.
The following containers have a yellow indicator in Container Manager and they report errors in their logs:
- nextcloud-aio-whiteboard: “Waiting for redis to start…”
- nextcloud-aio-apache: “Waiting for Nextcloud to start…”
- nextcloud-aio-notify-push: “Waiting for Nextcloud to start…”
- nextcloud-aio-nextcloud: “Waiting for database to start…”
So whiteboard is waiting for redis. And apache and notify-push are waiting for nextcloud, which in turn is waiting for the database. Redis seems to run normally. The database (PostgreSQL) log, even though it reports as normal and healthy in Container Manager, still has two lines of note:
- LOG: listening on Unix socket “/var/run/postgresql/.s.PGSQL.5432”
- LOG: listening on IPv4 address"0.0.0.0", port 5432
Also, I notice that the log of nextcloud-aio-clamav reports an error: “Database update process failed: HTTP GET failed”. Maybe that is irrelevant but I just want to throw it out there.
Does someone know how I can get past this issue to finally get Nextcloud installed?
Here is extra information:
The Basics
-
Nextcloud Server version:
- 10.10.0 (Is Hub version the same as Server version?)
-
Operating system and version:
- Synology DSM 7.2.2-72806 Update 3
-
Web server and version:
- none
-
Reverse proxy and version:
- nginx (embedded in DSM)
-
PHP version:
- 7.4.33-0130
-
Is this the first time you’ve seen this error? (Yes / No):
- no
-
When did this problem seem to first start?
- as soon as I started trying to install it (over a month ago)
-
Installation method:
- AIO docker, running the following command:
docker run -d
–init
–sig-proxy=false
–name nextcloud-aio-mastercontainer
–restart unless-stopped
–env PUID=1034
–env PGID=100
–env TZ=Europe/Amsterdam
–env NEXTCLOUD_DATADIR=“/volume1/cloud”
–env WATCHTOWER_DOCKER_SOCKET_PATH=“/var/run/docker.sock”
–env APACHE_PORT=8443
–env APACHE_IP_BINDING=192.168.1.101
–publish 8080:8080
–volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config
–volume /var/run/docker.sock:/var/run/docker.sock:ro
nextcloud/all-in-one:latest
- AIO docker, running the following command:
-
Are you using CloudfIare, mod_security, or similar?
- no
-
NAS Model: Synology DS224+, with memory expansion of 16GB (total 18GB) and 20TB harddrive (all functioning properly as far as I know)
-
Router: ASUS RT-AX1800U, running OpenWrt version 24.10.0
Steps to replicate it:
- In Synology firewall, open ports as specified here.
- In OpenWrt router (Dnsmasq), add DNS records as specified here, EXCEPT the ones with “ns.your.domain” (so I skipped the first and the last one) because that interferes with my reverse proxy setup that I use for other services). (Perhaps that is the problem? But I don’t think so and wouldn’t know how to fix this.)
- Run the following command as root (same one as already mentioned above):
docker run -d
–init
–sig-proxy=false
–name nextcloud-aio-mastercontainer
–restart unless-stopped
–env PUID=1034
–env PGID=100
–env TZ=Europe/Amsterdam
–env NEXTCLOUD_DATADIR=“/volume1/cloud”
–env WATCHTOWER_DOCKER_SOCKET_PATH=“/var/run/docker.sock”
–env APACHE_PORT=8443
–env APACHE_IP_BINDING=192.168.1.101
–publish 8080:8080
–volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config
–volume /var/run/docker.sock:/var/run/docker.sock:ro
nextcloud/all-in-one:latest - After container nextcloud-aio-mastercontainer has started, go to NAS IP-address port 8080 (in my case 192.168.1.101:8080), receive passphrase and enter it.
- On the next page, tick box to install Nextcloud Hub version10.10.0 (instead of Nextcloud Hub 9) and select the following four additional containers: ClamAV, Collabora, Imaginary, Whiteboard
Log entries
Nextcloud
N/A (cannot find any log in my data directory)
I hope this gives all of you enough information and I hope someone has the magic tip for me to get past this. Thank you so much!!