Cloudron Forum

Thanks for raising this question, @jdaviescoates.

I am personally not sure open-sourcing is critical here, as I think the first beneficiaries would be big cloud platforms (AWS, etc) that would then be able to host it and cut out any income for the developers. The current source available arrangement strikes me as probably necessary and appropriate.

I'm increasingly convinced that OSS as such is broken as a means of protecting against corporate exploitation, and it should not be celebrated as an end in itself. Based on my conversations with @girish, I think the single most important fact about Cloudron is that the company is bootstrapping (based on our subscription fees) and not seeking an exit. As long as that's the case, I think the community should support their self-defense through licensing.

Rather than fixating on licensing, it might be more relevant to all of us to discuss the possibility of an "exit to community" for Cloudron, in which ultimately the company we pay into becomes owned by—and accountable to—the people who rely on it. This could help ensure that the company we're paying into, and that is stewarding the code we depend on, doesn't get captured by forces beyond our control.

Given that Lemmy is taking off due to the Reddit issues, it seems like it would be very worthwhile for Cloudron to support it.

https://the-federation.info/platform/73

Using 172.18.0.0/16 worked for me on the WOPI whitelist when using built-in CODE server.

@robi Thanks—yes, I uninstalled it.

A friend just told me about Start9, which makes both hardware and an OS for self-hosting:

https://start9.com/
https://github.com/Start9Labs/start-os

Thank you! The Site Logo block did the trick. Thanks, @girish!

Wordpress has gotten so complex!

Yes, that worked for me! That seems strange, but it works.

Hugely exciting. Thank you!

@3wordchant This is really exciting. Thank you for sharing this project!

@girish Thanks so much for this! Just what I needed. I'm working on creating an example repo that I can use for future. I think I fully de-cloudron-ed it... Am I right to leave in .gitlab-ci.yml this part?

default:
image: cloudron/docs-ci@sha256:4a63ad48a6fbbd168828769b0d796b511d09d173ab5dd64368338997164aa4ab

Here's the repo: https://gitlab.com/medlabboulder/docs

Let me know if there's anything else I should do. But for now it deploys!

I am using Cloudron to manage a university class with 250+ students. I wonder if there is a way to easily add all the students to a specific group, without having to add them manually one by one. For instance, can I:

• Send them a magic link that they can use to create a new account in a given group?
• Import them via a csv file or the like?

Thanks for your help.

I hope we can get this added! Minetest is now called Luanti, and it is available as a Flatpack if that helps: https://flathub.org/apps/org.luanti.luanti

Thanks all! It seems to have worked smoothly.

On this and other apps where Cloudron login is required, is there a way to remove the app's native login fields to avoid confusing users?

Hi friends—is there anyway to deploy Node.js on the LAMP server? or a recommended alternative approach?

Amazing—this is a huge help @andreasdueren! It really improves the user experience. I'd love to see this kind of direct login option on more Cloudron apps, without the confusion of multiple options. Maybe this should be added to the official docs?

I'm having a strange experience when using Listmonk (which in general I love!). The number of recorded views on my campaigns has been significantly declining. I can't figure out why this might be (other than lousy content?). Can anyone think of a way I could diagnose this issue?

I'm having trouble enabling my users to access Loomio. For now, at least, the goal is for all Cloudron users to be able to log in. Here is my env.sh:

And the Cloudron Access Control:

I was able to create an initial account. I'm the Cloudron admin account. But when a less-privileged account tries, here's what happens. They click the key button here:

Then log into Cloudron if they haven't yet. Then they get this:

I try Create Account, and the next screen is this:

I then enter a name, hit enter, and get this:

The logs look like this:

ep 09 13:59:23 [09/Sep/2025:19:59:23 +0000] 172.18.0.1 "GET /socket.io/?channel_token=0a44509556dc6849817ae75c99dc27bb&EIO=4&transport=websocket&sid=DUSj2M0mfdpeHoplAAAG HTTP/1.1" "Mozilla/5.0 (X11; Linux x86_64; rv:142.0) Gecko/20100101 Firefox/142.0" 101 343 "-" 338.888 338.888
Sep 09 13:59:27 I, [2025-09-09T19:59:27.053758 #89] INFO -- : source=rack-timeout id=a9a67a5f-b092-4cc6-871a-507461756d07 wait=3ms timeout=15000ms state=ready
Sep 09 13:59:27 I, [2025-09-09T19:59:27.054568 #89] INFO -- : [a9a67a5f-b092-4cc6-871a-507461756d07] Started POST "/api/v1/registrations" for 2601:280:4681:7f50:d03e:b131:c42b:9dbd at 2025-09-09 19:59:27 +0000
Sep 09 13:59:27 I, [2025-09-09T19:59:27.061332 #89] INFO -- : [a9a67a5f-b092-4cc6-871a-507461756d07] Processing by Api::V1::RegistrationsController#create as JSON
Sep 09 13:59:27 I, [2025-09-09T19:59:27.061437 #89] INFO -- : [a9a67a5f-b092-4cc6-871a-507461756d07] Parameters: {"user" => {"name" => "test", "email" => "[FILTERED]"}, "registration" => {"user" => {"name" => "test", "email" => "[FILTERED]"}}}
Sep 09 13:59:27 I, [2025-09-09T19:59:27.097082 #89] INFO -- : [a9a67a5f-b092-4cc6-871a-507461756d07] Filter chain halted as :permission_check rendered or redirected
Sep 09 13:59:27 I, [2025-09-09T19:59:27.098055 #89] INFO -- : [a9a67a5f-b092-4cc6-871a-507461756d07] Completed 422 Unprocessable Entity in 36ms (Views: 0.2ms | ActiveRecord: 0.0ms (0 queries, 0 cached) | GC: 23.6ms)
Sep 09 13:59:27 I, [2025-09-09T19:59:27.099929 #89] INFO -- : [a9a67a5f-b092-4cc6-871a-507461756d07] source=rack-timeout id=a9a67a5f-b092-4cc6-871a-507461756d07 wait=3ms timeout=15000ms service=46ms state=completed
Sep 09 13:59:27 [09/Sep/2025:19:59:27 +0000] 172.18.0.1 "POST /api/v1/registrations HTTP/1.1" "Mozilla/5.0 (X11; Linux x86_64; rv:142.0) Gecko/20100101 Firefox/142.0" 422 1074 "https://loomio.medlab.host/dashboard" 0.049 0.049
Sep 09 13:59:30 [09/Sep/2025:19:59:30 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 203 "-" 0.004 0.004
Sep 09 13:59:32 I, [2025-09-09T19:59:32.775609 #81] INFO -- : source=rack-timeout id=de58afb4-baea-43de-bed7-3b260013092f wait=2ms timeout=15000ms state=ready
Sep 09 13:59:32 I, [2025-09-09T19:59:32.776522 #81] INFO -- : [de58afb4-baea-43de-bed7-3b260013092f] Started GET "/api/v1/boot/version?version=3.0.5&release=1757100919&now=1757447973262" for 128.138.65.206 at 2025-09-09 19:59:32 +0000
Sep 09 13:59:32 I, [2025-09-09T19:59:32.778088 #81] INFO -- : [de58afb4-baea-43de-bed7-3b260013092f] Processing by Api::V1::BootController#version as JSON
Sep 09 13:59:32 I, [2025-09-09T19:59:32.778625 #81] INFO -- : [de58afb4-baea-43de-bed7-3b260013092f] Parameters: {"version" => "3.0.5", "release" => "1757100919", "now" => "1757447973262", "boot" => {}}
Sep 09 13:59:32 I, [2025-09-09T19:59:32.782954 #81] INFO -- : [de58afb4-baea-43de-bed7-3b260013092f] Completed 200 OK in 4ms (Views: 0.1ms | ActiveRecord: 0.0ms (0 queries, 0 cached) | GC: 0.8ms)
Sep 09 13:59:32 I, [2025-09-09T19:59:32.783555 #81] INFO -- : [de58afb4-baea-43de-bed7-3b260013092f] source=rack-timeout id=de58afb4-baea-43de-bed7-3b260013092f wait=2ms timeout=15000ms service=8ms state=completed
Sep 09 13:59:32 [09/Sep/2025:19:59:32 +0000] 172.18.0.1 "GET /api/v1/boot/version?version=3.0.5&release=1757100919&now=1757447973262 HTTP/1.1" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36" 200 1237 "https://loomio.medlab.host/dashboard" 0.010 0.010
Sep 09 13:59:40 [09/Sep/2025:19:59:40 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 203 "-" 0.004 0.004

Any thoughts on why this Cloudron user can't log in on Loomio?

Thanks in advance, and thank you for supporting this excellent app.

Following this thread I raised the timeout period and got at least some promising results. I haven't tested at large scale. But I'm curious if others have any best practices suggestions for these settings.

Analytics are still not loading, even with memory raised on the db and the app.

@james good question:) Yes, I did, multiple times.

@ntnsndr Update: I just created a test campaign for 500 dummy users, and it appears to be working normally, arriving in my x+[1-500]@gmail.com inbox within about 30 minutes of initiating the campaign. In order to achieve this, I did the following in Cloudron:

• Raised Listmonk memory limit to 512
• Raised postgresql memory limit to 2 GB

And in Listmonk SMTP settings:

• Max connections to 25
• Idle timeout to 2m, Wait timeout to 5m

I am still getting the "AxiosError: Network Error" on any analytics page on Listmonk.

Note that in the past I have been able to send campaigns to large lists without changing any of these default settings, but my server has been under increased load lately.

I would appreciate any further guidance on best practices from @girish or anyone else. Thanks!

Update: two days later, this setup did NOT work for my 900 person email list. I got an even lower view count than before, with more errors.