Nextcloud-Dragonfish-Electric-Eel problems Issues affecting the application
Nextcloud-Dragonfish-Electric-Eel problems Issues affecting the application
. 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
xXGl4diatorXx
06-26-2016, 11:30 PM #1Hey 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
To be clear, I tested with the deprecated storage structure option on and off. I spent the whole day trying this. When I turned it back on, there was no game, then I turned it off and it fixed itself.
Sorry to anyone facing the same issue—I didn’t give a definitive solution.
Important tip: Configure your ACLs properly. Both appdata and userdata need www-data for both user and group roles. pgdata (for PostgreSQL) should be set to "netdata" for users, and "docker" for the group. You’ll also need to grant the parent dataset the same permissions in the ACL list to access the child dataset.
Edited January 27, 2025 by EduardoM
Kawaii_Caelyn
06-27-2016, 12:40 AM #2I really don’t understand what I did. I checked the app install settings, removed the host path causing the problem, then reused the same path. The same went for the appdata host path—just repeat the steps and it works again.
To be clear, I tested with the deprecated storage structure option on and off. I spent the whole day trying this. When I turned it back on, there was no game, then I turned it off and it fixed itself.
Sorry to anyone facing the same issue—I didn’t give a definitive solution.
Important tip: Configure your ACLs properly. Both appdata and userdata need www-data for both user and group roles. pgdata (for PostgreSQL) should be set to "netdata" for users, and "docker" for the group. You’ll also need to grant the parent dataset the same permissions in the ACL list to access the child dataset.
Edited January 27, 2025 by EduardoM