opencloud install on a Truenas Scale system - looking to replace Nextcloud AIO

[aedavis22]

I am wondering if anyone has had any experience in using or deploying the opencloud setup to a Truenas Scale server. It is very robust, supports dockers, LXC containers as well as full blown VMs and I just decided to move to it from Proxmox due to the included LXC and I need to replace Nextcloud AIO due to it's weird complexity, strange data access and ULTRA slow speeds. I am hoping that opencloud has some sort of team based tele meeting system such as Microsoft Teams or Zoom and clients for both IOS and Android. I look forward to hearing from all of you.

Thanks,

Tony Davis

[schlaggi]

I installed it in a separate container. Just go to instances --> create new instance, set name, container, any distro, cpu&memory (like 2 cores, 2 GB) and disable the default network settings and select your adapter. Then create the instance.
You can then open the shell in the container and follow the normal OpenCloud installation. The instance gets its own ip address in your network, where OpenCloud will be available.
Hope that helps.

[haldi4803]

App in TrueNAS Scale (the yaml way)

Would you mind sharing?

[marco79cgn]

App in TrueNAS Scale (the yaml way)

Would you mind sharing?

In TrueNAS Scale → Apps → Discover Apps → push the three dots → Install via YAML

The yaml file looks like this:

services:
  opencloud-rolling:
    container_name: opencloud
    volumes:
      - opencloud-data:/var/lib/opencloud
      - opencloud-config:/etc/opencloud
    image: opencloudeu/opencloud-rolling
    ports:
      - 9200:9200
    entrypoint:
      - /bin/sh
    command:
      - '-c'
      - opencloud init --insecure true || true; opencloud server
    environment:
      - IDM_CREATE_DEMO_USERS=false
      - OC_URL=https://[your-ip-address]:[port]
volumes:
  opencloud-data:
  opencloud-config:

This works pretty well, but the data volume is also stored inside the Apps Dataset (SSD in my case) which is not what I want. I want to store the open cloud data on my HDD dataset. I don't know how to achieve this with the custom Apps/yaml way. That's why I changed to the Instances approach where I can mount a folder from the HDD dataset. Unfortunately there is a bug in Open Cloud which leads to not working bind mounts. Therefore I made a symlink to the docker volumes directory (/var/lib/docker/volumes -> /mnt/HDD/OpenCloud/opencloud/).
//EDIT: outdated, see my comment here

[haldi4803]

You don't need to create volumes if you want persistent storage.

services:
  opencloud-rolling:
    container_name: opencloud
    volumes:
      - /mnt/NVME/docker/opencloud/data:/var/lib/opencloud
      - /mnt/NVME/docker/opencloud/config:/etc/opencloud
    image: opencloudeu/opencloud-rolling
    ports:
      - 9200:9200
    entrypoint:
      - /bin/sh
    command:
      - '-c'
      - opencloud init --insecure true || true; opencloud server
    environment:
      - IDM_CREATE_DEMO_USERS=false
      - OC_URL=https://[your-ip-address]

[marco79cgn]

You don't need to create volumes if you want persistent storage.

In theory yes, but as I said, there seems to be a bug in the current version of OpenCloud if you try to work with bind mounts (folders) instead of named volumes. It always throws a "permission denied" error. This guy here noticed the same thing. That's why I ended up using volume mounts and symlinked them to another folder.

[micbar]

If you use bind mounts, you need to have the correct file system ownerships (1000:1000) and your filesystem needs support for extended attributes.

[naamah75]

I got this error... what I'm wrong? tried yaml posted by @marco79cgn marco

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/middlewared/job.py", line 515, in run
    await self.future
  File "/usr/lib/python3/dist-packages/middlewared/job.py", line 562, in __run_body
    rv = await self.middleware.run_in_thread(self.method, *args)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/middlewared/main.py", line 622, in run_in_thread
    return await self.run_in_executor(io_thread_pool_executor, method, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/middlewared/main.py", line 619, in run_in_executor
    return await loop.run_in_executor(pool, functools.partial(method, *args, **kwargs))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/middlewared/service/crud_service.py", line 294, in nf
    rv = func(*args, **kwargs)
         ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/middlewared/api/base/decorator.py", line 101, in wrapped
    result = func(*args)
             ^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/middlewared/plugins/apps/crud.py", line 130, in do_create
    return self.middleware.call_sync('app.custom.create', data, job)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1036, in call_sync
    return methodobj(*prepared_call.args)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/middlewared/plugins/apps/custom_app.py", line 84, in create
    raise e from None
  File "/usr/lib/python3/dist-packages/middlewared/plugins/apps/custom_app.py", line 74, in create
    compose_action(app_name, version, 'up', force_recreate=True, remove_orphans=True)
  File "/usr/lib/python3/dist-packages/middlewared/plugins/apps/compose_utils.py", line 36, in compose_action
    compose_action(app_name, app_version, 'down', remove_orphans=True)
  File "/usr/lib/python3/dist-packages/middlewared/plugins/apps/compose_utils.py", line 61, in compose_action
    raise CallError(err_msg)
middlewared.service_exception.CallError: [EFAULT] Failed 'down' action for 'opencloud' app. Please check /var/log/app_lifecycle.log for more details

[schlaggi]

Please open the file „/var/log/app_lifecycle.log“.
It’s usually the only way to reliably say what went wrong.

[naamah75]

Found!
OC_URL=https://[your-ip-address]:[port]
not
OC_URL=https://[your-ip-address]

[naamah75]

but now I can't log in with the default credentials admin:admin

{"level":"error","service":"idm","bind_dn":"uid=admin,ou=users,o=libregraph-idm","op":"bind","remote_addr":"127.0.0.1:42230","time":"2025-06-11T06:21:19Z","message":"invalid credentials"}

[marco79cgn]

but now I can't log in with the default credentials admin:admin

Check the logs of the container for your unique credentials. They are printed there.

[naamah75]

Try to login but I got Unexpected HTTP response: 500. Please check your connection and try again.

This is the ouput of the command opencloud init --insecure true -f -ap MYPASSWORD

=========================================
 generated OpenCloud Config
=========================================
 configpath : /etc/opencloud/opencloud.yaml
 user       : admin
 password   : MYPASSWORD


=========================================
An older config file has been backed up to
 /etc/opencloud/opencloud.yaml.2025-06-11-09-55-22.backup

This is the log of my container:

2025-06-11 09:56:02.275355+00:00{"level":"error","service":"ocm","error":"'web reachability': could not connect to http server: Get \"http://127.0.0.1:9280\": dial tcp 127.0.0.1:9280: connect: connection refused","time":"2025-06-11T09:56:02Z","message":"check failed"}
2025-06-11 09:56:57.711243+00:002025/06/11 09:56:57 http: TLS handshake error from 10.0.0.53:1120: remote error: tls: unknown certificate
2025-06-11 09:56:57.727538+00:002025/06/11 09:56:57 http: TLS handshake error from 10.0.0.53:1121: remote error: tls: unknown certificate
2025-06-11 09:56:57.813569+00:002025/06/11 09:56:57 http: TLS handshake error from 10.0.0.53:1124: remote error: tls: unknown certificate
2025-06-11 09:56:57.818440+00:002025/06/11 09:56:57 http: TLS handshake error from 10.0.0.53:1125: remote error: tls: unknown certificate
2025-06-11 09:56:57.826249+00:002025/06/11 09:56:57 http: TLS handshake error from 10.0.0.53:1126: remote error: tls: unknown certificate
2025-06-11 09:57:02.296095+00:00{"level":"error","service":"storage-system","pkg":"rgrpc","traceid":"85b4a5b30401e230d7bf193aedf8ffee","error":"error: not found: space jsoncs3-public-share-manager-metadata not found","status":{"code":6,"message":"not found when listing spaces","trace":"85b4a5b30401e230d7bf193aedf8ffee"},"filters":[{"type":2,"Term":{"Id":{"opaque_id":"jsoncs3-public-share-manager-metadata!jsoncs3-public-share-manager-metadata"}}}],"time":"2025-06-11T09:57:02Z","message":"failed to list storage spaces"}
2025-06-11 09:57:06.955558+00:00{"level":"error","service":"idm","bind_dn":"uid=idp,ou=sysusers,o=libregraph-idm","op":"bind","remote_addr":"127.0.0.1:40810","time":"2025-06-11T09:57:06Z","message":"invalid credentials"}
2025-06-11 09:57:06.957211+00:00{"level":"error","service":"idp","error":"ldap identifier backend logon connect error: LDAP Result Code 49 \"Invalid Credentials\": ","time":"2025-06-11T09:57:06Z","message":"identifier failed to logon with backend"}

[naamah75]

tryed also to reset password with

~ $ opencloud idm resetpassword

but I got another error:

Resetting password for user 'uid=admin,ou=users,o=libregraph-idm'.
Enter new password: 
Re-enter new password: 
{"level":"error","service":"idm","db":"/var/lib/opencloud/idm/idm.boltdb","error":"timeout","time":"2025-06-11T13:25:49Z","message":"Error opening database"}
Failed to open database: 'timeout'. Please stop any running OpenCloud idm instance, as this tool requires exclusive access to the database.
timeout

[canusaswede]

I've followed the instructions from here: https://docs.opencloud.eu/docs/admin/getting-started/container/docker-compose in the TrueNas Shell, per the guidance of this YouTube video: https://www.youtube.com/watch?v=mOkNYmjg_5M and am currently stuck with the attached error when, on Step#5, Starting OpenCloud with the command of: docker compose up -d

[canusaswede]

apologies; failed to mention that I am a complete NOOB to using Docker. this project is my very first attempt and I have truly surprised my self at how far I've made it so far, but I am totally lost with the "how-to" of your suggestion :(

[micbar]

@canusaswede Ok. Let me try to explain. I think your problem is not related to docker.

1. You TrueNAS system is connected to the network
2. I suppose it has a web Interface.
3. Web browsers are using port 443 for https:// and port 80 for http:// addresses.

The openCloud docker compose cannot start because it cannot use port 80 because some other service on your TrueNAS is already using port 80. This conflict needs to be resolved.

[canusaswede]

completely understand; absolutely correct. how do I resolve the issue with your suggestion(s) of checking for Apache or nginx and stop them? In the TrueNAS UI itself? If so, there are none of either there

[micbar]

I see the same question in another thread about synology: https://github.com/orgs/opencloud-eu/discussions/1105

Maybe TrueNAS has its own reverse proxy? Then you need to use this guide and set up the external proxy to route to the opencloud services. https://github.com/opencloud-eu/opencloud-compose/?tab=readme-ov-file#behind-external-proxy

[canusaswede]

with those threads, sounds like a deployment with Portainer might be a better deployment solution (?)

[Jorysm]

@marco79cgn

I made a symlink to the docker volumes directory (/var/lib/docker/volumes -> /mnt/HDD/OpenCloud/opencloud/).

Can you tell us more about this? How did you do it?

[marco79cgn]

Thanks to the comments here by @micbar I found an easier solution. Use it at your own risk!

In TrueNAS Community/Scale:

1. create a new Dataset on your HDD pool, name it for example opencloud and grant apps (built-in) permissions
2. go to Instances create a new instance and choose Ubuntu noble
3. under Storage → Disks choose the dataset you created in 1. and as destination choose e.g. /mnt/data
4. click "Create"
5. click on the new instance in the TrueNAS GUI and choose Tools → Shell (to open a shell)
6. create two new folders: mkdir /mnt/data/config && mkdir /mnt/data/opencloud-data
7. important: set permissions to user 1000: sudo chown -R 1000:1000 /mnt/data
8. install docker:

apt update && apt upgrade -y
sudo apt-get install ca-certificates curl -y
sudo install -m 0755 -d /etc/apt/keyrings
sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.asc
sudo chmod a+r /etc/apt/keyrings/docker.asc
echo   "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/ubuntu \
$(. /etc/os-release && echo "${UBUNTU_CODENAME:-$VERSION_CODENAME}") stable" |   sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
sudo apt-get update
sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
systemctl enable docker && systemctl start docker

9. obtain the ip address of your instance: hostname -I (e.g. 192.168.178.23) → use this in step 10 as OC_URL
10. create docker-compose.yaml:

services:
  opencloud-rolling:
    container_name: opencloud
    volumes:
      - /mnt/data/opencloud-data:/var/lib/opencloud
      - /mnt/data/config:/etc/opencloud
    image: opencloudeu/opencloud-rolling
    ports:
      - 9200:9200
    entrypoint:
      - /bin/sh
    command:
      - '-c'
      - opencloud init --insecure true || true; opencloud server
    environment:
      - IDM_CREATE_DEMO_USERS=false
      - OC_URL=https://[your-ip-address]:[port]

11. check the docker logs to obtain your credentials: docker logs opencloud

That's it. I'm running Pangolin on a small public VPS (Strato, 1€/month) which tunnels my public domain opencloud.my-domain.de to the opencloud instance running on my local TrueNAS. This way I can access it from a public url, share links and even have an https connection with valid certificate (from Pangolin). I know that this is not the recommended way but it works. So in my case I don't need to specify a port in the OC_URL. Other users here (like @naamah75) have reported that it only works for them with a port number (9200). Try whatever works for you.

[R-Nabil]

Why is it not recommended way ? It looks to me like your approach is safe no ?

[VentingBow5]

This is the yaml file I am running successfully in TrueNAS (Install via YAML):

services:
  opencloud-rolling:
    command:
      - '-c'
      - opencloud init --insecure true || true; opencloud server
    container_name: opencloud
    entrypoint:
      - /bin/sh
    environment:
      - IDM_CREATE_DEMO_USERS=false
      - OC_URL=https://opencloud.your.domain
    image: opencloudeu/opencloud-rolling
    ports:
      - '9200:9200'
    restart: unless-stopped
    volumes:
      - /mnt/hdd/apps/opencloud/data:/var/lib/opencloud
      - /mnt/hdd/apps/opencloud/config:/etc/opencloud

For the bind mounts to work add the following file ownership 1000:1000 to the respective datasets.

[canusaswede]

file is present; from what I can see/interpret, server address is 1,000% correct throughout it, yet I'm still getting the same doggone error

[haldi4803]

Using ixVolume as Data folder works. Changing that to an existing Folder via Hostpath gives error 500 at login
Unexpected HTTP response: 500. Please check your connection and try again.

i assume thats the folder permission issue everyone is talking about? App runs as 568 and user "apps" has access to the folder. Works for Jellyfin/filbrowser and others.

2025-09-28 10:39:38.720533+00:00Config file not found!
2025-09-28 10:39:39.010734+00:002025-09-28T10:39:39.010734195Z
2025-09-28 10:39:39.010756+00:00=========================================
2025-09-28 10:39:39.010771+00:00generated OpenCloud Config
2025-09-28 10:39:39.010778+00:00=========================================
2025-09-28 10:39:39.010785+00:00configpath : /etc/opencloud/opencloud.yaml
2025-09-28 10:39:39.010799+00:00user       : admin
2025-09-28 10:39:39.010806+00:00password   : admin
2025-09-28 10:39:39.010813+00:002025-09-28T10:39:39.010813414Z
2025-09-28 10:39:39.015365+00:00Starting OpenCloud...
2025-09-28 10:40:40.019613+00:00{"level":"error","service":"storage-system","host.name":"984dd9ee469a","pkg":"rgrpc","traceid":"ae533548c959a763c649aea21f2c8f9a","error":"error: not found: space jsoncs3-public-share-manager-metadata not found","status":{"code":6,"message":"not found when listing spaces","trace":"ae533548c959a763c649aea21f2c8f9a"},"filters":[{"type":2,"Term":{"Id":{"opaque_id":"jsoncs3-public-share-manager-metadata!jsoncs3-public-share-manager-metadata"}}}],"time":"2025-09-28T10:40:40Z","message":"failed to list storage spaces"}
2025-09-28 10:41:40.006465+00:00{"level":"error","service":"storage-system","host.name":"984dd9ee469a","pkg":"rgrpc","traceid":"66b10cf6f19a70aca44041d80d41ec89","error":"error: not found: space jsoncs3-public-share-manager-metadata not found","status":{"code":6,"message":"not found when listing spaces","trace":"66b10cf6f19a70aca44041d80d41ec89"},"filters":[{"type":2,"Term":{"Id":{"opaque_id":"jsoncs3-public-share-manager-metadata!jsoncs3-public-share-manager-metadata"}}}],"time":"2025-09-28T10:41:40Z","message":"failed to list storage spaces"}
2025-09-28 10:42:40.006651+00:00{"level":"error","service":"storage-system","host.name":"984dd9ee469a","pkg":"rgrpc","traceid":"729feada170381d91697b70de58c8bde","error":"error: not found: space jsoncs3-public-share-manager-metadata not found","status":{"code":6,"message":"not found when listing spaces","trace":"729feada170381d91697b70de58c8bde"},"filters":[{"type":2,"Term":{"Id":{"opaque_id":"jsoncs3-public-share-manager-metadata!jsoncs3-public-share-manager-metadata"}}}],"time":"2025-09-28T10:42:40Z","message":"failed to list storage spaces"}
2025-09-28 10:43:40.005606+00:00{"level":"error","service":"storage-system","host.name":"984dd9ee469a","pkg":"rgrpc","traceid":"abf1b5ac2ae23eface4343aa75425248","error":"error: not found: space jsoncs3-public-share-manager-metadata not found","status":{"code":6,"message":"not found when listing spaces","trace":"abf1b5ac2ae23eface4343aa75425248"},"filters":[{"type":2,"Term":{"Id":{"opaque_id":"jsoncs3-public-share-manager-metadata!jsoncs3-public-share-manager-metadata"}}}],"time":"2025-09-28T10:43:40Z","message":"failed to list storage spaces"}
2025-09-28 10:44:22.558858+00:00{"level":"error","service":"proxy","error":"failed to verify access token: token signature is invalid: crypto/rsa: verification error","authenticator":"oidc","path":"/ocs/v1.php/cloud/capabilities","user_agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:143.0) Gecko/20100101 Firefox/143.0","client.address":"192.168.1.200","network.peer.address":"","network.peer.port":"","time":"2025-09-28T10:44:22Z","message":"failed to authenticate the request"}
2025-09-28 10:44:22.571959+00:00{"level":"error","service":"proxy","error":"failed to verify access token: token signature is invalid: crypto/rsa: verification error","authenticator":"oidc","path":"/api/v0/settings/roles-list","user_agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:143.0) Gecko/20100101 Firefox/143.0","client.address":"192.168.1.200","network.peer.address":"","network.peer.port":"","time":"2025-09-28T10:44:22Z","message":"failed to authenticate the request"}
2025-09-28 10:44:22.575615+00:00{"level":"error","service":"proxy","error":"failed to verify access token: token signature is invalid: crypto/rsa: verification error","authenticator":"oidc","path":"/graph/v1.0/me","user_agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:143.0) Gecko/20100101 Firefox/143.0","client.address":"192.168.1.200","network.peer.address":"","network.peer.port":"","time":"2025-09-28T10:44:22Z","message":"failed to authenticate the request"}
2025-09-28 10:44:26.944209+00:00{"level":"error","service":"idm","bind_dn":"uid=idp,ou=sysusers,o=libregraph-idm","op":"bind","remote_addr":"127.0.0.1:39118","time":"2025-09-28T10:44:26Z","message":"invalid credentials"}
2025-09-28 10:44:26.944557+00:00{"level":"error","service":"idp","error":"ldap identifier backend logon connect error: LDAP Result Code 49 \"Invalid Credentials\": ","time":"2025-09-28T10:44:26Z","message":"identifier failed to logon with backend"}
2025-09-28 10:44:40.005714+00:00{"level":"error","service":"storage-system","host.name":"984dd9ee469a","pkg":"rgrpc","traceid":"3e0f18cff1ca4543c3faa21637e3e593","error":"error: not found: space jsoncs3-public-share-manager-metadata not found","status":{"code":6,"message":"not found when listing spaces","trace":"3e0f18cff1ca4543c3faa21637e3e593"},"filters":[{"type":2,"Term":{"Id":{"opaque_id":"jsoncs3-public-share-manager-metadata!jsoncs3-public-share-manager-metadata"}}}],"time":"2025-09-28T10:44:40Z","message":"failed to list storage spaces"}

Edit:
Okay... that might be my Stupidity only...
the DATA folder is NOT where your Files/Data is Stored but for OpenClouds OWN data?
SO how exactly do you Mount your own already existing Data into Opencloud???

[micbar]

SO how exactly do you Mount your own already existing Data into Opencloud???

opencloud uses 1000:1000 for file ownership. You need to mount your folder like https://github.com/opencloud-eu/opencloud-compose/blob/main/.env.example#L104-L115

[canusaswede]

Using ixVolume as Data folder works. Changing that to an existing Folder via Hostpath gives error 500 at login Unexpected HTTP response: 500. Please check your connection and try again.

i assume thats the folder permission issue everyone is talking about? App runs as 568 and user "apps" has access to the folder. Works for Jellyfin/filbrowser and others.

2025-09-28 10:39:38.720533+00:00Config file not found!
2025-09-28 10:39:39.010734+00:002025-09-28T10:39:39.010734195Z
2025-09-28 10:39:39.010756+00:00=========================================
2025-09-28 10:39:39.010771+00:00generated OpenCloud Config
2025-09-28 10:39:39.010778+00:00=========================================
2025-09-28 10:39:39.010785+00:00configpath : /etc/opencloud/opencloud.yaml
2025-09-28 10:39:39.010799+00:00user       : admin
2025-09-28 10:39:39.010806+00:00password   : admin
2025-09-28 10:39:39.010813+00:002025-09-28T10:39:39.010813414Z
2025-09-28 10:39:39.015365+00:00Starting OpenCloud...
2025-09-28 10:40:40.019613+00:00{"level":"error","service":"storage-system","host.name":"984dd9ee469a","pkg":"rgrpc","traceid":"ae533548c959a763c649aea21f2c8f9a","error":"error: not found: space jsoncs3-public-share-manager-metadata not found","status":{"code":6,"message":"not found when listing spaces","trace":"ae533548c959a763c649aea21f2c8f9a"},"filters":[{"type":2,"Term":{"Id":{"opaque_id":"jsoncs3-public-share-manager-metadata!jsoncs3-public-share-manager-metadata"}}}],"time":"2025-09-28T10:40:40Z","message":"failed to list storage spaces"}
2025-09-28 10:41:40.006465+00:00{"level":"error","service":"storage-system","host.name":"984dd9ee469a","pkg":"rgrpc","traceid":"66b10cf6f19a70aca44041d80d41ec89","error":"error: not found: space jsoncs3-public-share-manager-metadata not found","status":{"code":6,"message":"not found when listing spaces","trace":"66b10cf6f19a70aca44041d80d41ec89"},"filters":[{"type":2,"Term":{"Id":{"opaque_id":"jsoncs3-public-share-manager-metadata!jsoncs3-public-share-manager-metadata"}}}],"time":"2025-09-28T10:41:40Z","message":"failed to list storage spaces"}
2025-09-28 10:42:40.006651+00:00{"level":"error","service":"storage-system","host.name":"984dd9ee469a","pkg":"rgrpc","traceid":"729feada170381d91697b70de58c8bde","error":"error: not found: space jsoncs3-public-share-manager-metadata not found","status":{"code":6,"message":"not found when listing spaces","trace":"729feada170381d91697b70de58c8bde"},"filters":[{"type":2,"Term":{"Id":{"opaque_id":"jsoncs3-public-share-manager-metadata!jsoncs3-public-share-manager-metadata"}}}],"time":"2025-09-28T10:42:40Z","message":"failed to list storage spaces"}
2025-09-28 10:43:40.005606+00:00{"level":"error","service":"storage-system","host.name":"984dd9ee469a","pkg":"rgrpc","traceid":"abf1b5ac2ae23eface4343aa75425248","error":"error: not found: space jsoncs3-public-share-manager-metadata not found","status":{"code":6,"message":"not found when listing spaces","trace":"abf1b5ac2ae23eface4343aa75425248"},"filters":[{"type":2,"Term":{"Id":{"opaque_id":"jsoncs3-public-share-manager-metadata!jsoncs3-public-share-manager-metadata"}}}],"time":"2025-09-28T10:43:40Z","message":"failed to list storage spaces"}
2025-09-28 10:44:22.558858+00:00{"level":"error","service":"proxy","error":"failed to verify access token: token signature is invalid: crypto/rsa: verification error","authenticator":"oidc","path":"/ocs/v1.php/cloud/capabilities","user_agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:143.0) Gecko/20100101 Firefox/143.0","client.address":"192.168.1.200","network.peer.address":"","network.peer.port":"","time":"2025-09-28T10:44:22Z","message":"failed to authenticate the request"}
2025-09-28 10:44:22.571959+00:00{"level":"error","service":"proxy","error":"failed to verify access token: token signature is invalid: crypto/rsa: verification error","authenticator":"oidc","path":"/api/v0/settings/roles-list","user_agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:143.0) Gecko/20100101 Firefox/143.0","client.address":"192.168.1.200","network.peer.address":"","network.peer.port":"","time":"2025-09-28T10:44:22Z","message":"failed to authenticate the request"}
2025-09-28 10:44:22.575615+00:00{"level":"error","service":"proxy","error":"failed to verify access token: token signature is invalid: crypto/rsa: verification error","authenticator":"oidc","path":"/graph/v1.0/me","user_agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:143.0) Gecko/20100101 Firefox/143.0","client.address":"192.168.1.200","network.peer.address":"","network.peer.port":"","time":"2025-09-28T10:44:22Z","message":"failed to authenticate the request"}
2025-09-28 10:44:26.944209+00:00{"level":"error","service":"idm","bind_dn":"uid=idp,ou=sysusers,o=libregraph-idm","op":"bind","remote_addr":"127.0.0.1:39118","time":"2025-09-28T10:44:26Z","message":"invalid credentials"}
2025-09-28 10:44:26.944557+00:00{"level":"error","service":"idp","error":"ldap identifier backend logon connect error: LDAP Result Code 49 \"Invalid Credentials\": ","time":"2025-09-28T10:44:26Z","message":"identifier failed to logon with backend"}
2025-09-28 10:44:40.005714+00:00{"level":"error","service":"storage-system","host.name":"984dd9ee469a","pkg":"rgrpc","traceid":"3e0f18cff1ca4543c3faa21637e3e593","error":"error: not found: space jsoncs3-public-share-manager-metadata not found","status":{"code":6,"message":"not found when listing spaces","trace":"3e0f18cff1ca4543c3faa21637e3e593"},"filters":[{"type":2,"Term":{"Id":{"opaque_id":"jsoncs3-public-share-manager-metadata!jsoncs3-public-share-manager-metadata"}}}],"time":"2025-09-28T10:44:40Z","message":"failed to list storage spaces"}

Edit: Okay... that might be my Stupidity only... the DATA folder is NOT where your Files/Data is Stored but for OpenClouds OWN data? SO how exactly do you Mount your own already existing Data into Opencloud???

your path would begin with "/mnt/your/local/folder"

[magnus-soung]

I did this and replaced OC_URL=https://opencloud.your.domain to OC_URL=https://my.ip:port but now I can't tunnel it through cloudflare

[canusaswede]

How does one make file ownership 1000:1000 via YAML? Because neither exists in my credentials list From: VentingBow5 ***@***.***> Sent: Wednesday, September 24, 2025 05:19 To: opencloud-eu/opencloud ***@***.***> Cc: canusaswede ***@***.***>; Mention ***@***.***> Subject: Re: [opencloud-eu/opencloud] opencloud install on a Truenas Scale system - looking to replace Nextcloud AIO (Discussion #788) This is the yaml file I am running successfully in TrueNAS (Install via YAML): services: opencloud-rolling: command: - '-c' - opencloud init --insecure true || true; opencloud server container_name: opencloud entrypoint: - /bin/sh environment: - IDM_CREATE_DEMO_USERS=false - OC_URL=https://opencloud.your.domain image: opencloudeu/opencloud-rolling ports: - '9200:9200' restart: unless-stopped volumes: - /mnt/hdd/apps/opencloud/data:/var/lib/opencloud - /mnt/hdd/apps/opencloud/config:/etc/opencloud For the bind mounts to work add the following file ownership 1000:1000 to the respective folders. image.png (view on web) <https://github.com/user-attachments/assets/2809a24b-25d8-4ea4-947a-056a12e83c1f> — Reply to this email directly, view it on GitHub <#788 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEO325HASOWIWU6LAT7QABL3UKD5BAVCNFSM6AAAAAB4SSQSQCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINBZHAZDINI> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AEO325EQOYSZXCMDT76FFZL3UKD5BA5CNFSM6AAAAAB4SSQSQCWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQA3U44K.gif> Message ID: ***@***.*** ***@***.***> >

[VentingBow5]

Go to the CLI and:

sudo chown -R 1000:1000 /mnt/hdd/apps/opencloud/data:/var/lib/opencloud
sudo chown -R 1000:1000 /mnt/hdd/apps/opencloud/config:/etc/opencloud

That's it.

[canusaswede]

Tried that already – no change I’m really wanting to move away from Cloudflare and Nginx to Pangolin, but find myself in need of some guidance utilizing Newt to get there From: MuffinMonster ***@***.***> Sent: Wednesday, September 24, 2025 11:17 To: opencloud-eu/opencloud ***@***.***> Cc: canusaswede ***@***.***>; Mention ***@***.***> Subject: Re: [opencloud-eu/opencloud] opencloud install on a Truenas Scale system - looking to replace Nextcloud AIO (Discussion #788) Log Error is: config file not found and a: TLS handshake error from 192.168.14.77, several different lines with a slew of variety of ports, which is a virtual device, not the actual truenas instance along with remote error: tls: unknown certificate I'd try to spin it up minimally with just iX Volumes and work my way from there, if it works with iX Volumes the issue stems from your dataset permissions (for the config APPS should work and for the data www-data is what i picked) I use pangolin with opencloud and that's what I put for the Application URL, those two are really the only things that can break as the opencloud truenas app has minimal configuration. — Reply to this email directly, view it on GitHub <#788 (reply in thread)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEO325B27ERLDPFPW7J2GWL3ULN3NAVCNFSM6AAAAAB4SSQSQCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINJQGIYDKOA> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AEO325DSDIGIJ47BDFT2UPL3ULN3NA5CNFSM6AAAAAB4SSQSQCWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQA3VEKU.gif> Message ID: ***@***.*** ***@***.***> >

[canusaswede]

Plus there’s this, as well: From: MuffinMonster ***@***.***> Sent: Wednesday, September 24, 2025 11:17 To: opencloud-eu/opencloud ***@***.***> Cc: canusaswede ***@***.***>; Mention ***@***.***> Subject: Re: [opencloud-eu/opencloud] opencloud install on a Truenas Scale system - looking to replace Nextcloud AIO (Discussion #788) Log Error is: config file not found and a: TLS handshake error from 192.168.14.77, several different lines with a slew of variety of ports, which is a virtual device, not the actual truenas instance along with remote error: tls: unknown certificate I'd try to spin it up minimally with just iX Volumes and work my way from there, if it works with iX Volumes the issue stems from your dataset permissions (for the config APPS should work and for the data www-data is what i picked) I use pangolin with opencloud and that's what I put for the Application URL, those two are really the only things that can break as the opencloud truenas app has minimal configuration. — Reply to this email directly, view it on GitHub <#788 (reply in thread)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEO325B27ERLDPFPW7J2GWL3ULN3NAVCNFSM6AAAAAB4SSQSQCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINJQGIYDKOA> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AEO325DSDIGIJ47BDFT2UPL3ULN3NA5CNFSM6AAAAAB4SSQSQCWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQA3VEKU.gif> Message ID: ***@***.*** ***@***.***> >

[canusaswede]

here's the additional I was referring to yesterday (screenshot didn't come thru):

You have installed an app that needs additional configuration, please see
the following link on how to convert the config.json config into /etc/opencloud/apps.yaml
https://docs.opencloud.eu/docs/dev/server/Services/web/Web-info/#application-configuration

I’m really wanting to move away from Cloudflare and Nginx to Pangolin, but find myself in need of some guidance utilizing Newt to get there

[ronzino83]

If you install using truenas scale app to this.

1. create a dataset opencloud. Owner root, Groups apps . apps is 568
2. create two sub dataset config and store, inherit permissions
3. now the part that should be written better in the auto configuration during installation. IN THE APPLICATION URL you MUST write down also the port so it must be https://yoursite:yourport

if you don't specify the port then the webserver says that config.json is missing

4. specify the application port as the same insert point 3)

[canusaswede]

keep getting "Bad Gateway"

[ronzino83]

I wonder which is the URL of the community that is managing OpenCloud on TrueNas Scale . Does anyone know it ?
I would like to ask how to start opencloud collaboration server that, as far as i understood, is a prerequisite to connect with onlyoffice server

[muffn]

https://github.com/truenas/apps/issues

There you go

[Sudo935]

For anyone else who is looking to run the full OpenCloud stack on TrueNAS Scale, this is what I did to get everything up and running.

Configure TrueNAS

Permissions

Since we want to run containers as user 1000 and group 1000 a new user and group will need to be created in the TrueNAS UI if you chose to assign permissions to Dataset via the UI.

First create the group.

Credentials --> Groups --> Add
GID: 1000
Name: abc
Save

The create the user

Credentials --> Users --> Add
Username: abc
Allow Access: Uncheck all boxes
Authentication: Check the Disable Password box
UID: 1000
Groups: Uncheck Create New Primary Group and enter 1000 for the Primary Group and 1000 for the Auxiliary Groups
Save

Create Datasets

This is how I structure my Datasets in TrueNAS. You can also just have a single OpenCloud folder and the rest will be created when everything is launched.

Pool
  Docker-Apps
    OpenCloud
      Antivirus
      App
      Backup
      Config
      Data
      Monitoring
      Radicale
      Search
      WebOffice

All of these folders may not be needed but I haven't gone through and tested what is and isn't needed. Again, you could just make an OpenCloud folder and stop there. Everything else is to take advantage of TrueNAS Dataset features.

Change the Permissions

Click on the OpenCloud Dataset and scroll down to permissions. Click Edit and then enter the following:

User: abc
Apply User: Checked
Group: abc
Apply Group: Checked

Advanced (Only needed if you made child Datasets
Apply Permissions Recursively: Checked (Confirm the warning that pops up)
Apply Permissions to Child Datasets: Checked

Compose file

This can be done on a separate computer or on the TrueNAS box itself. This is not a full tutorial, if you want that then visit the repository https://github.com/opencloud-eu/opencloud-compose

Clone the OpenCloud-Compose repo: git clone https://github.com/opencloud-eu/opencloud-compose.git
CD into the directory: cd opencloud-compose
Copy the example env file: cp .env.example .env
Go through and edit the env file to include the features you want
Finally, use docker compose to give you a flattened compose file: docker compose config >> final-compose.yaml
You will then need to open the final-compose.yaml file and ensure that all volumes are mapped correctly since docker compose config will map the source of volumes to wherever the opencloud-compose folder is.

With the flattened file you should be able to copy it over into TrueNAS and just run it.

Add the App to TrueNAS

In the Apps tab go to Discover Apps, click the three dots next to the Custom App button and select Install via yaml. From there enter a name for the app all lowercase, and paste in the contents of the final-compose.yaml file then click Save.

Alternatively you could copy the final-compose.yaml file to the root of the OpenCloud Dataset. Then instead of pasting the whole yaml into TrueNAS you can instead do this:

include: 
  - /mnt/Tank/Docker-Apps/OpenCloud/final-compose.yaml
services: {}

And click Save.

This should create the App. If there are any errors you should check the app_lifecycle.log file in a separate window or SSH connection TrueNAS. I usually have a console windows with an SSH connection to my TrueNAS box when adding apps so I can run tail -n 5 /var/log/app_lifecycle.log and see what the error is.