Cloudron Forum

Great catch! This is now fixed with https://git.cloudron.io/platform/box/-/commit/d97c60832344fff7e9bd7d02cb978e0313c4862f

This path does not exist in community version of Mattermost System Console > Compliance > Data Retention Policies Looks like it is only for paying customers. [image: 1767793198537-b45f28e2-f500-457a-afa3-52fdfc91c85a-image-resized.png]

We used to have that actually, but given that apps which use LDAP were affected by this, we lifted those. By now the situation has changed quite a bit with most apps now being on OpenID, we have to revisit this. Regarding the roadmap, we are looking into things for v9.1 and will open a thread here to discuss those items soon. We do take this forum section into account, which is why it exists, so if feature requests have some traction by the community, they are more likely to be picked. So bumping threads and revisiting discussions here is a crude but useful way to signal for us.

I have never seen that failing, unless something is wrong with the ssh connection itself, but we really have to decode the stderr buffer (a fix we have for the next cloudron version to make that readable) to get a better understanding why it fails. For the curious people https://git.cloudron.io/platform/box/-/commit/b89aa4488cef24b68e23fdcafdf7773d6ae9e762 would be that change.

Cross-posting from https://forum.cloudron.io/post/118075 Making progress on packaging Seafile for Cloudron

@crazybrad yes, I checked, they are still offering PRO for small deployments - still needs a licence but zero-cost for up to 3 [image: 1767789794845-screenshot-2026-01-07-at-12.42.46-resized.png]

@nebulon thanks for the update. May I take the opportunity to make 2 requests and a comment : the "log jam" on custom apps can easily be solved by building in to the Cloudron facility something equivalent to CCAI (open hosted custom app installer), or more specifically CCAI-P ("closed" Personal Edition installer). The process to install a custom app from a git repo link and pre-built cloudron-ajusted Docker image is relatively trivial for techs/devs like yourselves. An AppDev who is more pro than me can easily accomplish it. The custom apps catalogue is maybe something you don't want to build into Cloudron, but I would be happy to host it, with suitable links for the user to use in their Cloudron equivalent of CCAI-P. although I built it and am therefore responsible, I don't really like the open CCAI, because it is more complex and forces users to enter their creds on a 3rd party site, which is always a little uncomfortable. But CCAI-P or the Cloudron re-engineered version is a very different situation. Even just adopting CCAI-P into the AppStore, maybe as an interim step, would be a huge leap forward, with relatively minimal effort from Cloudron team. happy to make any changes to CCAI-P which Cloudron team dictate to facilitate its adoption to AppStore Specifically about your Maps package, slightly sad to hear it is suspended for now. It is nice. But as an alternative for those wanting something similar, may I pitch Facilmap - already packaged for Cloudron and available as a custom app - as a candidate for early adoption into the AppStore. Final comment : there has been occasional unhappiness that people cannot deploy apps in a docker-compose fashion. I understand and actually agree with this "restriction" - the benefits of Cloudron stability etc are too important to sacrifice. But this unhappiness pops up occasionally and can be very largely addressed by implementing something like CCAI-P into the AppStore or into the platform. All true Cloudron fans want Cloudron to grow, and I think this would be a big part of doing so. After that long pitch, I am very glad that you said the topic is under active discussion, and that even the initial CCAI was not stamped down immediately as being unacceptable, which I would have understood. I look forward to news on the way forward, acknowledging that Cloudron team have 101 other things on their plate.

Just released a new package which fixes the issue. The root problem was a missing LANG environment variable which caused some trouble.

Indeed, that app treats each user individually and since an app would have to actively sync up some deactivated (or even deleted) user state explicitly, which releasebell does not, it just keeps working for that user. Since the app uses OpenID, there is actually no real way for the app, to know if a user even still exists to then purge the user. A login of the user would of course not work, but since this works in releasebell without a login-session, not sure what to besides manually purging that user. Have to think more about how to better handle that, until that you may have to actually do what you proposed. I was trying to quickly come up with a mysql statement to purge, but that is more involved than I thought, due to all the constraints.

hi @msbt How exaclty did you get Cloudflare R2 for Postiz to work? I am trying to get LinkedIn Page working without success and the same error message "Could not add channel .... " tried to overwrite ``` STORAGE_PROVIDER=local in the env file put it never worked

I'm not saying it will suit everyone but dwservice is a free and useful remote support solution. And you don't have to host anything.

@mrejas said in Upgrade to 8.0.1 but interface seems to be 7.x: Haha, I obviously got lost somehow! The Cloudron forurm's search ranking is just Too Good