1 hour ago, Joloxx9 said:

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?

For basic Opencloud as file storage, you need just the open cloud container. This is pretty easy. Just use my open cloud template and remove all variables ports and stuff under show more settings.

If want collabora to work, you need all three containers. They also need to be on the same docker network. (My script cscript can create a docker network).

Wopi server is the "glue component" between open loud and collabora. So it's necessary.

The container boot order is 1. Opencloud 2. Collabora 3. Collaboration(wopi server).

With my script and templates, it's not that hard to set up. My script has a user section, you need to define your domains, folders, docker network, and if you want to install collabora. The script creates all folders and the correct files.

If you use pangolin, you shouldn't need another proxy. Just point your domains to the containers+ports.

If you install my collabora container keep an eye on the extra parameters under more settings. There are two places you need to enter your opencloud domain. It's a bit hidden, that's why I mention it.

Everything else should be straight forward.

Edited December 19, 2025Dec 19 by Nemu

2 hours ago, Nemu said:

For basic Opencloud as file storage, you need just the open cloud container. This is pretty easy. Just use my open cloud template and remove all variables ports and stuff under show more settings.

If want collabora to work, you need all three containers. They also need to be on the same docker network. (My script cscript can create a docker network).

Wopi server is the "glue component" between open loud and collabora. So it's necessary.

The container boot order is 1. Opencloud 2. Collabora 3. Collaboration(wopi server).

With my script and templates, it's not that hard to set up. My script has a user section, you need to define your domains, folders, docker network, and if you want to install collabora. The script creates all folders and the correct files.

If you use pangolin, you shouldn't need another proxy. Just point your domains to the containers+ports.

If you install my collabora container keep an eye on the extra parameters under more settings. There are two places you need to enter your opencloud domain. It's a bit hidden, that's why I mention it.

Everything else should be straight forward.

Thank you I will have a look in upcoming days, I have deployed opencloud already so I think I will wipe it and use your script to get everything working as it will be painful to do everything alone.

cant get this container to start

tried both available in the unraid store

similar issue in both

what is needed for this container to start and work

4 hours ago, charettepa said:

cant get this container to start

tried both available in the unraid store

similar issue in both

what is needed for this container to start and work

Try my template.

GitHub

GitHub - Nemuritor01/Opencloud-Unraid-Templates: Unraid t...

Unraid templates to install Opencloud with additional services as Collabora - Nemuritor01/Opencloud-Unraid-Templates

It's in the early stage and I'm still waiting for feedback, if this works for most people. If so, I will check to get it listed in the community store.

Before installing the container, use the pre-install script (it has a user section, you need to define your domains, volumes etc).

With this it should be straight forward. There is also a guide on my GitHub.

Edited December 21, 2025Dec 21 by Nemu
Missed a link

4 hours ago, Nemu said:

Try my template.

GitHub

GitHub - Nemuritor01/Opencloud-Unraid-Templates: Unraid t...

Unraid templates to install Opencloud with additional services as Collabora - Nemuritor01/Opencloud-Unraid-Templates

It's in the early stage and I'm still waiting for feedback, if this works for most people. If so, I will check to get it listed in the community store.

Before installing the container, use the pre-install script (it has a user section, you need to define your domains, volumes etc).

With this it should be straight forward. There is also a guide on my GitHub.

Thanks for your work, I did tried this few hours ago and after 30 min I dropped it. I will try again later once my sanity is back. Do I need need SWAG even if I have pangolin as reverse proxy?

Edited December 21, 2025Dec 21 by Joloxx9

38 minutes ago, Joloxx9 said:

Thanks for your work, I did tried this few hours ago and after 30 min I dropped it. I will try again later once my sanity is back. Do I need need SWAG even if I have pangolin as reverse proxy?

In general, it should be ok, if you just use pangolin.

1. Did you use my script? Have you changed the user settings in it?

2. Then check, if it has created the folders and the files - csp.yaml and banned-password-list.txt

3. Opencloud Container: Enter you password (IDM_ADMIN_PASSWORD), enter your opencloud domain with https in front: OC_URL https://opencloud.yourdomain.com then enter your collabora domain WITHOUT https in front: COLLABORA_DOMAIN collabora.yourdomain.com leave all other variables as is.

4. collabora container: enter your wopi server domain (collaboration container) in aliasgroup1 with port: https://wopi.yourdomain.com:443 change your password. Under more settings extra_params you need to enter 2 times your opencloud domain ( opencloud.yourdomain.com)

5. collaboration container (wopi server): Enter MICRO_REGISTRY_ADRESS: YourserverIP:9233 ; then under COLLABORATION_WOPI_SRC enter your wopi server domain with https in front: https://wopi.yourdomain.com, then under COLLABORATION_APP_ADDR enter your Collabora!!! domain with https in front: https://collabora.yourdomain.com ; under OC_URL enter your opencloud domain with https in front: https://opencloud.yourdomain.com ; under COLLABORATION_APP_ICON enter https://collabora.yourdomain.com/favicon.ico

6. leave the rest as is.

7. create your domains with pangolin opencloud to container port 9200, collabora to container port 9980 and collaboration container port 9300.

This should be it

one more info. If you made a mistake and started the container. You can not just edit the container variable and restart the container, as the open cloud.yaml won't get overwritten. So you always need to delete the open cloud.yaml under open cloud/config manually! That's important and one of the issues I had. So I always removed the complete containers without removing the images, deleted the folders and started from scratch.

Edited December 21, 2025Dec 21 by Nemu

1 hour ago, Nemu said:

In general, it should be ok, if you just use pangolin.

1. Did you use my script? Have you changed the user settings in it?

2. Then check, if it has crested the folders and the files - csp.yaml and banned-password-list.txt

3. Opencloud Container: Enter you password (IDM_ADMIN_PASSWORD), enter your opencloud domain with https in front: https://opencloud.yourdomain.com then enter your collabora domain WITHOUT https in front: collabora.yourdomain.com leave all other variables as is.

4. collabora container: enter your wopi server domain (collaboration container) in aliasgroup1 with port: https://wopi.yourdomain.com:443 change your password. Under more settings extra_params you need to enter 2 times your opencloud domain ( opencloud.yourdomain.com)

5. collaboration container (wopi server): Enter MICRO_REGISTRY_ADRESS: YourserverIP:9233 ; then under COLLABORATION_WOPI_SRC enter your wopi server domain with https in front: https://wopi.yourdomain.com, the under COLLABORATION_APP_ADDR enter your Collabora!!! domain with https in front: https://collabora.yourdomain.com ; under OC_URL enter your opencloud domain with https in front: https://opencloud.yourdomain.com ; under COLLABORATION_APP_ICON enter https://collabora.yourdomain.com/favicon.ico

6. leave the rest as is.

7. create your domains with pangolin opencloud to container port 9200, collabora to container port 9980 and collaboration container port 9300.

This should be it

one more info. If you made a mistake and started the container. You can not just edit the container variable and restart the container, as the open cloud.yaml won't get overwritten. So you always need to delete the open cloud.yaml under open cloud/config manually! That's important and one of the issues I had. So I always removed the complete containers without removing the images, deleted the folders and started from scratch.

Approach number 2:

Did step by step, do I have to run init in this version? If I do this should be in documentation.

Just now, Joloxx9 said:

Approach number 2:

Did step by step, do I have to run init in this version? If I do this should be in documentation.

Yes. My container has the the post args.

<PostArgs>-c "opencloud init || true; opencloud server"</PostArgs>

That's important, as without init, the container can't create the opencloud.yaml

Edited December 21, 2025Dec 21 by Nemu

Weird, it is blank but I can see it in code.

Just now, Joloxx9 said:

Weird, it is blank but I can see it in code.

Really weird. But this explains the failure. The opencloud.yaml has the jwt secret, which is synced with the wopi server.

Edited December 21, 2025Dec 21 by Nemu

4 minutes ago, Joloxx9 said:

I am literally following your steps. There was error with initial template but something is not clear in the description.

The first error is normal. That's what I wrote, that the opencloud.yaml gets created on first container start and can't be overwritten.

As mentioned. I always started from scratch to create the containers, when I made a mistake as it often caused issues, just overwrite, or delete the opencloud.yaml.

Second seems an issue with the proxy conf. Can you try to use https in pangolin instead of http. It's weird but I also have to use https in cloudflare instead of http.

Otherwisee I can have a more detailed look later.

PS. I've just tested with just cloudflare domains, all http and disabled swag. Works totally fine. So swag is not a must and it should also work with pangolin.

Edited December 21, 2025Dec 21 by Nemu

51 minutes ago, Nemu said:

The first error is normal. That's what I wrote, that the opencloud.yaml gets created on first container start and can't be overwritten.

As mentioned. I always started from scratch to create the containers, when I made a mistake as it often caused issues, just overwrite, or delete the opencloud.yaml.

Second seems an issue with the proxy conf. Can you try to use https in pangolin instead of http. It's weird but I also have to use https in cloudflare instead of http.

Otherwisee I can have a more detailed look later.

PS. I've just tested with just cloudflare domains, all http and disabled swag. Works totally fine. So swag is not a must and it should also work with pangolin.

it does not accept the login/password combination, no matter what I put as a password :)

I've just tested my config with just running domains cloudflare without swag. My cloud flare domains were http to each container, and it works. So it should also work with pangolin.

6 minutes ago, Joloxx9 said:

it does not accept the login/password combination, no matter what I put as a password :)

Seems you have used a banned password my friend ;)

Password admin is in the banned password txt. You also need to comply to the password rules.

At least 8 characters

At least 1 lowercase letter

At least 1 uppercase letter

At least 1 digit

At least 1 special character

NOT in the banned password list

If you use a new password. Delete the opencloud.yaml before ;)

1 minute ago, Nemu said:

I've just tested my config with just running domains cloudflare without swag. My cloud flare domains were http to each container, and it works. So it should also work with pangolin.

Seems you have used a banned password my friend ;)

Password admin is in the banned password txt. You also need to comply to the password rules.

At least 8 characters

At least 1 lowercase letter

At least 1 uppercase letter

At least 1 digit

At least 1 special character

NOT in the banned password list

If you use a new password. Delete the opencloud.yaml before ;)

Well I put admin because mine something like "&R7$Tyklo56" was not working.

I will try once again.

9 hours ago, Nemu said:

Try my template.

GitHub

GitHub - Nemuritor01/Opencloud-Unraid-Templates: Unraid t...

Unraid templates to install Opencloud with additional services as Collabora - Nemuritor01/Opencloud-Unraid-Templates

It's in the early stage and I'm still waiting for feedback, if this works for most people. If so, I will check to get it listed in the community store.

Before installing the container, use the pre-install script (it has a user section, you need to define your domains, volumes etc).

With this it should be straight forward. There is also a guide on my GitHub.

Sorry I am late to reply

thanks for this

I am fairly new to unraid

how does one use this template?

39 minutes ago, Nemu said:

I've just tested my config with just running domains cloudflare without swag. My cloud flare domains were http to each container, and it works. So it should also work with pangolin.

Seems you have used a banned password my friend ;)

Password admin is in the banned password txt. You also need to comply to the password rules.

At least 8 characters

At least 1 lowercase letter

At least 1 uppercase letter

At least 1 digit

At least 1 special character

NOT in the banned password list

If you use a new password. Delete the opencloud.yaml before ;)

Did fresh install as it was not accepting ANY password, now I am facing this:




I literally have no clue what is going with this thing, why is it so hard to set it up?

17 minutes ago, Joloxx9 said:

Did fresh install as it was not accepting ANY password, now I am facing this:




I literally have no clue what is going with this thing, why is it so hard to set it up?

That's a lot of info stuff. Can you access the UI?

18 minutes ago, Nemu said:

That's a lot of info stuff. Can you access the UI?

I have deployed a lot containers in my life, had some issues previously with some of them but this thing, I finally managed to do it and bum:

You know what is funny? That I had fully working instance of opencloud, but I was going to add collabra, and I tought that this will speed it up lol. I give up, not sure what is wrong, I am doing everything step by step and every time there is something broken.

3 minutes ago, Joloxx9 said:

I have deployed a lot containers in my life, had some issues previously with some of them but this thing, I finally managed to do it and bum:

You know what is funny? That I had fully working instance of opencloud, but I was going to add collabra, and I tought that this will speed it up lol. I give up, not sure what is wrong, I am doing everything step by step and every time there is something broken.

Yeah... It's a pain, especially the proxy stuff. But this is a good progress. In general the container works.

8 minutes ago, Joloxx9 said:

I have deployed a lot containers in my life, had some issues previously with some of them but this thing, I finally managed to do it and bum:

You know what is funny? That I had fully working instance of opencloud, but I was going to add collabra, and I tought that this will speed it up lol. I give up, not sure what is wrong, I am doing everything step by step and every time there is something broken.

Yeah. Guess how often I had to reinstall each container again and again.

But the container is running. Seems something with the reverse proxy. I'm not familiar with pangolin, how it handles the proxy stuff.

As I'm not familiar with pangolin, I've check with AI. This is the answer. Maybe it helps?

Key Differences & Required Configuration

For Pengolin (which uses Caddy instead of nginx), you need:

1. Check Your Pengolin/Caddy Configuration

Instead of the nginx .conf files, Pengolin uses Caddy's Caddyfile syntax. You need something like this for OpenCloud:

opencloud.yourdomain.com {

reverse_proxy opencloud:9200 {

header_up X-Forwarded-Proto {scheme}

header_up X-Forwarded-Host {host}

header_up X-Real-IP {remote}

}

# Disable buffering for SSE

flush_interval -1

}

2. Critical Headers for Authentication

The login failure is almost certainly because these headers aren't being passed:

X-Forwarded-Proto (must be "https")

X-Forwarded-Host (your domain)

X-Real-IP (client IP)

hey guys.

using the info i got here and other sites

i was able to get this particular mcreekmore to work

1. the password requirements

2. the proper setup of proxies

3. your proxy must NOT have block common exploits

i now have it running and connected with windows app

but onlyoffice and colabora dont seem to be present

did i do something wrong or is that separate

I think my issue is on the pangolin side at the moment.

46 minutes ago, Joloxx9 said:

I think my issue is on the pangolin side at the moment.

Yes. It seems so.

1 hour ago, charettepa said:

hey guys.

using the info i got here and other sites

i was able to get this particular mcreekmore to work

1. the password requirements

2. the proper setup of proxies

3. your proxy must NOT have block common exploits

i now have it running and connected with windows app

but onlyoffice and colabora dont seem to be present

did i do something wrong or is that separate

For collabora you need additional containers and variables. I believe, that the mcreekmore container is for basic Opencloud at the moment.

26 minutes ago, Nemu said:

Yes. It seems so.

Yup, there was something going on between Pangolin OIDC and opencloud, had to do some rules and voila:

6 minutes ago, Joloxx9 said:

Yup, there was something going on between Pangolin OIDC and opencloud, had to do some rules and voila:

Perfect. 👍🏻Collabora also working?