Nextcloud does not start and cannot reinstall after Electric Eel update

Apps and Virtualization
41

We have tested and successfully deployed the Nextcloud app in Electric Eel using these new instructions. Please give this a test drive to see if it resolves your deployment issues. If not, let us know what appears to be happening and blocking your deployments:

Note, this does not address the Nextcloud/Collabora deployments. We are working on updating all the app tutorials for apps found in the stable repo.

3 Likes
42

Iā€™m at my witā€™s end. Iā€™ve tried everything I can think of but cannot get this to reinstall. It installed fine following the provided directions. I tried importing an old database from my last install but it turned out they were different Postgres versions so I couldnā€™t do it. Wiped the install to try again and have been unsuccessful in getting it to redeploy.

Iā€™ve tried:

  • Deleting App
  • Deleting data sets
  • Deleting container images (manually removing redis/postgres as well)
  • Running docker builder prune
  • Redoing permissions
  • Using a different app name

In every case it returns the same error others are showing:

[2024/11/09 16:50:35] (ERROR) app_lifecycle.compose_action():56 - Failed 'up' action for 'cloudsvr' app:  postgres Pulling
 redis Pulling
 cron Pulling
 nextcloud Pulling
 cron Warning pull access denied for ix-nextcloud, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
 nextcloud Warning pull access denied for ix-nextcloud, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
 a480a496ba95 Already exists
...
< more pulls/downloads>
...
 postgres Pulled
 Network ix-cloudsvr_default  Creating
 Network ix-cloudsvr_default  Created
 Volume "ix-cloudsvr_redis-data"  Creating
 Volume "ix-cloudsvr_redis-data"  Created
 Container ix-cloudsvr-permissions-1  Creating
time="2024-11-09T16:48:34-06:00" level=warning msg="config `uid`, `gid` and `mode` are not supported, they will be ignored"
time="2024-11-09T16:48:34-06:00" level=warning msg="config `uid`, `gid` and `mode` are not supported, they will be ignored"
 Container ix-cloudsvr-permissions-1  Created
 Container ix-cloudsvr-postgres-1  Creating
 Container ix-cloudsvr-redis-1  Creating
 Container ix-cloudsvr-redis-1  Created
 Container ix-cloudsvr-postgres-1  Created
 Container ix-cloudsvr-nextcloud-1  Creating
time="2024-11-09T16:48:34-06:00" level=warning msg="config `uid`, `gid` and `mode` are not supported, they will be ignored"
time="2024-11-09T16:48:34-06:00" level=warning msg="config `uid`, `gid` and `mode` are not supported, they will be ignored"
 Container ix-cloudsvr-nextcloud-1  Created
 Container ix-cloudsvr-cron-1  Creating
time="2024-11-09T16:48:34-06:00" level=warning msg="config `uid`, `gid` and `mode` are not supported, they will be ignored"
 Container ix-cloudsvr-cron-1  Created
 Container ix-cloudsvr-permissions-1  Starting
 Container ix-cloudsvr-permissions-1  Started
 Container ix-cloudsvr-permissions-1  Waiting
 Container ix-cloudsvr-permissions-1  Waiting
 Container ix-cloudsvr-permissions-1  Exited
 Container ix-cloudsvr-redis-1  Starting
 Container ix-cloudsvr-permissions-1  Exited
 Container ix-cloudsvr-postgres-1  Starting
 Container ix-cloudsvr-redis-1  Started
 Container ix-cloudsvr-postgres-1  Started
 Container ix-cloudsvr-permissions-1  Waiting
 Container ix-cloudsvr-postgres-1  Waiting
 Container ix-cloudsvr-redis-1  Waiting
 Container ix-cloudsvr-permissions-1  Exited
 Container ix-cloudsvr-postgres-1  Healthy
 Container ix-cloudsvr-redis-1  Healthy
 Container ix-cloudsvr-nextcloud-1  Starting
 Container ix-cloudsvr-nextcloud-1  Started
 Container ix-cloudsvr-nextcloud-1  Waiting
 Container ix-cloudsvr-nextcloud-1  Error
dependency failed to start: container ix-cloudsvr-nextcloud-1 is unhealthy
43

Thanks a lot for the updated manual. Following all these instructions from scratch allows me to get a running* Nextcloud instance.

But there seem to be a problem with the Redis credentials. I used own password for Nextcloud, Postgres and Redis during the setup. Finally the counter is deployed and the login page appears in the browser. Unfortunately, Iā€™m stuck there, login never succeeds.

I was able to nail it down to wrong Redis credentials. I have to set them to ā€œnextcloudā€ during setup. Whatever I choose, itā€™s filled properly into NC config.php but it only works when set to default password. I suspect there is another location that always refers to that default password.

May you double check the app if there is somewhere a hardcoded password defined? Or could anybody guide me to the location where I can change the Redis password?

44

I deleted the Nextcloud app after trying all the upgrade suggestions. I used Host Path for my storage which was not deleted.
My question is, if I follow the official steps now to reinstall the Nextcloud app, how can I copy/import my existing data to the new instance? The data is sitting in a folder in a dataset and all my pictures and files are there. I really want to save this. Or maybe another question is, how can I pull the files out and copy them to an SMB share?

45

You donā€™t copy it, you point the hostpaths to the same locations you were using before.

46

Thanks for replying. I followed the new official for installing Nextcloud, but getting this error in the log: ā€œdependency failed to start: container ix-nextcloud-postgres-1 is unhealthyā€.
Iā€™m using Host Path for Postgres Data Storage and pointing it to the same dataset as my previous installation. Is that correct?

47

@requird Follow the instructions here for setting up your postgres dataset and configuring permissions: Nextcloud | TrueNAS Documentation Hub

Note that the dataset must use Posix permissions.

1 Like
48

I think youā€™re running into the same problem most of the rest of us are. The instructions work fine for an initial install, but if you ever uninstall there seems to be something left behind that blocks the app from working. Itā€™s not permissions, itā€™s not a container image, but something deep in the system keeps it from working.

49

Thanks to @DjP-iX I got a bit further, but Iā€™m not there yet. Now Iā€™m getting ā€œdependency failed to start: container ix-nextcloud-nextcloud-1 is unhealthyā€.

I really had to go step by step on those dataset permissions. Iā€™m a little confused about one step where it says to add user 33 with Full Permissions. Who/what is user 33? I tried with user 33 and also my admin user UID. Both did not work.

Any other suggestions are appreciated!

50

UID 33 should be www-data. You may double-check at Credentials ā†’ Users.
Nextcloud is executed by that user, so you make sure that it can fully access that dataset.

51

That step is talking about adding an ACL entry in the Nextcloud storage configuration when you add the host path. Click Host Path > Enable ACL > enter the host path > Click ADD for an ACL Entry and enter UID 33 > add the Force flag if the dataset contains existing data. It should look like this:

image
image450Ɨ927 12.1 KB

52

FWIW, mine didnā€™t start either but I didnā€™t have time to look into it. Today I updated to the latest (30.0.2) and it started. Apologies for not having any useful information other than that. The app itself is saying I need to update something using the command line updater. Again, no time to deal with it at the moment.

1 Like
53

Thanks that new guide solved the issue for me!

54

After tinkering with my nc app settings (adding a redis/etc passwords), deleting then reinstalling the app, and reconnecting to my existing datasets I was able to get my instance running again. However, Iā€™m faced with a ā€œPlease use the command line updater because updating via browser is disabled in your config.php.ā€ error whenever I try to access the web ui. :rofl: This wouldnā€™t be an issue for most people here, but Iā€™m no command line warrior (quiet the opposite in fact.) and Iā€™m certain anyone would love to trade problems with me and get back up and running. Iā€™ve tried using the tns shell and the main command line interface, but I honestly have no idea what Iā€™m doing. I initially set mine up repeating what Iā€™ve seen others doing on YouTube.

55

Had the same problem of Nextcloud not deploying after updating to Electric Eel and on top of that all my Nextcloud data was in the ixVolume datasets.
Waiting for the update didā€™t help. Additionally, I had 8TB nextcloud snapshot that I could not delete, because it had cloned dependencies.

To solve this:

  1. Followed this guide closely to set up a second instance of the Nextcloud without deleting the old one.
  • Created the 3 datasets under a parent dataset with required permissions exactly as described.
  • For the app install settings copied all the settings from the guide, except:
    *Copied all the passwords and usernames from the old install settings
    *I did not use the ip:port for the as suggested in the guide for the Host field, instead I put just the ip there without a port, otherwise I was getting ā€œuntrustedā€ error in Nextcloud
  1. Next I moved all my data from ixVolume to a new host path data of the sec ond Nextcloud instance using the Midnight Commander:

  • Opened TruNas shell: Advanced settings ā†’ Shell and typed-> mc

  • My old data was stored in 2 places as duplicates due to undeletable snapshot:
    */mnt//ix-applications/releases/nextcloud/volumes/ix_volumes/ix-nextcloud_data/data/admin/files

    */ix-apps/app_mounts/nextcloud/ix-nextcloud_data

  • So moved the data using File-> Move in the midnight commander into the new Nextcloud data folder, for me it was here:
    */mnt//nextcloud/data/admin/files

**Because moving took a while had to extend the web session, otherwise it would stop the move after the default 300 seconds.

Extend Sessions:

Advanced Settings ā†’ Access ā†’ Configure ā†’ Set to 15000 seconds

  1. Then you have to open Nextcloud shell to index new files, otherwise they wonā€™t appear in the WebUI

*Apps-> Nextcloud> small shell icon next to Nextcloud ā†’ run
*In the Nextcloud shell type:
*runuser
*runuser -u www-data ā€“ php occ files:scan --all

After it finishes the scan, the files should appear in the new Nextcloud instance.

  1. Finally, had to delete that huge cloned snapshot.

Stuck snapshots was giving error when trying to delete:

( [EINVAL] options.defer or snapshot got a dependant clone):

Opened the Truenas shell: Advanced settings ā†’ Shell and typed
zfs list -t snapshot -o name,clones -r (To show shere the cloned snapshots are)

Then used this commands to destroy the stuck snapshots. !!!Be careful as using this deleted all the data stored in the original Nexcloud instance along with the data that was in the stuck snapshot - so make sure all the data from step 2 is backed up!!!

  • zfs promote StorageMirror/ix-apps/app_mounts/nextcloud/ix-nextcloud_data

  • zfs destroy -R StorageMirror/ix-apps/app_mounts/nextcloud/ix-nextcloud_data