Nexcloud AIO on Unraid will not start three of the dockers

StephenMF · March 13, 2025, 4:25pm

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 https://github.com/nextcloud/all-in-one#can-i-use-a-cifssmb-share-as-nextclouds-datadir
2025-03-13T13:41:35.858761659Z Connection to nextcloud-aio-database (172.20.0.5) 5432 port [tcp/postgresql] succeeded!

stnslwk · March 14, 2025, 5:44am

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

StephenMF · March 15, 2025, 11:07am

I dont even know what this means

stnslwk · March 15, 2025, 11:32am

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.

StephenMF · March 15, 2025, 12:56pm

I am not working with SMBs
I am pointing Nextcloud AIO to it’s own share called Nextcloud-AIO
I don’t have any folders called NAS or MAGIC.

or anything in “/mnt/remote/storage/nas /var/local/magic/nextcloud/mount”

So i’m not really how those commands should work?

It worked in the beginning and created all this.

StephenMF · March 15, 2025, 4:27pm

Got this error.
ln: failed to create symbolic link ‘/var/local/magic/nextcloud/mount’: No such file or directory
root@EskiUnraid:~#

wwe · March 16, 2025, 11:13am

the problem is located around data directory access.

StephenMF:

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)

even it doesn’t seem to make sense from the log output… you should review the docker bind/volume mount instructions and share your compose/docker run together with the datadir permissions list (ls -al).

the owner sshd from your screenshot seems strange… usually 33 is webserver user…

StephenMF · March 16, 2025, 12:30pm

Thanks all… for looking and answering.

Owner and permissions are listed above in the screenshot of the Docker/nextcloud data folder.

( /mnt/user/Nextcloud-AIO )

szaimen · March 16, 2025, 12:32pm

Hi, can you post the output of sudo ls -la /mnt/user here?

StephenMF · March 16, 2025, 12:34pm

yes.

drwxrwxrwx  1 nobody users  220 Mar 16 13:35 .
drwxr-xr-x 11 root   root   220 Mar 15 17:58 ..
drwxrwxrwx  1 nobody users   18 Apr 26  2024 .Trash-99
drwxrwxrwx  1 nobody users   74 Apr 26  2024 AppsBackups
drwxrwxrwx  1 nobody users    0 Nov  9  2023 Define-7
drwxrwxrwx  1 nobody users   22 Oct 11  2021 GIT
drwxrwxrwx  1 nobody users  192 Mar  1 02:19 Nextcloud-AIO
drwxrwxrwx  1 nobody users    8 Jan 27 22:42 Nextcloud-AIO-Backup
drwxrwxrwx  1 nobody users    0 Feb 11 21:17 Photos
drwxrwxrwx  1 nobody users   82 May 13  2024 Render
drwxrwxrwx  1 nobody users    0 Mar 13 11:24 Resillio
drwxrwxrwx  1 nobody users    0 Jun 29  2022 Share
drwxrwxrwx  1 nobody users  210 Feb 11 11:09 StashU
drwxrwxrwx  1 nobody users  538 Mar 16 11:12 appdata
drwxrwxrwx  1 nobody users    0 Jun  9  2021 clients
drwxrwxrwx  1 nobody users    0 Dec  4 10:16 domains
drwxrwxrwx  1 nobody users   92 Feb 11 14:50 immich-app
drwxrwxrwx  1 nobody users   12 Jan 21 13:07 immich-store
drwxrwxrwx  1 nobody users    0 Jun 20  2023 isos
drwxrwxrwx  1 nobody users   92 Nov  7 02:21 photos-immich
drwxrwxrwx  1 nobody users 5750 Mar  4 12:07 rec
drwxrwxrwx  1 nobody users   26 Sep 14  2023 system
drwxrwxrwx  1 nobody users    0 Jun 11  2021 urbackup_tmp_files

StephenMF · March 16, 2025, 12:40pm

new user, one folder deeper.

user sshd I guess is made by Nexcloud AIO master docker?

root@EskiUnraid:~# sudo ls -la /mnt/user/Nextcloud-AIO
total 24
drwxr-x--- 1 sshd   root  192 Mar  1 02:19 .
drwxrwxrwx 1 nobody users 220 Mar 16 13:35 ..
-rwxr-x--- 1 sshd   root  542 Feb 27 11:22 .htaccess
-rwxr-x--- 1 sshd   root   52 Feb 27 11:22 .ncdata
drwxr-x--- 1 sshd   root   20 Jan 20 23:18 StephenMF
drwxr-x--- 1 sshd   root   20 Jan 20 22:22 admin
drwxr-x--- 1 sshd   root  132 Jan 26 22:46 appdata_ocu3oftkc2wj
-rwxr-x--- 1 sshd   root    0 Jan 14 16:18 audit.log
-rwxr-x--- 1 sshd   root    0 Jan 14 16:41 fts-index.done
-rwxr-x--- 1 sshd   root    0 Feb 27 11:22 index.html
-rwxr-x--- 1 sshd   root    0 Jan 14 16:14 nextcloud.log

szaimen · March 16, 2025, 12:42pm

Just to link the code in question, this error comes up if the web server user running inside the container (uid 33) cannot write into the configured data dir: all-in-one/Containers/nextcloud/entrypoint.sh at 77dd56bade11cbb6ecffe8f2ada381520a16f5d6 · nextcloud/all-in-one · GitHub

And yes, I think uid 33 is the sshd user on unraid…

szaimen · March 16, 2025, 12:44pm

Can you run sudo docker inspect nextcloud-aio-nextcloud | grep /mnt/user/Nextcloud-AIO and post the output here?

StephenMF · March 16, 2025, 12:45pm

Full disclosure.
I am not a coder - I use computers by pressing buttons

So this is very unfamiliar to me.

All my other dockers work by just pressing buttons.

And I really appreciate your effort.

root@EskiUnraid:~# sudo docker inspect nextcloud-aio-nextcloud | grep /mnt/user/Nextcloud-AIO
“/mnt/user/Nextcloud-AIO:/mnt/ncdata:rw”
“Source”: “/mnt/user/Nextcloud-AIO”,

szaimen · March 16, 2025, 12:49pm

Hm… Can you run sudo docker restart nextcloud-aio-nextcloud and check if that makes any difference?

StephenMF · March 16, 2025, 1:30pm

Same.

StephenMF · March 16, 2025, 7:41pm

So I found this on the Unraid forum.

https://forums.unraid.net/topic/187473-spaceinvaders-nextcloud-aio-docker/#findComment-1530445

Sounds exactly like what I am going through.

My serious warning: stay away from Nextcloud AIO, it is a killer (and gets killed every few days) on UNRAID.

First of all, uninstalling the dockers wont work, look at the docker’s git page there is a “removal instruction” that needs to be followed stricktly.

Then, follow the installation advices literally too, it can work, although you will not like the outcome.

Even if it is running, it wont run for long because UNRAID’s file permissions and Nextcloud’s file permissions are different and cannot be set to a common and working value. So either UNRAID cannot read the data or Nextcloud refuses to start at all because permissions have been tampered with (for instance if you click on “set docker friendly permissions” in the GUI). You will not notice it directly but someday you will like to do a backup (Nextcloud comes with its own backup but this is only consuming time and space if the data is within an UNRAID array) or you want to offer them to the LAN with SMB or NFS. Nothing will work!!!

So to prevent really painful experiences with potential data loss: STAY WAY!

(but read and follow the deinstallation instructions, else there will always be reminders left on your system that prevent future new installations. Maybe someday AIO and UNRAID can play better together)

system · June 11, 2025, 4:25pm

This topic was automatically closed after 90 days. New replies are no longer allowed.