Cloudron Forum

I'm excited to see this in production!

I would really like to see this as well. The reason I don't use Cloudflare tunnels is privacy policy enables them to review all content that you use via a tunnel. That's really unfortunate.

Pangolin also recently received a grant from FUTO as well. I'd really like to see this one.

I guess a better title would be "Matrix Public Room List is Not Complete".

Man that helps a lot. Thank you so much. I wonder if we want to update the docs to add rooms/spaces via matrixrooms.info because of this. Either way, thank you so very much.

So, basically, these codes work:

Add a new key:

su - cloudron -c 'source /app/code/.venv/bin/activate; ltmanage keys --api-keys-db-path /app/data/db/api_keys.db add 120'

Show all created keys:
su - cloudron -c 'source /app/code/.venv/bin/activate; ltmanage keys --api-keys-db-path /app/data/db/api_keys.db'

But, the remove key doesn't seem to work for me (I don't understand the formatting) and it would be great to have a character set version as well such as from LibreTranslate: ltmanage keys add 120 --char-limit 5000

Okay, sorry for the rapid fire.

Rock on! This is perfect and super helpful.

According to folks on their forum, there's another step to lock down:

https://community.libretranslate.com/t/locking-down-api-key-on-self-hosted-through-cloudron/1767/2

We may need to update the docs here on cloudron:

To configure requirement for api key to use, set --req-limit to 0 and add the --api-keys flag. Requests made without a proper api key will be rejected.

I'd love to see this on cloudron to connect TrueNAS as a back up.

I setup Matrix and have added my admin user via this (I did edit the username for my instance but do not include here):

PGPASSWORD=${CLOUDRON_POSTGRESQL_PASSWORD} psql -h ${CLOUDRON_POSTGRESQL_HOST} -p ${CLOUDRON_POSTGRESQL_PORT} -U ${CLOUDRON_POSTGRESQL_USERNAME} -d ${CLOUDRON_POSTGRESQL_DATABASE} -c "UPDATE users SET admin=1 WHERE name='@myuser@mydomain.com'"

I setup federation by adding the on the bare domain on port 443 in the well known locations in Cloudron, and it appears to work when I go to federationtester.matrix.org.

I have updated the yaml by placing these two lines in the end:

# By default an instance cannot be added for room discovery in other instances. To enable this feature to make public rooms discoverable, add the following to the config file at /app/data/configs/homeserver.yaml:
allow_public_rooms_over_federation: true
#MSC1772: Matrix Spaces support can be enabled by editing /app/data/configs/homeserver.yaml using the File Manager and adding the following line: 
experimental_features: {spaces_enabled: true}

I have no identity server setup and don't know if I need one (please advise). I am trying to add some rooms back that I was a part of through my account on matrix.org (such as Linux Mint and Asahi Linux), but my search results are very limited. I see maybe 100 or so rooms on the public matrix.org listing.

I'm absolutely positive that this is user error, but how can I get access to the full list of public rooms available?

Public spaces is the same - I have one available to join:

Thanks in advance for any pointers on what I did wrong. Thanks

Please forgive me, but does anyone know if there is a way to enable 2FA on Postiz? I don't see anything in Cloudron documentation for this app. And, it appears that you can login without any form of 2FA (setup to let app determine users).

If I install a key, do I need to comment out the line below so that it is locked down to only users with api keys?

Hello,

I am new to this and wanted to ask a couple questions. I am planning on installing at Hetzner and using a domain I picked up through Cloudflare. There is no one-click install, but I am not sure that would be the best idea for me regardless to not know what's going on fully.

I understand this script is all I need to run on the latest version of Ubuntu LTS, which right now is 24.04.

wget https://cloudron.io/cloudron-setup
chmod +x ./cloudron-setup
./cloudron-setup

My question is twofold:

• Since my plan is to use Cloudron for my own company and in the future roll out to clients we have, is it wiser for me to go the route of a dedicated vCPU or a shared VCPU?
  
• Second, I want to make sure that I secure this as best as we can. Should I, or should I not, 1. disable the root user, 2. setup the non-root user and enable its keygen, 3. install Fail2Ban, and/or 4. install Crowdsec BEFORE I go through the installation as described with the wget command? Should I do this after I install Cloudron or does Cloudron do some of these items itself? Are any of these four steps here unnecessary?

Thank you for the help in advance. If there is anything that a NEW user should ask but I am missing here, please let me know where to look for insight. Cloudron seems like the best solution for me right now, but I just want to make sure I get the initial install done right so that I can focus on deploying the apps and not on the integrity of my initial installation.

Matt

Has anyone been able to integrate vikunja via n8n to kimai? That seems to be one of the avenues to solve the lack of a time tracking option with vikunja.

I'd love to have this as well. Plus 1

Thank you all so much. This is extremely helpful and will guide how I set up things. I appreciate better now that you can migrate very easily with Cloudron. So that part doesn't give me any reservations.

I didn't think of email and blacklists so thanks for pointing out a blindspot.

One more quick question. Do you recommend installing CrowdSec or not? Maybe it's overkill?

@nebulon it is more confusing this way. Is there a way to set it up so that once the server is rebooted, the notification stays, but the "reboot" button becomes a grayed out button that says "reboot completed". Then leave the notification as a form of a log, I would say.