HI Folks hopefully someone can help me iron out the bugs with this?
 After updating my Unraid server to 7.0 and solving the Wrong Pool State Issue when trying to to start the array I found that all my Dockers & VM's had got wiped. So I started to reinstall all the dockers I had and thought rather than going through the process of having to Install MariaDB and then Docker etc.. I would use the new Nextcloud AIO and using the one set up by Spaceinvader (love his instructional videos they are really concise and well thought out) It all installed nicely even able to access it from outside my home network using a cloudflared tunnel.

However I have run into a couple of bugs that I cannot get around the first one is that when I have tried to update by clicking on the apply update or by
stopping the containers and trying to update them individually I get this message see attached. There are a couple of other niggles however this is the main one I am running this on a Dell Power Edge Server

Hopefully you wonderful people can help           

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)

 

Just a Quick Update the latest Unraid Update Fixed it somehow. and it is still up and running ok

On 2/27/2025 at 6:33 AM, MAM59 said:

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)

 

You have tips on what to guides to follow then?

 

19 minutes ago, StephenMF said:

You have tips on what to guides to follow then?

sadly no. at least not on UNRAID.

 

What about the Nextcloud AIO VM?
Same issues?

12 minutes ago, StephenMF said:

What about the Nextcloud AIO VM?
Same issues?

Depends on where the data directory is located. If on an UNRAID share/array then YES 😞

You see, NXC's and UNRAID's file permissions don't go together. There is a big risk that they may be damaged by some common tool and then you get problems on either side. An UNRAID backup tool cannot read NXC data (that's why AIO comes with its own backup, but for me it makes no real sense to keep data doubled on the same machine). Or you run UNRAID's "Fix Docker Safe Permissions" tool that will allow access for UNRAID but prevent AIO even from starting anymore.

As long as you do not tamper with any of them, AIO works ok...

But for me its a too high risk to be cut off from data or cloud if accidentally (maybe one day an app like "fix common problems" will reset permissions without asking?) some tool can kill it with the click of a button or via cron.

You have to decide yourself if you are willing to take such a risk.

 

This is second time I tried installing Nextcloud - First one stopped working... not sure how.

So I tried "fool proof" AIO and after some weeks that stopped working.

Maybe because of something I did - Maybe not.

It was just running. did not really put anything on it, did a couple of updates, did a couple of backups... and suddenly i get access errors, like described here.

https://help.nextcloud.com/t/nexcloud-aio-on-unraid-will-not-start-three-of-the-dockers/219954

 

 

You can get AIO to run without issues if you consider it as an "island" and never modify its data externally but you're making it hard on yourself, it's a heavy lump of stuff with a lot that's usually unnecessary for a home install and not well tailored to unraid unless you understand everything.

 

Simple official nextcloud container and a mariadb instance is easier.

Some guidance here:

 

 

Edited March 17, 20251 yr by Kilrah

1 hour ago, Kilrah said:

You can get AIO to run without issues if you consider it as an "island" and never modify its data externally but you're making it hard on yourself, it's a heavy lump of stuff with a lot that's usually unnecessary for a home install and not well tailored to unraid unless you understand everything.

 

Simple official nextcloud container and a mariadb instance is easier.

Some guidance here:

 

 

OK.
Thanks.
I will kill my current AIO and try this... when I have some time.

 

what i dont get about this is: 

 

A: why change nextcloud data outside of nextcloud  and even if you do, why is nextcloud AIO diferent from other nextcloud docker images? 
do they mount data diferently and if so do they than also allow data to be shared amoung diferent apps? 

 

would i be able still setup or use the nexcloud talk backend server somehow?  

 

one of the main reasons why im even considering this is because i kinda like to have the  igpu of my  pentium 5000 working for  the memories app etc. 

 

@Kilrah have you any take on this?

A while back I jumped at the opportunity to switch from LSIO Nextcloud + mariadb images to Spaceinvader's AIO image and I haven't had any issues with it. Seems to have better performance than the former. Also, makes it effortless to add Collabora and increase functionality of Nextcloud Talk without faffing around with STUN/TURN server settings, which require a lot more setup with the LSIO image. I just followed the video guide.

You definitely want to keep Nextcloud storage on it's own share and generally refrain from modifying those files from outside of Nextcloud. But if you want to access other stuff on your array through the Nextcloud interface then you can add the "NEXTCLOUD_MOUNT" variable to the AIO container and point it to whatever directory on the host you want to mount with the "External Storage" plugin inside of Nextcloud.

You want to update the containers via the AIO interface rather than from the unRAID docker management page. From within Nextcloud, go to Administration Settings > Overview and click on "Open Nextcloud AIO Interface". I believe if there are updates available then you'll be prompted to do it from there. I have enabled auto-backups and auto-updates within the AIO interface per the SpaceInvader setup video. Slightly annoying that the unRAID interface constantly prompts to update the containters, but I've just ignored those warnings within Fix Common Problems.

This is the way to go, IMO.

Hello guys,

I used standard Nextcloud with a Swag combination for years and after the last issue with it I decided to switsch to AIO using Spaceinvaderone's tutorial.

Installation with default settings went smoothly, but I cannot start initial setup right after the installation. The docker stops itself after a couple of minutes and the log shows that the DNS resolving does not work.

 

I checked other containers, they all can resolve DNS. AIO does not.

I tried to find any hint in forums, also by links in the log, but no luck. Reinstalled with no change in behaviour.

 

The resolution was to delete Extra parameters. May be it would help anybody, because I was completely stack. Note: I have a pfsense router.