starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-25 01:06:06 +03:00

[GH-ISSUE #11610] OpenCloud LXC Issues #2449

New issue

Closed

opened 2026-02-26 12:52:30 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 12:52:30 +03:00

Owner

Originally created by @summoningpixels on GitHub (Feb 6, 2026).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/11610

Originally assigned to: @vhsdream on GitHub.

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

📜 What is the name of the script you are using?

OpenCloud

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/opencloud.sh)"

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

pve-manager/9.1.5/80cf92a64bef6889 (running kernel: 6.17.4-2-pve)

📝 Provide a clear and concise description of the issue.

I'm on a fresh install of the OpenCloud LXC and encountered 3 issues;

When creating a new document, Collabora notifies you via an error tooltip that links to their server audit saying Your server is configured with insufficient hardware resources, which may lead to poor performance.

I assumed, per the linked Collabora documentation for this error that it's tied to the number of cpu threads. The script has a default of 2. Increasing it to 3 yields the same error, while increasing it to 4 makes the error disappear:

I configured all OpenCloud with Zoraxy as a reverse proxy. cloud.domain works as intended, collabora.domain returns OK, whereas wopi.domain returns a 404. Though my testing is limited (for now), everything else seems to be working fine in spite of the 404 error.
The script's webpage mentions the .env location as /opt/opencloud/opencloud.env for those wanting the optional OpenID integration, however the .env's path is actually /etc/opencloud/opencloud.env and should be either amended during the lxc's creation or on the website.

🔄 Steps to reproduce the issue.

Create or open an existing document through Collabora, notice the bottom error tooltip that links to the Server Audit.
Link wopi.domain to lxcIP:9300, then access the url and get a 404 error.
/opt/opencloud/opencloud.env doesn't exist on the script's lxc, it's actually placed in /etc/opencloud/opencloud.env

❌ Paste the full error output (if available).

🖼️ Additional context (optional).

No response

Originally created by @summoningpixels on GitHub (Feb 6, 2026). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/11610 Originally assigned to: @vhsdream on GitHub. ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 What is the name of the script you are using? OpenCloud ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/opencloud.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? pve-manager/9.1.5/80cf92a64bef6889 (running kernel: 6.17.4-2-pve) ### 📝 Provide a clear and concise description of the issue. I'm on a fresh install of the OpenCloud LXC and encountered 3 issues; 1. When creating a new document, Collabora notifies you via an error tooltip that links to their server audit saying `Your server is configured with insufficient hardware resources, which may lead to poor performance`. <img width="631" height="435" alt="Image" src="https://github.com/user-attachments/assets/5cb17088-f00e-4774-b752-3389a503075d" /> I assumed, [per the linked Collabora documentation](https://sdk.collaboraonline.com/docs/installation/Configuration.html#performance) for this error that it's tied to the number of cpu threads. The script has a default of 2. Increasing it to 3 yields the same error, while increasing it to 4 makes the error disappear: <img width="631" height="415" alt="Image" src="https://github.com/user-attachments/assets/25e37812-c737-4c92-b5e7-b30a2ee8a461" /> 2. I configured all OpenCloud with Zoraxy as a reverse proxy. `cloud.domain` works as intended, `collabora.domain` returns OK, whereas `wopi.domain` returns a 404. Though my testing is limited (for now), everything else seems to be working fine in spite of the 404 error. 3. [The script's webpage](https://community-scripts.github.io/ProxmoxVE/scripts?id=opencloud) mentions the .env location as `/opt/opencloud/opencloud.env` for those wanting the optional OpenID integration, however the .env's path is actually `/etc/opencloud/opencloud.env` and should be either amended during the lxc's creation or on the website. <img width="1021" height="86" alt="Image" src="https://github.com/user-attachments/assets/409da9e9-15ce-4a5f-a160-dc0eb5a38010" /> ### 🔄 Steps to reproduce the issue. 1. Create or open an existing document through Collabora, notice the bottom error tooltip that links to the Server Audit. 2. Link `wopi.domain` to `lxcIP:9300`, then access the url and get a 404 error. 3. `/opt/opencloud/opencloud.env` doesn't exist on the script's lxc, it's actually placed in `/etc/opencloud/opencloud.env` ### ❌ Paste the full error output (if available). - ### 🖼️ Additional context (optional). _No response_

kerem

2026-02-26 12:52:30 +03:00

closed this issue
added the
json
label

kerem commented

2026-02-26 12:52:30 +03:00

Author

Owner

@vhsdream commented on GitHub (Feb 6, 2026):

Hi @summoningpixels Thanks for the feedback!

I don't consider the insufficient resources warning to be a bug or issue. People are free to adjust container resources as desired.
The Wopi domain isn't intended to be directly reachable via a web browser. The Collabora server uses the Wopi endpoint to interact with the documents stored in Opencloud.
Thanks for pointing out the oversights with the website JSON. I'll make a PR to fix them.

@vhsdream commented on GitHub (Feb 6, 2026): Hi @summoningpixels Thanks for the feedback! 1. I don't consider the insufficient resources warning to be a bug or issue. People are free to adjust container resources as desired. 2. The Wopi domain isn't intended to be directly reachable via a web browser. The Collabora server uses the Wopi endpoint to interact with the documents stored in Opencloud. 3. Thanks for pointing out the oversights with the website JSON. I'll make a PR to fix them.

kerem commented

2026-02-26 12:52:30 +03:00

Author

Owner

@summoningpixels commented on GitHub (Feb 6, 2026):

Hi @summoningpixels Thanks for the feedback!

1. I don't consider the insufficient resources warning to be a bug or issue. People are free to adjust container resources as desired.

2. The Wopi domain isn't intended to be directly reachable via a web browser. The Collabora server uses the Wopi endpoint to interact with the documents stored in Opencloud.

3. Thanks for pointing out the oversights with the website JSON. I'll make a PR to fix them.

No worries and thanks for all the work put into making this script work!

While true, I'd just say that it's kind of bad UX if the default installation has an error nag each time you open a document (which might happen often for those installing this). Perhaps adjusting Collabora's per_document.max_concurrency to 2 to match the lxc's default config would be a solution? Otherwise, it might just be worth mentioning the website that the error will happen unless you increase your CPU allocation in Proxmox to 4 for this lxc.
Perfect!
Awesome, thanks! <3

@summoningpixels commented on GitHub (Feb 6, 2026): > Hi [@summoningpixels](https://github.com/summoningpixels) Thanks for the feedback! > > 1. I don't consider the insufficient resources warning to be a bug or issue. People are free to adjust container resources as desired. > > 2. The Wopi domain isn't intended to be directly reachable via a web browser. The Collabora server uses the Wopi endpoint to interact with the documents stored in Opencloud. > > 3. Thanks for pointing out the oversights with the website JSON. I'll make a PR to fix them. No worries and thanks for all the work put into making this script work! 1. While true, I'd just say that it's kind of bad UX if the default installation has an error nag each time you open a document (which might happen often for those installing this). Perhaps adjusting Collabora's `per_document.max_concurrency` to `2` to match the lxc's default config would be a solution? Otherwise, it might just be worth mentioning the website that the error will happen unless you increase your CPU allocation in Proxmox to 4 for this lxc. 2. Perfect! 3. Awesome, thanks! <3

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ProxmoxVE#2449

No description provided.

Rows
Columns