Cloudron Forum

Released v0.0.27 fixing python script issue (reported by @zonzonzon)

Hello @mathieu Unfortunatly we can't add PRs from the upstream code while building the app. This has to be done be the maintainer.

I could also use the fstab to mount an SSHFS filesystem to the remotes, and let Cloudron backup via filesystem there. This would move the management of the mount out of the hands of Cloudron, and into the hands of the OS. I don't know if that would help.

Thanks I will try on another cloudron, just to confirm all is well

Amazing !

Ok, I finally resolved it on my side, and it was caused by the CORS policy on the S3 buckets. The policies were too restrictive, and obviously it wasn't working. [image: 1770723781555-dcd98899-eff9-4a08-b2da-00b9d28ae28e-cleanshot-2026-02-10-at-13.42.18.png]

What version of the @freshrss package do you have installed?

I took a quick look. An installation test revealed one problem. The start.sh file in the repo does not have the execute permission bit set leading to the following error when installing the app: App installation error: Installation failed: (HTTP code 400) unexpected - failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: exec: "/app/pkg/start.sh": permission denied I have created a PR that you can merge to fix this issue: https://github.com/stalecontext/filestash-cloudron-app/pull/1

@girish probably for when we fixed the usernames having trouble with special chars and allowing just a dot which couldn't be deleted!

No, For spam filtering. I've moved to Postfix. I didn't like how locked down the MTA is.

From their FAQ: Can I self host Postiz all by myself? Definitely, we are trying to make Postiz to host as easy as possible, check our documentation to find out how

@LoudLemur thank you the tokens : this kinda reflects the "journey" that CCAI went on. Initially it was browser-only ... and not user's site. I acknowledge users' cautions about this. Hence recommending a short-lived token disposable for use in CCAI open browser Then we had CCAI-P deployed on your own cloudron, and interacting with your own Cloudron. In this case a multi-use long-life token was OK and so recommended. I think the quote you included in your question is from CCAI-P. Then CustomAppGateway got rid of browsers completely for initial install and you enter a token into the binary on your local device. So not needed to use single-use short-term token. But hey everyone's paranoid these days so no harm in doing so. I don't recognise the need for a 3rd token, but it might an academic question, as Cloudron 9.1 will make all this redundant. A much smoother and less problematic security approach, because it's all "on platform" RO vs RW : it needs to make changes to your Cloudron, so RW. pretty icons : that all comes down to the app being deployed. CCAI-P uses a similar but deliberately different logo to Cloudron. Let me know which apps are not rendering a nice icon, and I can look at it. Cloudron : [image: 1770670785150-cloudron.png] CCAI / CCAI-P : [image: 1770670818282-logo.png]

@o1lab it's understandable in this economy. I only have two real requests for your team: 2FA / MFA needs to be one of those enterprise features you give to the community. It is becoming trivial to use tools like Opus 4.6 to find vulnerabilities in open source code and exploit it. You need to come up with a plan for the small business self hosted users. I want to support your product development but I don't need you to host it. I hope you guys seriously consider unlocking a "Community Plus" option.