Cloudron Forum

@hakunamatata good call! I didn't guess they would only allow a list of proxy sources. Now the proxy works well!

@nebulon this is all I have:

Response Headers

content-length: 16
content-type: text/plain; charset=utf-8
date: Wed, 11 Jun 2025 18
server: nginx
x-firefox-spdy: h2

400: Bad Request

When trying to have an App Proxy set up to proxy my local HomeAssistant to be available on a domain, after logging in to cloudron on the domain it only gives 400 error. Is this a cloudron setup issue or issue with HomeAssistant? I use http for uri and use ipv4 address with port. I'm unable to see anything in proxy app logs.

Looks like another update of SIG helper is needed.

License listed for komga or for the cloudron files?

Edit: there's no license field in manifest, so I just added the license to the repo.

I update my komga repo to the latest version. Been working great with my Kobo.

Wow, there sure are lots of fixes needed for inv sig helper:
https://github.com/iv-org/inv_sig_helper/pull/43

Inv Sig helper could use an update: https://github.com/iv-org/inv_sig_helper/issues/36

Yep, that worked!

I packaged it because I orederd a kobo device and there was good support for it with this software. I packaged Kavita previously, so I'm sure I'll package more in the future when I find good motivation.

I've made a first build of Komga for cloudron:
~~https://git.eyecreate.org/eyecreate/cloudron-komga~~
https://git.cloudron.io/eyecreate/komga
I didn't know if it was worth setting it up with OIDC, but otherwise should be fully usable.
I also included kepubify to help make more compatible with Kobo devices.

I was going to make a new repo on git.cloudron.io, but couldn't find the create repo button. I eventually tried the url https://git.cloudron.io/projects/new and got a 404. Did something happen where restrictions have been placed on this instance or is there a bug?

I've been using this device:
https://slae.sh/projects/cc2652/
As well as a development device with a Texas Instruments CC2531 chip for testing.

I was playing around with homeassistant to see of I could use this server app instead of my RPI. It seems I can't find a way to pass in devices like my USB ZigBee radio to the container. Is there a workaround or plan to make this possible?

I noticed recently that my subscription list of videos was not updating. After looking into the documentation, it seems that they expect you to reboot the software frequently. Anywhere from hourly to daily. After rebooting, it was working correctly again. Is there a way that we could automate or allow configuring how often a container is rebooted?

I've also had similar issues with backups the past few days.

2024-03-20T08:58:00.790Z box:shell backup-snapshot/app_c4a27e93-af6e-44e2-b7cf-9056fa01c5c3 code: null, signal: SIGKILL
2024-03-20T08:58:00.792Z box:taskworker Task took 10678.952 seconds
2024-03-20T08:58:00.793Z box:tasks setCompleted - 16169: {"result":null,"error":{"stack":"BoxError: Backuptask crashed\n    at runBackupUpload (/home/yellowtent/box/src/backuptask.js:164:15)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async uploadAppSnapshot (/home/yellowtent/box/src/backuptask.js:361:5)\n    at async backupAppWithTag (/home/yellowtent/box/src/backuptask.js:383:5)\n    at async fullBackup (/home/yellowtent/box/src/backuptask.js:504:29)","name":"BoxError","reason":"Internal Error","details":{},"message":"Backuptask crashed"}}
2024-03-20T08:58:00.793Z box:tasks update 16169: {"percent":100,"result":null,"error":{"stack":"BoxError: Backuptask crashed\n    at runBackupUpload (/home/yellowtent/box/src/backuptask.js:164:15)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async uploadAppSnapshot (/home/yellowtent/box/src/backuptask.js:361:5)\n    at async backupAppWithTag (/home/yellowtent/box/src/backuptask.js:383:5)\n    at async fullBackup (/home/yellowtent/box/src/backuptask.js:504:29)","name":"BoxError","reason":"Internal Error","details":{},"message":"Backuptask crashed"}}
BoxError: Backuptask crashed

It would be nice if the error or code it pointed too had more info about what happened. Best I can tell is it got killed somehow. I increased the backup task memory and will see what happens next time.

Edit: it didn't crash yesterday, so maybe it just needed more ram.

Yep, just added it now!

I haven't updated the readme(which references some incorrect instructions for install), but I think the build instructions should work.

@robi v7.6.4

If my nfs server goes offline, the nfs volumes in cloudron are in a failure state(or, even if you refresh the volume in dashboard, files don't show up in container) until the containers using them are restarted. Remounting the volume in dashboard should fix any connection issues without manual restarting containers.