Cloudron Forum

I had the same 400 error with IONOS S3 and it turned out to be a simple setup issue. In Cloudron’s backup settings, make sure you select the IONOS (Profitbricks) option instead of the generic S3 choice. Then double-check that the endpoint and region match your bucket exactly—for example s3.<your-region>.ionoscloud.com—and that path-style URLs are enabled. After I corrected those settings, the backups ran without any errors. If you still get the 400 after that, try a small manual backup or upload a tiny file with the same keys using the AWS CLI to confirm the credentials. If the problem persists, sharing the few log lines just before the crash will help others spot what’s wrong. Hope this helps get your backups running smoothly.

Okay, thanks! Just switched to the Cloudron app, and it is working nicely so far.

@marcusquinn Fantastic!

Hi @girish Just wondering if including a tiny LLM into the package is still on the table. Hoarding links gets quickly out of proportion and the search function of Linkwarden is not the best (in my case). Auto-tagging would be very helpful to find links saved ages ago.

We would like to see a cloudron reseller who accepts Bitcoin for payment

To the Horillia enthusiast I am looking for alpha testers of the Horilla Cloudron app. Public installation with demo data for testing https://horilla.cloudron.app.cloudron.dev/ Login is admin:admin I can reset this setup anytime to the default demo state if needed. Custom private installation You need the Cloudron CLI Login to your Cloudron instance: cloudron login my.$DOMAIN.$TLD Clone the code: git clone ssh://git@git.cloudron.io:6000/playground/horilla-app.git cd horilla-app git checkout develop Install the app: cloudron install --location $YOUR_CUSTOM_SUBDOMAIN --image brutalbirdie/horilla.cloudron.app:0.0.11 I have added a doc.md file for common task: https://git.cloudron.io/playground/horilla-app/-/blob/develop/doc.md?ref_type=heads

@girish sounds great! for app support you could maybe add a "support" entry for each app in the "configure app" settings which displays the contact information (mail or link to support page) of the maintainer. something to keep in mind of course is to make it clear who support what. cloudron system issues -> cloudron. app updates or issues of the app running on cloudron -> maintainer issues with the app itself -> app developers marking the apps with a little icon to indicate who is maintaining it or maybe if the maintainers are somehow "verified"/"trusted" would be nice. alternative is ofcourse to allow custom apps but make it abundantly clear that cloudron will not support any issues. could be a red indicator in the "support" tab like "not officially supported by cloudron. please contact support@maintainer.com for assistance or ask in the forum." either way i would love to see custom app support! maybe hiding the option for custom apps/app repos under "developer options" or something similar could be a start, so it has to be explicitly activated. here you could also add the info "activate at your own risk. custom apps are not supported by the cloudron team.

Hello @DerrickX and welcome to the Cloudron Forum

Nice! thanks @girish

Hello @OrezBodajoy Please run the following command and provide output of cloudron-support --troubleshoot