@seeker Community app now available https://forum.cloudron.io/topic/15473/bind-git-backed-web-apps
rosano
Posts
-
remotestorage.io -
Bind: Git-backed web appsSelf-hostable remoteStorage server that enables connecting web apps to git. I'm currently using it to sync web apps to my Gitea instance on Cloudron but it's still in development. So far you can connect a GitHub account and choose a repo.

Be welcome to discuss also on the remoteStorage forum: https://community.remotestorage.io/t/bind-remotestorage-server-backed-by-git/967
Bind
Detail Link / Info Wishlist topic https://forum.cloudron.io/post/7030 Author @rosano Repository https://github.com/0dataapp/bind Install CloudronVersions.json -
Backup seems to fail for community app@james I tried installing the app on a different name and the issue was still there, but now it's not for some reason. Will try what you suggest if it happens again and report back.
-
Backup seems to fail for community appDepending on how the community app it is packaged it could be magnitude of things.
When we introduced community apps, we explicitly stated that we can not offer support for these.I'm not sure it has anything to do with the app. Seems like it's just a permissions issue on Cloudron? Two other installation of the same build (one via
cloudron installand one via Community App) have no issue. -
Backup seems to fail for community appNot sure why this would be the case, other apps are fine.
2026-04-29T08:24:40.883Z taskworker: Starting task 16691. Logs are at /home/yellowtent/platformdata/logs/tasks/16691.log 2026-04-29T08:24:40.931Z taskworker: Running task of type appBackup 2026-04-29T08:24:40.958Z tasks: updating task 16691 with: {"percent":1,"message":"Backing up •••••.•••••.•••••.•••••. Waiting for lock"} 2026-04-29T08:24:40.982Z locks: write: current locks: {"app_backup_3c57c93b-7c67-40ad-bd65-27a18e073a68":"16691"} 2026-04-29T08:24:40.982Z locks: acquire: app_backup_3c57c93b-7c67-40ad-bd65-27a18e073a68 2026-04-29T08:24:40.983Z tasks: updating task 16691 with: {"message":"Snapshotting app •••••.•••••.•••••.•••••"} 2026-04-29T08:24:40.984Z tasks: setCompleted - 16691: {"result":null,"error":{"message":"Error creating config.json: EACCES: permission denied, open '/home/yellowtent/appsdata/3c57c93b-7c67-40ad-bd65-27a18e073a68/config.json'","reason":"FileSystem Error"},"percent":100} 2026-04-29T08:24:40.985Z tasks: updating task 16691 with: {"completed":true,"result":null,"error":{"message":"Error creating config.json: EACCES: permission denied, open '/home/yellowtent/appsdata/3c57c93b-7c67-40ad-bd65-27a18e073a68/config.json'","reason":"FileSystem Error"},"percent":100} 2026-04-29T08:24:40.992Z taskworker: Task took 0.112 seconds BoxError: Error creating config.json: EACCES: permission denied, open '/home/yellowtent/appsdata/3c57c93b-7c67-40ad-bd65-27a18e073a68/config.json' at Object.writeConfig (file:///home/yellowtent/box/src/apps.js:1603:15) at snapshotApp (file:///home/yellowtent/box/src/backuptask.js:328:16) at uploadAppSnapshot (file:///home/yellowtent/box/src/backuptask.js:340:11) at backupAppWithTag (file:///home/yellowtent/box/src/backuptask.js:382:32) at backupApp (file:///home/yellowtent/box/src/backuptask.js:430:24) at process.processTicksAndRejections (node:internal/process/task_queues:103:5) at async appBackup (file:///home/yellowtent/box/src/backuptask.js:594:20) 2026-04-29T08:24:40.993Z Exiting with code 0 -
`cloudron versions update` returns cli versionI was trying to update an existing version of my community app via
cloudron versions update --version 0.0.1and it seems to return
8.2.1which is my cli version.Not sure if I did something incorrect or if this is a bug.
-
CLI ignores cloudron/DockerfileJust tried updating the CLI via
npm install -g cloudron@8.2.1and it seems to work now
Thanks for looking into it. -
CLI ignores cloudron/Dockerfile@james My fix at the moment is to make a temporary commit moving Cloudron stuff into
/Dockerfileand then deleting the commit after successful install. Seems to look only there. -
Community App: CloudronVersions.json Response timeoutSimilarly described in Unusable application:
Pushing/pulling an image from a remote works correctly. However, attempting to pull an image from the same server doesn't work at all.
I tried upgrading to Ubuntu 24.04 and it seems to work as expected now (versions file + icon on the same server without issue).
-
Can't run cloudron update for an app in error staterosano said:
I'm currently very stuck on updating those custom apps when the registry is inaccessible and would appreciate any help.
I've solved my issue by pushing an image to an external registry (docker hub) and then tagging the unreachable image:
docker pull alfa/bravo:charlie docker tag alfa/bravo:charlie docker.cloudron.example.com/bravo:latest docker push docker.cloudron.example.com/bravo:latestBut I've learned that I need to phase out the self-hosted Docker registry due to those same-server network issues and migrate to Cloudron's CLI's built-in uploading and building.
-
Can't run cloudron update for an app in error stateSo you are not able to reach the docker registry to install apps or are you referring to a specific registry used by some community packages?
My registry is on the same Cloudron. I have built images with the Builder app and pushed there to install custom apps in the past. But it seems recently my Cloudron can no longer make network requests to the same Cloudron (maybe I've misconfigured something?).
Maybe the thread is mixing issues
I suppose for this thread I would only want to know if there's a way to force update an app in error state. The network issue is documented here. I'm currently very stuck on updating those custom apps when the registry is inaccessible and would appreciate any help.
-
Can't run cloudron update for an app in error state@nebulon I don't see any reference to hairpin:
[OK] node version is correct [OK] IPv6 is enabled and public IPv6 address is working [OK] docker is running [OK] docker version is correct [OK] MySQL is running [OK] netplan is good [OK] DNS is resolving via systemd-resolved [OK] unbound is running [OK] nginx is running [OK] dashboard cert is valid [OK] dashboard is reachable via loopback [OK] No pending database migrations [OK] Service 'mysql' is running and healthy [OK] Service 'postgresql' is running and healthy [OK] Service 'mongodb' is running and healthy [OK] Service 'mail' is running and healthy [OK] Service 'graphite' is running and healthy [OK] Service 'sftp' is running and healthy [OK] box v9.1.5 is running [OK] Dashboard is reachable via domain name -
Can't run cloudron update for an app in error state@ekevu123 I'm in the same situation now and I'm wondering if your registry is on a separate Cloudron or everything's on one? I have issues whenever my Cloudron makes requests to URLs hosted on the same Cloudron and now it seems I can no longer install because the image can't be reached for that reason

-
CLI ignores cloudron/DockerfileI just tried
cloudron install --file platform/cloudron/Dockerfilein another project and it seems to still be ignoring the--fileargument.No build detected. This package will be built on the server. Location: test-build App is being installed. => Queued ... => Deleting old containers => Building image App installation error: Installation failed: Unable to build image from /home/yellowtent/appsdata/f84d72bb-bbbb-4f2e-a731-30b8cf399128/source.tar.gz: (HTTP code 500) server error - Cannot locate specified Dockerfile: DockerfileIs this a bug or have I missed something?
-
CLI ignores cloudron/DockerfileWith v8.0.2
cloudron updateseems to only look forDockerfileat the root even though my project hascloudron/Dockerfile. I tried deleting theDockerfileat the root and/or setting--file cloudron/Dockerfilebut it still seems to be stuck looking at the root.Cannot locate specified Dockerfile: Dockerfile -
Community App: CloudronVersions.json Response timeoutOk, I've solved this for my purposes.
Seems like when I try
curl -v https://bind.0data.app/CloudronVersions.jsonfrom my Cloudron, it fails.* Trying •••.••.••.••:443... * connect to •••.••.••.•• port 443 failed: Connection timed out * Failed to connect to bind.0data.app port 443 after 129437 ms: Connection timed out * Closing connection 0 curl: (28) Failed to connect to bind.0data.app port 443 after 129437 ms: Connection timed outWhich tells me there's some issue with loading URLs from the same server.
Interestingly, if I find the internal IP via
docker inspect <process> | grep '"IPAddress"'and port via
docker inspect <process> | grep -A5 '"Ports"'I can call successfully load the file with
curl -v -H "Host: bind.0data.app" http://<ip>:<port>/CloudronVersions.jsonBut I have decided it's easier for me to simply host a kind of URL masking thing on another server. Anyway thanks for the help and attention from everyone who chimed in


️ -
Community App: CloudronVersions.json Response timeoutActually I spoke too soon, it did timeout but then it kept going and installed the app. And now it seems to work with the SVG as well. Just seem to not work when my server uses a versions file on the same server.
-
Community App: CloudronVersions.json Response timeout@robi I tried with png in case you mean SVG is an issue, same thing.
Mar 23 09:51:19 tasks: updating task 16295 with: {"percent":15,"message":"Downloading icon"} Mar 23 09:51:19 apptask: downloadIcon: Downloading community icon https://static.rosano.ca/0data/identity.png Mar 23 09:52:19 community: Attempt 1 failed. Will retry: Network error downloading icon: The operation was aborted -
Community App: CloudronVersions.json Response timeoutIf it's important, write to us on support@cloudron.io and we will have to debug further.
I just wrote and was told to post here because it's a technical request?
-
Community App: CloudronVersions.json Response timeoutAlso similarly: I could start installing my app, but it fails on downloading the icon, which is also hosted on my Cloudron.
Mar 21 16:07:20 apptask: downloadIcon: Downloading community icon https://bind.0data.app/identity.svg Mar 21 16:08:20 community: Attempt 1 failed. Will retry: Network error downloading icon: The operation was aborted Mar 21 16:09:25 community: Attempt 2 failed. Will retry: Network error downloading icon: The operation was aborted Mar 21 16:10:31 community: Attempt 3 failed. Will retry: Network error downloading icon: The operation was aborted Mar 21 16:11:36 community: Attempt 4 failed. Will retry: Network error downloading icon: The operation was abortedAgain, not sure why this would behave differently but maybe I will write to support to go deeper.