On 8/21/2025 at 8:04 PM, orangerobot said:

I set up OpenCloud using their official docker-compose repository and I'm facing similar issues.

Uploads regularly get stuck and OC is unable to perform any write-operations afterwards, unless I reboot the whole server (restarting the containers isn't enough).

At this point I think it's not possible to setup OpenCloud on Unraid, but I would love to be proven otherwise.

How did you do this? Were you using the unraid compose plugin?

So far I did not heart from any guy: "oh yeah, oc is running like a charm"..

It seems there are some fundamental issues using opencloud (docker) on unraid. On some systems it will not run at all, on the next system it is running but will stuck at a specific kind of file (like nemu reported). My experience is somewhere between these..

All in all opencloud were build modular. You can choose which services you want to use and add them via compose. Unfortunately unraid is not (yet?) prepared for docker-compose without using separate services.

I do not think that could be fixed by the unraid template.

I tried to get it working on my local machine. I had NO issue. It worked as expected. Thus I think the problem lies in the OC repository or in the unraid OS - or both.

Hello again..

I can start and access the container through the webgui.. But i can't make it work with the nginx proxy manager?? I use nginx proxy manager on Lan only, and made my own domain, and i forwarded the container to the right ip address and the right port?? All my other containers in proxy manager works.. its only opencloud that does not work..

Anyone who has a solution??

10 hours ago, Mattti1912 said:

Hello again..

I can start and access the container through the webgui.. But i can't make it work with the nginx proxy manager?? I use nginx proxy manager on Lan only, and made my own domain, and i forwarded the container to the right ip address and the right port?? All my other containers in proxy manager works.. its only opencloud that does not work..

Anyone who has a solution??

No.. it is hard without any further information. But I am also not that familiar with nginx. But maybe this will help you:

Behind External Proxy | OpenCloud Docs

How to run OpenCloud behind an external Nginx proxy with Certbot (manual setup).

Actually this documentation is addressed for compose setups but maybe it gives you an idea to fix your problem.

Hello again and Thank you, so much:)

I' ve tried to fix this, and i got a little bit further.. I went back to nginx proxy manager and set it up with Redirection Hosts.. That works in the browser.. But it still wont work when i use the desktop app:(

Anyone with an idea on how to fix?

Thank you!

On 10/13/2025 at 2:21 PM, caracola said:

Not sure if I got you... You want to be able to access your cloud via lan (without proxy) and access it via www by your proxy?

You could not get it to work without proxy, or could you?

yeah i couldn't get past the "Missing or invalid config" unless i used the external proxy address. but i ran into another issue which has me giving up on this project for the time being. i uploaded a few folders worth of files. couldn't have been more than 3 folders with 10 documents each and the application only uploaded 4 documents and acted like it was still uploading. it wasnt more than 8MB worth of PDF's. Then i tried it from my phone and the docker hung along with my whole server. reboot and a parity check later (no issues found) and now the docker wont start. i tried deleting just the docker image and reinstalling it and i get a 500 error when i try to login. not getting the warm and fuzees to host my personal data. might revisit later.

From reading through the 3 pages of posts it sounds like Nextcloud is the only good option even though it's not that good.

My Unraid docker of opencloud has all files and folders set to nobody and has RW permissions set, has no errors in the logs, oc_insecure set to true and I can't even see a webui. I get:

This site can’t be reached

https://[Docker-IP]:9200/ is unreachable.

14 hours ago, scottygood said:

From reading through the 3 pages of posts it sounds like Nextcloud is the only good option even though it's not that good.

My Unraid docker of opencloud has all files and folders set to nobody and has RW permissions set, has no errors in the logs, oc_insecure set to true and I can't even see a webui. I get:

This site can’t be reached

https://[Docker-IP]:9200/ is unreachable.

Well, yes.. you can come to this assumption. But I think the feedback within this thread is a bit misleading, due to all these issues. I had really good experience when starting OC outside of unraid.

First of all try to change ownership of your config and data directory within unraid to 1000:1000

Is the log file empty or only without errors, as you said?

First of all: for all subsequent attempts, I set the permissions for the OC config and data directory to 1000:1000 using chown.

I installed OC with init as a post argument in a first run. Then, after OC stopped, I removed init and restarted the template. Log file without notes. When I call up the OC WebUI, I get the following message (in German):

"Missing or incorrect configuration.

Please check whether the config.json configuration file exists and is valid.

Please also check the browser console for further information."

Based on a tip in another forum, I reset everything and reinstalled OC with the post argument: opencloud init --diff. Template installed (log without errors) and after stopping the container, I removed the post argument on the second run. The log then displays this message twice (in English):

"The jwt_secret has not been set properly in your config for opencloud. Make sure your /etc/opencloud config contains the proper values (e.g. by using ‘opencloud init --diff’ and applying the patch or setting a value manually in the config/corresponding environment variable)",

with the result that the container does not start.

Can anyone help here, or do I have to work with NC because it seems to be easier to install under unraid?

I found an excellent set of instructions for OpenCloud as an LXC on the German part of the site. It works perfectly for me.

I'm still tinkering with my template and try to get more stuff working. I've managed to get the "App-Store" running. Even it's not a real store. So let's say it this way: you can download the files from the App store place it in your specific unraid folder and it installs and is working.

I have also not a lot of time, but I will check, if it's possible to get more stuff working with an unraid template.

Edited October 30, 2025Oct 30 by Nemu

On 10/15/2025 at 1:03 AM, Mattti1912 said:

I' ve tried to fix this, and i got a little bit further.. I went back to nginx proxy manager and set it up with Redirection Hosts.. That works in the browser.

Please, can you describe this. What did you change that you can reach OC with nginx proxy manager?

Hey guys. Short question. I've made a lot of progress running opencloud via templates. Unfortunately it needs some files to be pre placed or created via script. I have all set up but I have a question, what you prefer.

In general opencloud with additional services ( as collabora) relies on an env. file.

I can prepare two options.

1. Adding most of the variables and ports to the template, which makes the template a bit confusing.

2. I can make the template to read the env file, so that the user can create change all variables in the file, similar to the installation method of the official docker compose.

What I have running is opencloud, with app store and working collabora.

So overall three templates -> opencloud, collabora and wopi server.

I have also the config files for swag. Tough, I was not able to get it working with NPM, but I'm not very good in the proxy stuff.

I'm working on the remaining opencloud features as keycloak, but I can release a first version here.

Further, is anyone interested in maintaining the templates? @mcreekmore ??? Maybe together? My time is also very limited.

Edited December 10, 2025Dec 10 by Nemu

I will skip the env file approach. I'm preparing the instructions and will upload a link to my GitHub for first downloading and testing.

Chiming in. I can't use a revere proxy due to ISP issues, but I did get OpenCloud up and running with a Tailscale funnel, so I can access via internet (outside of Tailscale). You don't get a custom hostname, but I don't really care. I used TDSProxy, since the UnRaid built-in Tailscale routing caused the container to crash. Once I had it up locally, I added it to TDSProxy (using HTTPS, but TLS Validate=no), validated in Tailscale, then edited the container changing the host ip to my Tailscale url, changed insecure to false, then restarted the container. It worked right away and all apps can access it. Hope this helps someone, especially those who can't reverse proxy.

As promised, here my repo with the xml files and proxy confs. I´ve also created a pre_install_script. The script creates the folders (you can change the path manually) with correct permissions. Further, you can set collabora=true,
and add your domains. Then the template will also create the neccesary files (csp.yaml and banned-password-list.txt).
To use the script, I recommend to the "user scripts" plugin from community store. Just create a new script and copy the code from my script ove and run it.

My setup is: Cloudflare tunnel for the opencloud domain (published application route directly to the container). for the wopi server (collaboration container) and collabora I set a DNS rewrite in adguard home so that the container communicatin never leaves my local network.
Tough, I was not able to get it working with NGinX Proxy Manager, but I´m not that good in proxy stuff and also used AI to create the swag files correctly (based on the opencloud nginx sample).

If you just want to run opencloud without collabora. use the opencloud template. remove all variables under "show more settings"
if you want to run it locally, Just use https://localhost:9200 as OC_URL variable. be aware. you need to access the web ui via httpS !!
Your browser will tell you, that the site is not secure. you can click on advanced and the accept to continue to access page.

https://github.com/Nemuritor01/Opencloud-Unraid-Templates

If it works, I´m fine if mcreekmore wants to change his community template. As I said, I have not a lot of time to maintain this.

Contribution is very welcome to get this fully working.
my next step is integrating radicale.

1 hour ago, akshunj said:

Chiming in. I can't use a revere proxy due to ISP issues, but I did get OpenCloud up and running with a Tailscale funnel, so I can access via internet (outside of Tailscale). You don't get a custom hostname, but I don't really care. I used TDSProxy, since the UnRaid built-in Tailscale routing caused the container to crash. Once I had it up locally, I added it to TDSProxy (using HTTPS, but TLS Validate=no), validated in Tailscale, then edited the container changing the host ip to my Tailscale url, changed insecure to false, then restarted the container. It worked right away and all apps can access it. Hope this helps someone, especially those who can't reverse proxy.

This sounds interesting. Yes, the opencloud container crashes with tailscale. reason is the entrypint in the extra parameters. This prevents the container to download and run tailscale, but it´s neccessary to run opencloud. never heard about tds proxy but looks interesting. very interesting.

On 12/12/2025 at 6:48 PM, Nemu said:

never heard about tds proxy but looks interesting. very interesting.

Because of my reverse proxy situation, I have to rely on Tailscale for any containers I want to expose to the internet. But not all of them work seamlessly with the built-in docker Tailscale. TSDProxy (I used the wrong name in my previous post) is a great solution for those situations.

GitHub

GitHub - almeidapaulopt/tsdproxy: Tailscale Docker Proxy

Tailscale Docker Proxy. Contribute to almeidapaulopt/tsdproxy development by creating an account on GitHub.

It's in the apps tab, and requires the "labels" plugin for configuration. Great and easy to use solution.

1 hour ago, akshunj said:

Because of my reverse proxy situation, I have to rely on Tailscale for any containers I want to expose to the internet. But not all of them work seamlessly with the built-in docker Tailscale. TSDProxy (I used the wrong name in my previous post) is a great solution for those situations.

GitHub

GitHub - almeidapaulopt/tsdproxy: Tailscale Docker Proxy

Tailscale Docker Proxy. Contribute to almeidapaulopt/tsdproxy development by creating an account on GitHub.

It's in the apps tab, and requires the "labels" plugin for configuration. Great and easy to use solution.

I have already set it up. Great solution, but not for every situation. Seems it's just creates tail scale sub domains for the containers, but not "real" IPs. I often try to use A records in cloudflare and route a sub-domain of my main domain to a tailscale IP. This unfortunately doesn't work work with TSDproxy. Also tried a CNAME record and point it to the tailscale https domain, but this also doesn't work.

Having my sub-domain routed to tailscale would be my go-to solution for opencloud.

1 hour ago, akshunj said:

Because of my reverse proxy situation, I have to rely on Tailscale for any containers I want to expose to the internet. But not all of them work seamlessly with the built-in docker Tailscale. TSDProxy (I used the wrong name in my previous post) is a great solution for those situations.

GitHub

GitHub - almeidapaulopt/tsdproxy: Tailscale Docker Proxy

Tailscale Docker Proxy. Contribute to almeidapaulopt/tsdproxy development by creating an account on GitHub.

It's in the apps tab, and requires the "labels" plugin for configuration. Great and easy to use solution.

I have already set it up. Great solution, but not for every situation. Seems it's just creates tail scale sub domains for the containers, but not "real" IPs. I often try to use A records in cloudflare and route a sub-domain of my main domain to a tailscale IP. This unfortunately doesn't work work with TSDproxy. Also tried a CNAME record and point it to the tailscale https domain, but this also doesn't work.

Having my sub-domain routed to tailscale would be my go-to solution for opencloud.

1 hour ago, akshunj said:

Because of my reverse proxy situation, I have to rely on Tailscale for any containers I want to expose to the internet. But not all of them work seamlessly with the built-in docker Tailscale. TSDProxy (I used the wrong name in my previous post) is a great solution for those situations.

GitHub

GitHub - almeidapaulopt/tsdproxy: Tailscale Docker Proxy

Tailscale Docker Proxy. Contribute to almeidapaulopt/tsdproxy development by creating an account on GitHub.

It's in the apps tab, and requires the "labels" plugin for configuration. Great and easy to use solution.

I have already set it up and tested it. Nice solution, but not for every situation. Unfortunately it seems, that TSDproxy doesn't create a real tailscale IP. It creates tailscale sub-domains for the containers.

My approach is using sub-domains of my main-domain and route them with an A record to the tailscale IP. This is not possible with TSDproxy. I also tried a CNAME record and point it to the tail scale domain, but this also doesn't work. Unfortunately. But still a nice solution.

Thanks @mcreekmore for the effort in creating this community app! However, I wanted to share my experience attempting to use OpenCloud on Unraid.

My Background:

I had been planning to migrate from Seafile to OpenCloud for quite some time. Initially, my goal was to install OpenCloud through Unraid's Docker UI (essentially native docker run configurations).

Testing Phase:

For testing purposes, I set up a complete OpenCloud stack in an Ubuntu VM, including:

- OpenCloud (core)

- Collabora Office

- Apache Tika (using apache/tika:latest-full)

- PocketID as OIDC provider

- I even got OnlyOffice working successfully

I followed the external proxy configuration from the [official OpenCloud docs](https://docs.opencloud.eu/docs/admin/getting-started/container/docker-compose/external-proxy) to use my existing Nginx Proxy Manager on Unraid.

Challenges with Native Docker Deployment:

Unfortunately, when I attempted to replicate the working configuration via Unraid's Docker UI, I ran into issues that prevented a clean deployment. I don't recall all the specific problems, but it wasn't as straightforward as I had hoped.

VM-Specific Challenge:

During VM testing, I also encountered an interesting limitation: I wanted to mount an Unraid share into the VM (via 9P/VirtFS) to store the actual user data on the Unraid array. However, OpenCloud's database and cryptographic key files had write permission issues with the 9P filesystem. This meant I had to keep system data local to the VM.

Final Solution:

After the various challenges, I decided to stick with the VM-based installation that was working reliably. OpenCloud is now in production use on my system.

Backup Strategy:

My data resides in /mnt/user/backup/opencloud/ on the Unraid host. I've integrated this into my existing backup workflows:

- Local backup via rsync to my QNAP NAS

- Cloud backup via restic to pCloud (encrypted)

Conclusion:

While I appreciate the community app effort, my experience suggests that for a stable, production OpenCloud deployment with additional services like Collabora or OnlyOffice, running it in a dedicated VM might be the more reliable approach.

The VM approach provides:

- Better isolation

- Easier troubleshooting

- More predictable behavior with complex docker-compose stacks

- Standard OpenCloud documentation applies directly

Hope this helps others who might be considering their deployment options!

Alternative for External Access: Self-Hosted Tunneling with Pangolin

For those looking for a self-hosted alternative to Cloudflare Tunnel or Tailscale, I'm using Pangolin (https://github.com/fosrl/pangolin) - an open-source tunneled reverse proxy similar to Cloudflare Tunnel but completely self-hosted.

My Setup: - Hetzner VPS running Pangolin (Gerbil + Traefik) - WireGuard tunnel via Newt client (Docker on Unraid) - OpenCloud accessible via custom domain with automatic Let's Encrypt certificates - No ISP port forwarding required - Full control over the entire stack

Advantages: - Complete privacy (no third-party tunneling service) - Custom domains with your own DNS - Built-in identity-aware access control - No vendor lock-in - Works even with CGNAT/DS-Lite

Comparison to mentioned solutions: - More complex than Cloudflare Tunnel (requires VPS) - More flexible than Tailscale (supports public access with auth) - Similar cost to VPS solutions (~$4/month for small VPS)

Happy to share more details if anyone is interested in this approach!

I've managed to install it after short fight - but something doesn't make sense.

I need to run it with folders set to user 1000 - why do we then set puid/guid to 99/100? What is the point? Why docker can't create these folders with correct rights in the first place?

Edited December 18, 2025Dec 18 by Joloxx9

10 minutes ago, Joloxx9 said:

HI all,

I am not sure if the problem is with me but I really struggle to understand how to deploy this thing. With init it says that it got no access to the folders( I have created them and owners are nobody, should I set different owner?)

Without init I got error that jwt_secret is not set.

I am not sure but quite simple thing is made in overcomplicated way. Please advise.

Sounds for me like a permission issue.

Owner of the folders should be 1000:1000.

The uid 1000 usually will get the first additional user.

But you also can change the owner via terminal by typing:

chown -R 1000:1000 /path/to/opencloud

Just now, caracola said:

Sounds for me like a permission issue.

Owner of the folders should be 1000:1000.

The uid 1000 usually will get the first additional user.

But you also can change the owner via terminal by typing:

chown -R 1000:1000 /path/to/opencloud

I've edited the post. Yes I did fixed it by changing permissions, it looks like I need env to change e-mail settings, that is weird :D

Edited December 18, 2025Dec 18 by Joloxx9

Hm okay. Good to hear 😉

Because the container is not running as privileged due to security reasons. Thus it is not able to modify the host system.

1 hour ago, Joloxx9 said:

I've edited the post. Yes I did fixed it by changing permissions, it looks like I need env to change e-mail settings, that is weird :D

Which template did you use? Unraid custom templates shouldn't be able to use the env. file with the variables. You can try my y templates. The script has a user section, which you need to modify. Change domains, folders (if not default) and if you like to install collabora. The script creates the folders, permissions and necessary files for you.

The open cloud template also has the variables for email support.

20 hours ago, Nemu said:

Which template did you use? Unraid custom templates shouldn't be able to use the env. file with the variables. You can try my y templates. The script has a user section, which you need to modify. Change domains, folders (if not default) and if you like to install collabora. The script creates the folders, permissions and necessary files for you.

The open cloud template also has the variables for email support.

I will have a look on, I thought env can be loaded from the file or I could simply add some extra things in the template.

I moved from nextcloud AIO as it was overengineered and slow, opencloud is faster but looks like once I finish everything it wont be any less easier.

Now as I've seen your post I can say, there will be no easy way to get it running unfortunately. Do I really need wopi and nginx? I am already using pangolin as reverse proxy, do I need another one running internally? Cant I just have opencloud + collabra?

Edited December 19, 2025Dec 19 by Joloxx9