Cloudron Forum

ok. After manually installing netcat, cloudron-support --troubleshoot the same info as the WebUI. All good.

thank you for all your explanations

@James I used sudo because system told me I don't have permissions which / sudo which both tell me I have /opt/homebrew/bin/cloudron I updated / upgraded brew but it's still 5.14.7 No brew doctor errors. Tried to remove the brew version of cloudron but it is rejecting that. I will investigate Thank you for the pointers.

Hello @inibudi Currently, the Cloudron @vaultwarden app does not yet support OIDC/SSO. As stated above: @girish said in Cloudron documentation outdated? Bitwarden now supports SSO: thanks, I have created a task internally for @vladimir.d .

I enabled this en within seconds the log file was enormous, I asked ChatGPT to analyse it and here is it's observations: (too technical for me): Some observations after briefly enabling the MySQL general log (Cloudron v9) I enabled the MySQL general log only for a short time because of disk I/O concerns, but even within a few minutes a clear pattern showed up. What I’m seeing: A very high number of INSERT INTO session (...) and INSERT ... ON DUPLICATE KEY UPDATE These happen continuously and come from 172.18.0.1 As far as I understand, this IP is the Docker bridge gateway in Cloudron, so it likely represents multiple apps I temporarily disabled Matomo to rule that out, but disk I/O and session-related writes did not noticeably decrease, so it does not seem to be the main contributor. From the log it looks like: Multiple applications are storing sessions in MySQL Session rows are updated on almost every request This can generate a lot of InnoDB redo log and disk I/O, even with low traffic Nothing looks obviously broken, but I’m trying to understand whether this level of session write activity is: expected behavior in Cloudron v9 something that can be tuned or configured or if there are recommended best practices (e.g. Redis for sessions) Any guidance on how Cloudron expects apps to handle sessions, or how to reduce unnecessary MySQL write I/O, would be much appreciated. Thanks for looking into this.

Hello @sfeldkamp You can do this with the cloudron cli or the API. API example based on the Cloudron LAMP app: export ACCESS_TOKEN="YOUR_CLOUDRON_TOKEN" export CLOUDRON_DOMAIN="my.DOMAIN.TLD" curl "https://${CLOUDRON_DOMAIN}/api/v1/apps?access_token=${ACCESS_TOKEN}" \ -H 'content-type: application/json' \ --data-raw '{"appStoreId":"lamp.cloudronapp.php74@5.0.1","subdomain":"domain1","domain":"cloudron.dev","secondaryDomains":{},"aliasDomains":[{"domain": "cloudron.dev", "subdomain": "domain2"}, {"domain": "cloudron.dev", "subdomain": "*.wildcarddomain"}],"ports":{},"accessRestriction":null}' CLI example based on the Cloudron LAMP app: cloudron install --appstore-id "lamp.cloudronapp.php74@5.0.1" --location "domain1" --alias-domains "domain2,*.wildcarddomain" CLI example for a custom app: Note: I am using the yq tool to get the id and version from the CloudronManifest.json since this is how I also build the docker images for convenience. Info: You need to add "multiDomain": true, to the CloudronManifest.json to enable domain aliases, see: https://docs.cloudron.io/packaging/manifest/#multidomain cloudron install --location $(yq -r .id CloudronManifest.json) --image dr.cloudron.dev/$(yq -r .id CloudronManifest.json):$(yq -r .version CloudronManifest.json) --alias-domains "domain2,*.wildcarddomain"

@scooke said in Focus on Business Apps: One app for 11 bucks. Cloudron gives you unlimited apps for 16 bucks a month. You don't understand my situation. When I need a certain app, I need that app. I'm not a private user here. I represent a business. I'm not saying costs don't matter, but 11 bucks for one app would be ok, if that is the only option to get it. I haven't checked all the Cloudron alternatives so I cannot say what it will cost in the end. But it's not about costs – unless they're prohibitive or a competitor costs a lot less.

@eyecreate Thank you for this! I have lost a lot of time IRL with work and family stuff so someone else taking the mantle here is really helpful. I'll definitely be checking this out

Oooof Pydio Cells package fixed. Changed approach to use the provided browser configuration process (seems more reliable than doing it programmatically). What I like : nice UI functional desktop sync client (not yet tested) What I don't like : file names not exposed in the underlying app data storage (but this seems quite common in such apps) Not yet tested : API usage S3 bucket usage desktop sync client Deployment : My git repo : https://git.cloudron.io/timconsidine/cloudron-pydiocells Built Cloudron Docker image : tcmbp132021/cloudron-pydiocells:v1.0.0 Available as fast install on custom app installer : https://ccai.appx.uk and on custom app installer personal edition (remember to import the master catalogue)

Surely, the idea is to create an account per user, not per client. In that case, each user should be able to login on multiple clients using OIDC or app passwords, as appropriate to the client. If not, then OIDC is not a lot of use and a retrograde move from LDAP.

Hello @factord This looks like a copy-paste issue from Windows. \r in line 2 is a blank line, so a line break. When you copy and pasted, it pasted the line breaks windows style. Please describe how you have copy and pasted the code into the /app/data/fix_db.sh file.

This is how I use it currently, but I maintain the wireguard VPN myself, outside of cloudron, which is not the recommended way. I would LOVE for something like this to be available.

@robi That's the Cloudron CLI, not the CloudronManifest.json. I asked a follow up question though to clarify though, so thank you.

Hello @james, yes. I already use enterprise features such as API keys and workflows, so the standard system knows my key very well.

Welcome back to 2026! I wish you all a good new year and that all your plans and ideas with Cloudron (and beyond) will work out :)) Is anyone willing to create a meetup somewhere in Germany? What cities are you located in?

I will work on the translations in the coming weeks. Is anyone interested in helping or adding another Nordic language?