Nextcloud App

Apps and Virtualization
1

I installed Nextcloud as an APP and had everything up and running with out issue for several hours. I wanted to add an SMB share so I could access my TrueNAS storage. After configuring my SMB share in TrueNAS Scale, I edited the Nextcloud APP to use that share. I went through the steps and clicked update. It has been stuck on this ever since…

image

I have tried searching for answers without any resolve. I have also tried various settings changes, but still the same issue. Any input would be great. Thanks.

2

Without any more information, I guess I would start by reinstalling Nextcloud. I am not sure what you mean by you edited the app to use the share, since there are multiple data mounts to provide to nextcloud (app/configuation/postgres/data).

3

When you go into the Nextcloud APP edit menu, you can add an SMB share as shown below…

image
image707×1158 14 KB

This is where the problem is. With the configuration as show, it gets hung up as shown in the original post.

4

Where is the samba share located? Is it hosted by the same Truenas that Nextcloud is? What are you trying to accomplish? My Nextcloud data drive is a dataset on my Truenas that I can share. Maybe explain what you are trying to accomplish and why, we could help more.

5

I am simply trying to add an SMB share to the Nextcloud Server in the App settings. The share is on the same Truenas Scale server as the Nextcloud App. There is a place to add additional storage and I am choosing an SMB Share. I already have my Nextcloud AppData Storage and Nextcloud Postgres Data Storage set.

image
image668×667 12 KB

Whenever I do so and then click save, I get the configuration of 40% endlessly. If I go back in and remove the SMB share, it works as it should.

image

6

This is the error message when trying to set this up…

MountVolume.MountDevice failed for volume “nextcloud-nc-0-2456947204” : rpc error: code = Internal desc = volume(10.0.0.103/Nextcloud2_Remote#nextcloud-nc-0-2456947204) mount “/10.0.0.103/Nextcloud2_Remote” on “/var/lib/kubelet/plugins/kubernetes.io/csi/smb.csi.k8s.io/89b25c6bf219a4fb2438b242e09873789d56747b3c27e8dec13ae7dda5b6287b/globalmount” failed with mount failed: exit status 32 Mounting command: mount Mounting arguments: -t cifs -o noperm,gid=33, /10.0.0.103/Nextcloud2_Remote /var/lib/kubelet/plugins/kubernetes.io/csi/smb.csi.k8s.io/89b25c6bf219a4fb2438b242e09873789d56747b3c27e8dec13ae7dda5b6287b/globalmount Output: mount error(2): No such file or directory Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

7

What version of Scale are you using? I see Kubernetes references and the latest scale uses Docker. With my Docker based app, I added a dataset called test and made it a samba share, then pointed NC additional storage at the dataset test (not connecting SMB since it is on the same server). That change worked and deployed. Regardless of version, I would try that. Additionally, I find the docker apps work a bit more seamlessly than K8s, so if you are on an old version of scale, it might be worth upgrading.

8

Hello Theo. Thanks for your help thus far. I am actually running version Dragonfish-24.04.2.2. I just did an APP install from the Discover APPS tab. What selection did you use in additional storage? Host path?

image
image668×667 12 KB

9

I used host path option and then defined the host path as the dataset that was already set up to be an SMB share. That deployed for me, I did not do to much testing on it.