Jump to content

Nextcloud- Dragonfish-Electric Eel Issues

Go to solution Solved by EduardoM,

Honestly don't know what the heck I did. But I went into the app install settings, cleared the host path for the issue, then pointed to the exact same host path. Then a similar issue happened for the appdata host path, did the same thing, and viola, all is good .-.

To be clear, I tried this with "DEPRECATED: Old Storage Structure (See the tooltip for more information)" on and off. I've been working on this all day...I tried turning it back on, no game, I turned it back off, it's miraculously working. Sorry to other users who have the same issue and I did not provide a conclusive answer!

Important thing though!!! Set your ACL correctly. appdata and userdata MUST have www-data for both user and group. pgdata (for Postgress) MUST be "netdata" for user, and "docker" for group. You will need to give your parent dataset the same user permissions under the ACL list in order to get it on the child dataset

appdata-userdata ACL.png

pgdata ACL.png

Hey everyone! I'm having issues with my TrueNAS server after updating from Dragonfish to Electric Eel. All the other native apps that I have work, except Nextcloud :(. I've been trying everything that I can think of, and I can't seem to get it to work. At first it was issues with ACL, so I fixed those. Once I fixed them, I was still getting issues with deployment, so I took a further look into other forums, and I thought that maybe I needed to add some folders into the dataset via SMB and it should work. I currently have my path leading to Nextcloud_Database, and from there into 3 separate datasets that are called, "appdata", "userdata", and "pgdata". For each of the datasets that the host file is pointing to, in the SMB session, I added "html" for appdata, and "data" for userdata. I moved the data that was already in each folder to the new folder created, deployed, and everything seemed to be working good, until I went in the Web UI and it was asking me to create a new account, and then to install postgress, which I tried doing, and nothing happened, it just took me back to the admin login page. The files within appdata were replaced with new empty files, so I had to revert back to a snapshot an hour before I made the changes. Now I am back to my original issue with getting Nextcloud to deploy...

This is the /var/log/app_lifecycle.log output that I get.
[2025/01/26 18:58:56] (ERROR) app_lifecycle.compose_action():56 - Failed 'up' action for 'nextcloud' app:  Network ix-nextcloud_default  Creating
 Network ix-nextcloud_default  Created
 Container ix-nextcloud-postgres_upgrade-1  Creating
 Container ix-nextcloud-permissions-1  Creating
time="2025-01-26T18:58:55-06:00" level=warning msg="config `uid`, `gid` and `mode` are not supported, they will be ignored"
time="2025-01-26T18:58:55-06:00" level=warning msg="config `uid`, `gid` and `mode` are not supported, they will be ignored"
time="2025-01-26T18:58:55-06:00" level=warning msg="config `uid`, `gid` and `mode` are not supported, they will be ignored"
 Container ix-nextcloud-postgres_upgrade-1  Created
 Container ix-nextcloud-permissions-1  Created
 Container ix-nextcloud-postgres-1  Creating
 Container ix-nextcloud-redis-1  Creating
 Container ix-nextcloud-redis-1  Created
 Container ix-nextcloud-postgres-1  Created
 Container ix-nextcloud-nextcloud-1  Creating
time="2025-01-26T18:58:56-06:00" level=warning msg="config `uid`, `gid` and `mode` are not supported, they will be ignored"
time="2025-01-26T18:58:56-06:00" level=warning msg="config `uid`, `gid` and `mode` are not supported, they will be ignored"
time="2025-01-26T18:58:56-06:00" level=warning msg="config `uid`, `gid` and `mode` are not supported, they will be ignored"
Error response from daemon: invalid mount config for type "bind": bind source path does not exist: /mnt/NAS Storage/Apps/Nextcloud_Database/userdata/data

 

I understand that the error is saying that /mnt/NAS Storage/Apps/Nextcloud_Database/userdata/data doesn't exist, however, on the app itself, I don't have the host file pointing to that, I have it set to /mnt/NAS Storage/Apps/Nextcloud_Database/userdata

Link to comment
https://linustechtips.com/topic/1598280-nextcloud-dragonfish-electric-eel-issues/
Share on other sites

Link to post
Share on other sites

Honestly don't know what the heck I did. But I went into the app install settings, cleared the host path for the issue, then pointed to the exact same host path. Then a similar issue happened for the appdata host path, did the same thing, and viola, all is good .-.

To be clear, I tried this with "DEPRECATED: Old Storage Structure (See the tooltip for more information)" on and off. I've been working on this all day...I tried turning it back on, no game, I turned it back off, it's miraculously working. Sorry to other users who have the same issue and I did not provide a conclusive answer!

Important thing though!!! Set your ACL correctly. appdata and userdata MUST have www-data for both user and group. pgdata (for Postgress) MUST be "netdata" for user, and "docker" for group. You will need to give your parent dataset the same user permissions under the ACL list in order to get it on the child dataset

appdata-userdata ACL.png

pgdata ACL.png

Edited by EduardoM
text resize
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×