Problem with updating Nextcloud on TrueNAS

NervousGynocologist@lemmy.world to Selfhosted@lemmy.world – 22 points –

Hello friends,

I've been running a personal Nextcloud instance on my TrueNAS server for about a year now. I sadly haven't been able to update it though.

For some reason my data directory is called data2....

Now when I try to update through the web updater onthee step "Check for expected files" it gives me the error of: "The following extra files have been found:

  • data2 "

I have looked through the web for a solution and haven't found anything that works. I've tried renaming the directory data2 -> data and changing the default directory of nextcloud from data2 -> data... But this for some reason did not work.

If someone could please help/give me a link to a guide or something. I'm not a very advanced user but I'll give it my best shot. Let me know if you need more info please.

Thanks in advance.

6

If you are using the Truecharts app of Nextcloud you can open a support ticket on the Truecharts Discord server, they might be able to help or maybe someone already had the same problem and you can find a solution there.

Thank you for the reply. Wasn't aware of Truecharts... But I think they only support TrueNAS scale from what I see, I'm using Core. Not sure if that makes a difference but I'll check out their discord.

Oh yeah that makes a difference for sure. They do only support SCALE.

Gah, this is the reason I havent set up nextcloud. Cant tweak the all in one docker thing to my needs, and a manual install cant easily be updated. Too much hassle when I just want to use nextcloud memories

manual install cant easily be updated

It definitely can, been doing it for years. Just bump the version number in nextcloud_version, deploy, done.

It took a little bit of work but I rolled my own docker compose and it's been pretty solid. I pin the specific nextcloud version in my compose file (I don't like using :latest for things) and updating is as simple as incrementing the version, pulling the new image, and restarting the container. I've been running this way for a couple years now and I couldn't be happier with it.