Nexcloud AIO on Unraid will not start three of the dockers

ℹ️ Support 📦 Appliances (Docker, Snappy, VM, NCP, AIO)
, , ,
1

image
image589×670 28.8 KB

I followed Spaceinvader1s youtube guide and got everything running fine.
After a couple of weeks it would not start up again.

Any tips on what to do?

Nexcloud won’t start.
The two others that wont start says they are waiting for nextcloud.
I have successfulle made backups… but they won’t show up in the list… although they did that earlier.

This is the log from when I presse “nextcloud”

2025-03-13T13:41:26.151088508Z now
2025-03-13T13:41:26.151130565Z -------------------------------
2025-03-13T13:41:26.151144468Z 2025-03-13 13:41:26.149974+00
2025-03-13T13:41:26.151158121Z (1 row)
2025-03-13T13:41:26.151171122Z
2025-03-13T13:41:26.170325576Z + ‘[’ -f /dev-dri-group-was-added ‘]’
2025-03-13T13:41:26.170628879Z ++ find /dev -maxdepth 1 -mindepth 1 -name dri
2025-03-13T13:41:26.171453786Z + ‘[’ -n ‘’ ‘]’
2025-03-13T13:41:26.171491902Z + set +x
2025-03-13T13:41:27.248602753Z Connection to nextcloud-aio-redis (172.20.0.6) 6379 port [tcp/redis] succeeded!
2025-03-13T13:41:27.258464977Z The www-data user doesn’t seem to have access rights in the datadir.
2025-03-13T13:41:27.258505754Z Most likely are the files located on a drive that does not follow linux permissions.
2025-03-13T13:41:27.258521928Z Please adjust the permissions like mentioned below.
2025-03-13T13:41:27.258535691Z The found permissions are:
2025-03-13T13:41:27.258549297Z 33:0 750
2025-03-13T13:41:27.258562369Z (userID:groupID permissions)
2025-03-13T13:41:27.258575248Z but they should be:
2025-03-13T13:41:27.258588172Z 33:0 750
2025-03-13T13:41:27.258601108Z (userID:groupID permissions)

13T13:41:27.258640608Z Also make sure that the parent directories on the host of the directory that you’ve chosen as datadir are publicly readable with e.g. ‘sudo chmod +r /mnt’ (adjust the command accordingly to your case) and the same for all subdirectories.
2025-03-13T13:41:27.258659524Z Additionally, if you want to use a Fuse-mount as datadir, set ‘allow_other’ as additional mount option.
2025-03-13T13:41:27.258690289Z For SMB/CIFS mounts as datadir, see GitHub - nextcloud/all-in-one: 📦 The official Nextcloud installation method. Provides easy deployment and maintenance with most features included in this one Nextcloud instance.
2025-03-13T13:41:35.858761659Z Connection to nextcloud-aio-database (172.20.0.5) 5432 port [tcp/postgresql] succeeded!

2

If you like solutions that feel like cheating: sudo ln -s /mnt/remote/storage/nas /var/local/magic/nextcloud/mount

3

I dont even know what this means

4

If Nextcloud is failing to access its data directory, chances are you’re running into Unraid’s permission model with mounted SMB or FUSE shares. A quick workaround? Symlink the storage to where Nextcloud expects it:

sudo ln -s /mnt/remote/storage/nas /var/local/magic/nextcloud/mount

Use /var/local/magic/nextcloud/mount. This makes Nextcloud “believe” the files are local, sidestepping common permission conflicts with networked storage.

But! Symlinks inside Docker can be unpredictable, depending on how the container runtime interprets them. In more structured environments—think Kubernetes with persistent volumes or large-scale CI/CD pipelines—you’ll often see issues where symlinks break inside chrooted environments, immutable deployments, or when overlay filesystems (e.g., AUFS, OverlayFS) are involved.

A more stable fix? A proper bind mount and permission correction:

sudo chown -R 33:33 /mnt/remote/storage/nas
sudo chmod -R 750 /mnt/remote/storage/nas

If you’re working with SMB, ensure it’s mounted with allow_other, as some network shares enforce restrictive access by default. This approach is more in line with best practices for setups where storage consistency and permission handling are critical.