[Script request] opencloud

[dancgn]

Application Name

opencloud

Website

https://docs.opencloud.eu/de/

Description

Opencloud is a new (german) self hosted, simple and easy cloud like Seafile.
I tried it bare metal, docker and docker-compose on a ubuntu and a debian lxc, unfortunately nothing works.

I guess this is a nice one for this community and "easy" for you guys.

Due Diligence

• I have searched existing scripts and found no duplicates.
• I have searched existing discussions and found no duplicate requests.

[kylepyke]

I tried it bare metal, docker and docker-compose on a ubuntu and a debian lxc, unfortunately nothing works.

I had almost the same experience 😂. I was able to get it running with bare metal in an ubuntu LXC– you need an updated version of GO (>=1.24). You don't have access to any of the apps that way, which I see as one of the most desirable features. Would love to see a fully featured LXC docker version.

[vmhq]

Me too. Same experience :(

[MatKlein]

Same here. 😂

[ffuhrnew]

They are starting with opencloud in germany with a fresh and clean open source community driven alternative cloud solution.
As they are in progress there are a few docs available. Bare metal is not supported. But they have a complete working docker solution with traefik inside. You find a step by step guide under: https://docs.opencloud.eu/docs/admin/getting-started/docker/docker-compose
As a possible solution for the central .env file you could do everything according to the guide but in the end you create one individual docker compose file (stack) with this:
You can generate a single compose file from your desired opencloud_full config.

Configure your .env
run docker compose config > output.yml
You will get a single compose file
<you find this suggestion under -->
https://github.com/orgs/opencloud-eu/discussions/533#discussioncomment-12730366

[dancgn]

Using subdomains? eg:

* opencloud.mydomain.com

* collabora..mydomain.com

* onlyoffice.mydomain.com

etc.

Sorry for the dumb question, but they didn't need to set in my caddy-container, because it make everything by himself with traefik locally on the maschine?

[kylepyke]

Sorry, I don't understand your question.

[dancgn]

Sorry, I don't understand your question.
English isn't my main language, sorry. Try to translate it.

I’m trying to understand it. I have a Proxmox container running Caddy as a reverse proxy. There’s essentially one domain exposed to the “evil” internet. The individual subdomains don’t need to be configured in Caddy, since they’re only needed locally within the OpenCloud container itself. Basically just internal, managed by Traefik. I hope that made sense? I’m just going to give it a try now.

[kylepyke]

This is where the limit of my knowledge is. I use Pangolin instead of Caddy for exposing services to the net. Sorry, wish I could help more!

[dancgn]

No Problem, I'll try by myself.

Pangolin is a nice piece of software.

[FinFox1]

Well, i have also tried to install this one on bare-metal from this doc: https://docs.opencloud.eu/docs/admin/getting-started/other/bare-metal , but failed as you guys. I have attached the errors i am getting... Well, OpenCloud is a nice alternative to NextCloud, so i would love to use this bare-metal in a LXC.

When trying to install this on the latest Debian 12 version, i got theses errors:

When installing this on Ubuntu 24.04 as recommend, i got these errors:

Well, maybe someone knows a solution for this, but a perfect working script for LXC would be nice.

[tremor021]

ummm, https instead of http?

[FinFox1]

i tried both, http and https. With https i got these errors... http doesnt work.

[dancgn]

The problem is, that the bare-metal and the small docker-compose are the same.

I "want" the complete package.

[Patrick010]

Is this not the same as Owncloud?

[kylepyke]

No. It’s a project which some of the own loud devs split off.

[Patrick010]

That's Nextcloud

[kylepyke]

No. Owncloud split off from NextCloud. Open cloud split off from OwnCloud.

[Patrick010]

For those with the same question: https://www.youtube.com/watch?v=Ud9FEmNOgLs

[vhsdream]

I like a challenge, so I think I'm going to take a look at this...

[kylepyke]

🙌🙌

[tremor021]

Gotta love this @vhsdream

[ffuhrnew]

right mindset. if you want to get support—> contact meFriedrich FuhrAm 11.06.2025 um 06:07 schrieb Chris ***@***.***>: I like a challenge, so I think I'm going to take a look at this... —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[vhsdream]

Update

What Works

• OpenCloud basic: your basic file upload, management and sync
• Collabora: collaboratively create and edit Microsoft Word, Excel, PowerPoint files, as well as ODT, ODP and ODS files
• Install additional apps from the App Store
  • in the screenshot you can see the External Sites app - I added Homepage and my NAS to the App Switcher
• Email Notifications
• Radicale integration for CalDAV and CardDAV (not included - requires your own install)
• OpenID via web (currently Authelia and PocketID have been tested; have not tested the desktop app or mobile apps yet)

Next up

• Full text search with Apache Tika - will require your own Tika LXC, like Radicale
• Confirming that it's possible to use NFS/SMB that's bind-mounted in the LXC as storage

Why this all works

I got this all to work because I did the work of ensuring all OpenCloud-related services have valid TLS certificates. Not only that, but a working Content Security Policy is required. Luckily that is configurable via yaml file, included in the installation (csp.yaml).

• To get OpenID to work requires some additions to the CSP file.
• Embedding external sites also requires CSP edits.
• For the optional Radicale integration, after some experimenting I found that if you have an existing Radicale install with existing accounts, OpenCloud will not 'see' those and will instead create new ones, even if using the same username. Not a big problem, but FYI. Getting the integration to work also requires you to change your Radicale config to use http_x_remote_user as auth instead of other methods.

Feedback wanted

Currently, the install script prompts the end user (as close to the beginning of the installation as possible) to input the FQDNs for OpenCloud, Collabora, and the WOPI server (which acts as the bridge between OpenCloud and Collabora), before proceeding to install everything.

I'm wondering if the Collabora installation should be optional, if there are folks out there who might only want the barebones version of OpenCloud installed and nothing else. What do y'all think?

(As a small aside, I see a new OnlyOffice LXC in the works, and am now wondering if I should make a separate LXC for Collabora as well?)

If I get Apache Tika working, that for sure is going to be optional, so it's yet another prompt!

For Radicale, you just need to rename proxy.yaml.bak to proxy.yaml so there will be no prompt.

[dancgn]

It seems that I'm the only stupid person here...how? Can't find the script, a link, or whatever. So I can give you a feedback! Thanks!

[Patrick010]

This time it's not you ;)

The script is on the dev github; https://github.com/community-scripts/ProxmoxVED/blob/main/install/opencloud-install.sh

or

https://community-scripts.github.io/ProxmoxVED/

[vhsdream]

Well, the feedback I asked for is more about whether Collabora should be installed by default, or if you should have a choice in the matter; the script is not yet ready for release or even for testing.

Another thing I should have mentioned is that I'm using Caddy as my reverse proxy/TLS, and the configuration of OpenCloud/Collabora is geared towards that. I have a feeling that if you're using something else then there will be more manual configuration required.

[josecarre]

Well, the feedback I asked for is more about whether Collabora should be installed by default, or if you should have a choice in the matter; the script is not yet ready for release or even for testing.

Another thing I should have mentioned is that I'm using Caddy as my reverse proxy/TLS, and the configuration of OpenCloud/Collabora is geared towards that. I have a feeling that if you're using something else then there will be more manual configuration required.

Not an experienced opencloud user but i guess there will be people only interested in the "dropbox/gdrive alternative", so i 'd say it will be beneficial to make optional non mandatory components (like collabora and wopi?)

[vhsdream]

Update: Apache Tika will not be installed by default, nor will there be a prompt; instead, you'll need your own Apache Tika LXC and then uncomment some lines in opencloud.env.

[tremor021]

@vhsdream If optional components can be installed at a later date, you can put a whiptail menu in the updater script which users can use to install those.

In base install you should put whatever feels like appropriate thing to be in it. If that includes all components, then you should include all. if not, then just give option to install them either at install time or via update function. You have a example at:
https://github.com/community-scripts/ProxmoxVE/blob/main/ct/cronicle.sh

[vhsdream]

@tremor021 Thanks for the example!

I'm currently at a roadblock with figuring out how to have working external (bind-mounted) storage, since I assume most people would prefer to store files etc etc on a NAS, rather than in the LXC. It's currently not supported since CIFS and NFS are not POSIX filesystems.

It could be that my mount options on my host are insufficient. The issue is documented more in the Dev repo issue.

I have a couple more ideas but haven't had the time to fully conceptualize and then put into testing.

[ffuhrnew]

Thanks for your detailed information. if you use the opencloud-compose repo also external proxies are configurable. I have a question regarding the script… Where ca i find it to use/collaborate/test it?Friedrich FuhrAm 18.06.2025 um 11:43 schrieb Patrick ***@***.***>: This time it's not you ;) The script is on the dev github; https://github.com/community-scripts/ProxmoxVED/blob/main/install/opencloud-install.sh —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[coolduke666]

script is gone - wher do I find the latest version of the script? still in development?

[ffuhrnew]

To answer your question: i think that collabora embedded in the opencloud „frame“ is a very useful feature. compared to seafile,  nextcloud or owncloud it is good to have opencloud as a free/opensource alternative! I also use caddy and in connection with the opencloud-compose repo it shall be „easy“ to build a docker compose stack with „docker compose config > stack.yml after getting all answrrs regarding the elements an content that shall be installed   - i dontknow how to support you in coding the script. but i would be pleased to help. Friedrich FuhrAm 18.06.2025 um 13:42 schrieb Chris ***@***.***>: Well, the feedback I asked for is more about whether Collabora should be installed by default, or if you should have a choice in the matter; the script is not yet ready for release or even for testing. Another thing I should have mentioned is that I'm using Caddy as my reverse proxy/TLS, and the configuration of OpenCloud/Collabora is geared towards that. I have a feeling that if you're using something else then there will be more manual configuration required. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[wouldntyouknow]

I don't know how many people are like me, but I'm not a fan of Collabora, and would use OnlyOffice instead anyway...

[dancgn]

Honestly I would use it. At this moment I'm hosting Onlyoffice by myself.

[end0lin]

Regarding required TLS certificates: Would it be possible to auto integrate/generate let's encrypt certificates optionally during install?

[ccoles146]

By default OpenCloud would use Traeffik with let’s encrypt.

[ccoles146]

It's working as of today really easily. I'm using Docker LXC as found in the Helper-Scripts. I use the docker compose plugin. I have written a Gist about my setup but it's not yet public as it's just my notes for future reference but I can make it public if anyone's interested. It looks like they may include caddy in a future update, but currently I'm using my own Caddy LXC and Cloudflare tunnel.

[Stooovie]

Any progress on this? I can't deploy this by myself, I tried ;)

[ccoles146]

I followed this guide originally. It is in German but easy enough to understand or use a translate tool.
https://forums.unraid.net/topic/193380-opencloud-goes-lxc-container/
If you use the Community Docker container script then you can skip all the docker stuff, but make sure you select the option to install Docker Compose v2 when the script asks you. You probably don't need the reverse proxy stuff, if you have Caddy then I can share my config, if you have Nginx you can copy the config in the tutorial.
So basically:

• Install Docker LXC including Compose using community script
• Start at step 4. in the provided tutorial
• Clone the repository as per step 5. but you may need to install Git first.
• Create you .env file as per the example, or follow the Opencloud instructions.
• Modify your reverse proxy (if you have one) accordingly
• Create DNS records and wait for them to propagate
• Bring containers up

[Stooovie]

Thank you. I probably stumbled on the reverse proxy. I run NPM, had no issues running everything else through it including Nextcloud with Office, but this one I couldn't get to work. Then I tried the official documentation and docker compose which uses built-in Traefik, same result. The super convoluted docker compose doesn't help either.

I'll try your link, thanks again.

[vhsdream]

The day has finally come. The OpenCloud LXC is here.

[mscipio]

I have wasted most of my day trying to have this up and running first using just cloudflare tunnels, then adding a layer of nginx and nothing seems to be able to expose the opencloud lxc to the domain I set up to use for it. the setup instructions for the lxc has to be missing something crucial (at least to me). Or I am really dumb. Or both.

[wouldntyouknow]

I have wasted most of my day trying to have this up and running first using just cloudflare tunnels, then adding a layer of nginx and nothing seems to be able to expose the opencloud lxc to the domain I set up to use for it. the setup instructions for the lxc has to be missing something crucial (at least to me). Or I am really dumb. Or both.

Just added opencloud to local dns and nginx like any other resource really, and it worked, no custom stuff - port is 9200. Where I got stuck was collabora, 502 no matter what. The LXC is set up correctly so there is that, other stuff is out of scope for community scripts...

[ffuhrnew]

Good Morning: Here is a suggestion for you.
Reverse Proxy
Before you deploy opencloud lxc you install a reverse proxy of your choice on a system you control. Perhaps you try out zoraxy or caddy. With zoraxy you can set 3 crucial rules via the gui. In caddy you need to write 3 lines in the Caddyfile. You can use the helper scripts to install one of them.
TailScale
I suggest another step before you deploy opencloud at all. Install tailscale in the system that runs your reverse proxy. There is a helper script for installing tailscale in lxcs also. Use it!
Register FQDN
After those prelimanary steps you register any fqdn wherever you want. As i understand you also use cloudflare ... great!
Cloudflare DNS
After you registered your FQDN you change the dns entries to the cloudflare#s. In cloudflare you set a wildcard setting that points to the TAILSCALE ip address of your reverse proxy. Use no tunnels, use no cloudflare proxy!
Technitium DNS (if you are willing to do it!)
If you are really interested you can install an additional local nameserver like technitium and make a full dns entry for your FQDN also with a wildcard that points ... to the TAILSCALE Ip address of your reverse proxy and set a local dns management entry in tailscale that points to your local nameserver. For technitium there also is a helper script available.
Make reverse proxy settings
Reserve a local ip on your proxmox host for opencloud. Point the reverse proxy entries to this ip address with the following ports...
opencloud.FQDN --> 9200
collabora.FQDN --> 9980
wopi.FQDN --> 9300

NOW .... you install opencloud via the helper script and choose the local ip address and the exact names you set in the reverse proxy. https://community-scripts.github.io/ProxmoxVE/scripts?id=opencloud
Check
Connect with your tailscale vpn --> type: https://opencloud.FQDN login with admin and the credentials that were created. That´s it...

CAVE
You need to have the cloudflare apikey to enable caddy or zoraxy to obtain an renew your ssl certs. If you need addditional support on this topic ... just tell me.
You´ll have no openid and no radicale ... they have to be installed and configured seperately. But that´s another topic.

[ccoles146]

Troubleshooting can be a bit tricky. You should try to get it running internally first. How I have it set up Internet <--> Cloudflare Tunnel <--> Caddy <--> PiHole <--> OpenCloud
But internally you can go direct. In caddy I have opencloud.local and opencloud.domain.com. And in PiHole I have both, although you don't need pihole but can use hosts file instead. opencloud.domain.com should resolve to Caddy and opencloud.local should resolve to the opencloud container. If you need a certificate for HTTPS then Caddy will get this for you, and if you're using Cloudflare then you will need to install the Caddy with cloudflare plugin. So yes, it can get a bit complicated. To be honest I had a problem with a certificate expiring recently. And it turned out to be a mismatch in variable name in the Caddy config. I just installed an AI CLI on a container, gave it SSH access to Cloudflare, Caddy, Opencloud and said figure out the problem. It solved it in 5 minutes.

[Patrick010]

Interesting troubleshooting technique. Care to elaborate? What AI container did you install and how did you make it solve the issue?

[ccoles146]

Obviously slighty off topic... but: It's up to you where/how you install it. But I used the Community Script to install an unprivileged Debian LXC. Then I installed Claude Code, but you could also install Gemini CLI or your favorite one. It's usually a single command to have it installed. Then a single command to run it. But you should probably also create a user in the LXC - could call the user claude or whatever and install the AI tool as this user. Because to give it SSH access it will try to use the same user. Therefore go to all the containers you want it to access and create the same user. I created public/private keys and copied the public keys to the authorized_keys file on each of the containers. You need to configure sudo to allow necessary tools to run without password for this user. If you see that it tries to do something unexpected then ask the AI what it wants to do and why it can't do it, then you either run the command yourself or add it to the sudo config. Basically it cannot enter a password.

I've quickly written a gist to explain how to configure SSH for this:
my gist

I hope that helps.

[Patrick010]

Obviously slighty off topic...

[...]

I hope that helps.

Not really lol. I have never done this, no idea how to install AI CLI in a container and have it solve problems. Can you point me to docs or a howto? What prompt did you use for claude? I usually just go to the Grok or whater website and paste in errorlogs. Your solution sounds much easier, in such a sense that I dont have to copy paste anything and have AI figure it out himself.

[dancgn]

I installed it by myself with my Caddy included.

It runs stable with docker compose.

[tremor021]

Thank you for reporting something that has nothing to do with our script...