On 2/23/2026 at 9:29 PM, Nemu said:

I'm not using tailscale for opencloud. I'm using three of my domains I own. Tough, for collabora and wopi server I've added a dns rewrite (to my swag container) in adguard home. So the internal communication of the stack never leaves my local network.

Opencloud is very "sensitive" regading change of parameters in the the template, which often leads to a corrupt installation. This is due to security issues. Opencloud container e.g. syncs tokens with wopi server. I would highly recommend recreating the stack, before applying changes. Remove the containers and also delete the folders (opencloud and collabora) and start from scratch. With the script, this is not difficult, as most of the data are saved in the script or in the template.

Thank you for your help and for taking the time to build and support this script.

I’ve attempted fresh installs multiple times, but Step 5 (TLS/connectivity) consistently fails. One thing I noticed is that the OpenCloud container is created with the name "OpenCloud" (capitalized), while the SWAG configuration templates reference it as opencloud. I’ve tried adjusting the capitalization in both the container and config files, but the issue persists.

Since I’m not deeply familiar with SWAG, I suspect my configuration might be incorrect. I followed the guide, but I’m unsure if I’ve missed any prerequisites—such as proper certificate paths, NGINX proxy settings, or DNS resolution. It would be helpful to have a way to verify that all prerequisites are met before running the script, as I can’t determine whether the problem lies in my setup or in the execution of the guide.

16 hours ago, CyprienDlp said:

Thank you for your help and for taking the time to build and support this script.

I’ve attempted fresh installs multiple times, but Step 5 (TLS/connectivity) consistently fails. One thing I noticed is that the OpenCloud container is created with the name "OpenCloud" (capitalized), while the SWAG configuration templates reference it as opencloud. I’ve tried adjusting the capitalization in both the container and config files, but the issue persists.

Since I’m not deeply familiar with SWAG, I suspect my configuration might be incorrect. I followed the guide, but I’m unsure if I’ve missed any prerequisites—such as proper certificate paths, NGINX proxy settings, or DNS resolution. It would be helpful to have a way to verify that all prerequisites are met before running the script, as I can’t determine whether the problem lies in my setup or in the execution of the guide.

One issue I have with swag is -> swag finding the container names often doesn't work. But you can use your server IP instead of the container name.

So instead of:

set $upstream_app opencloud;

set $upstream_port 9200;

Use:

set $upstream_app 192.168.178.10;

set $upstream_port 9200;

It's not as versatile as with container names, but I do not change my server IP, so I'm fine.

I just did a change to the network. I'm using Swag on network Bro instead of bridge (or custom network). The reason is the DNS rewrites I'm using, when I access my container from my home network. With Bro network, swag gets a full external IP and listening on ports 443 and 80.

That's necessary to create DNS rewrites. In adguard home (filters -> DNS rewrites) I've entered each of my containers sub-domains and route them to my swag IP. So when I'm at home, my traffic never leaves my home.

This way, I also do not need to make collabora and wopi domains public (via cloudflare or pangolin). Swag is enough.

Everything else in the swag guide you have posted should work and if you are using cloudflare as main DNS provider (as I do), the guide is straight forward.

Once this works, setting up opencloud with the helper script should be easy.

you can also test swag, if you e.g. test just the opencloud container as standalone without collabora etc.

Delete everything.

Don't use the script!Add container and template Opencloud. Remove everything under advanced view. Fill out, admin password and your url (OC_URL). what's in the main view.Then start the container. This is bare bones Opencloud. Then you can test, if your external domain works.

If this is fine, proceed with opencloud+collabora. Remember, you have to copy and paste the full template again.

Edited February 26Feb 26 by Nemu

On 2/15/2026 at 12:24 PM, yonesmit said:

Same problem here. In tests all works ok, windows sync, ios sync, all was ok. When I write 5GB to windows synced folder started correctly but after some time it stops and Unraid became unresponsive. I had to reboot from command line and forced to do a parity check. It's a shame because I liked due to simplicity. Any chance this get fixed? Seems a unraid problem because I don't see reports of this problem in other platforms.

Best Regards

Hi,

had the same problem but found a solution.

Go to Settings -> Global Share Settings and set "Permit exclusive shares" to yes.

My opencloud share was on the cache pool so the requirements were met.

38 minutes ago, Llamrei said:

Hi,

had the same problem but found a solution.

Go to Settings -> Global Share Settings and set "Permit exclusive shares" to yes.

My opencloud share was on the cache pool so the requirements were met.

Just checked my settings. I have already set "permit exclusive shares" to yes. I assume, that's why I did not see this problem. 😅

Hi everyone,

Has anyone successfully upgraded their OpenCloud container (opencloudeu/opencloud-rolling:latest) to version 7.0.0 on Unraid?

After pulling the latest update, my container is stuck in a crash loop. The log shows the following error right before it dies:

The service account id has not been configured for sharing. 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).

I have already tried the following troubleshooting steps, but none of them worked (the container still throws the exact same error):

1. Environment Variables: Added SHARING_SERVICE_ACCOUNT_ID (with the default UUID) and SHARING_SERVICE_ACCOUNT_SECRET (as well as the OC_ prefixed versions) directly to the Unraid Docker template.

2. Config File: Manually appended the sharing: block with service_account_id and service_account_secret to my original opencloud.yaml in appdata.

It seems like the container completely ignores both the env variables and the config file entries for the new sharing service account under Unraid.

Has anyone encountered this during the v7.0.0 upgrade and found a working solution or the correct variable names for Unraid?

Thanks in advance!

EDIT: Got it fixed like written above via editing the config file opencloud.yaml. During troubleshooting, I simply got confused with the paths because my opencloud.yaml mistakenly existed twice—once in the main appdata folder and once in the config subfolder. This caused me to edit the wrong file the entire time, while the container kept reading the other, uncorrected version on startup.

Edited May 26May 26 by SiggiSpak

On 5/26/2026 at 7:45 AM, SiggiSpak said:

Hi everyone,

Has anyone successfully upgraded their OpenCloud container (opencloudeu/opencloud-rolling:latest) to version 7.0.0 on Unraid?

After pulling the latest update, my container is stuck in a crash loop. The log shows the following error right before it dies:

I have already tried the following troubleshooting steps, but none of them worked (the container still throws the exact same error):

1. Environment Variables: Added SHARING_SERVICE_ACCOUNT_ID (with the default UUID) and SHARING_SERVICE_ACCOUNT_SECRET (as well as the OC_ prefixed versions) directly to the Unraid Docker template.

2. Config File: Manually appended the sharing: block with service_account_id and service_account_secret to my original opencloud.yaml in appdata.

It seems like the container completely ignores both the env variables and the config file entries for the new sharing service account under Unraid.

Has anyone encountered this during the v7.0.0 upgrade and found a working solution or the correct variable names for Unraid?

Thanks in advance!

EDIT: Got it fixed like written above via editing the config file opencloud.yaml. During troubleshooting, I simply got confused with the paths because my opencloud.yaml mistakenly existed twice—once in the main appdata folder and once in the config subfolder. This caused me to edit the wrong file the entire time, while the container kept reading the other, uncorrected version on startup.

Having the same issue, had to roll back to 6.2.0. Can you describe in more detail how you got this to work?

Just to let you know. I'm working on a fix and will post an update soon.

On 5/28/2026 at 9:05 AM, Yak said:

Having the same issue, had to roll back to 6.2.0. Can you describe in more detail how you got this to work?

Hey guys, this seems partially correct. the only thing is, that from what I see, it´s not necessary to add the environmental variables. it´s just necessary to add the sharing block.

I´ve created a script, which should do the work. update the container, then run the update script. thats it.
https://github.com/Nemuritor01/Unraid-Templates/blob/main/scripts/opencloud_v7_upgrade.sh

for new installations, no changes are necessary as the files get correctly created during first run.

55 minutes ago, Nemu said:

Hey guys, this seems partially correct. the only thing is, that from what I see, it´s not necessary to add the environmental variables. it´s just necessary to add the sharing block.

I´ve created a script, which should do the work. update the container, then run the update script. thats it.
https://github.com/Nemuritor01/Unraid-Templates/blob/main/scripts/opencloud_v7_upgrade.sh

for new installations, no changes are necessary as the files get correctly created during first run.

Worked a treat, thank you.