Cloudron Forum

@james I understand, I was suggesting a change for situations like Case 2 - a little more transparent but still a short message as to not confuse users/admins.

Hello, my Cloudron instance updated last night to 9.1.3 and many of my apps are not starting due to "plattform start" not finished. Looking at the services I found the redis not starting up in the context of one container (pixelfed). In the log I found this: cloudron-support --troubleshoot: Vendor: QEMU Product: Standard PC (i440FX + PIIX, 1996) Linux: 6.8.0-101-generic Ubuntu: noble 24.04 Execution environment: kvm Processor: 13th Gen Intel(R) Core(TM) i9-13900H BIOS pc-i440fx-10.1 CPU @ 2.0GHz x 8 RAM: 32859228KB Disk: /dev/sda2 2.7T [OK] node version is correct [OK] IPv6 is enabled in kernel. No public IPv6 address [OK] docker is running [OK] docker version is correct [OK] MySQL is running [OK] netplan is good [OK] DNS is resolving via systemd-resolved Service 'unbound' just started 7 secs ago, checking health again in 10s [OK] unbound is running [OK] nginx is running [OK] dashboard cert is valid [OK] dashboard is reachable via loopback [FAIL] Database migrations are pending. Last migration in DB: /20260217120000-mailPasswords-create-table.js. Last migration file: /package.json. Please run 'cloudron-support --apply-db-migrations' to apply the 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.3 is running [FAIL] Could not load dashboard domain. Hairpin NAT is not working. Please check if your router supports it Running 'cloudron-support --apply-db-migrations' (several times) didn't help. From '/home/yellowtent/platformdata/logs/box.log': ... 2026-03-09T17:43:51.873Z box:services Waiting for redis-33711a7d-a850-4163-9678-6c37aba763a8 2026-03-09T17:43:51.875Z box:services Attempt 1 failed. Will retry: Network error waiting for redis-33711a7d-a850-4163-9678-6c37aba763a8: connect ECONNREFUSED 172.18.0.2:3000 2026-03-09T17:44:07.058Z box:services startRedis: stopping and deleting previous redis container redis-693839fe-6d93-4bec-8963-ba45f18ffc2e 2026-03-09T17:44:07.058Z box:docker stopContainer: stopping container redis-693839fe-6d93-4bec-8963-ba45f18ffc2e 2026-03-09T17:44:09.550Z box:docker deleteContainer: deleting redis-693839fe-6d93-4bec-8963-ba45f18ffc2e 2026-03-09T17:44:09.700Z box:services startRedis: starting redis container redis-693839fe-6d93-4bec-8963-ba45f18ffc2e 2026-03-09T17:44:09.752Z box:shell services: /bin/bash -c docker run -d --restart=unless-stopped --name=redis-693839fe-6d93-4bec-8963-ba45f18ffc2e --hostname redis-693839 fe-6d93-4bec-8963-ba45f18ffc2e --label=location=mastodon.moik.cloud --net cloudron --net-alias redis-693839fe-6d93-4bec-8963-ba45f18ffc2e --log-driver syslog --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock --log-opt syslog-format=rfc5424 --log-opt tag=redis-693839fe-6d93-4bec-8963-ba45f18ffc2e -m 4294967296 --memory-swap -1 -e CLOUDRON_REDIS_PASSWORD -e CLOUDRON_REDIS_TOKEN=[...] -v /home/yellowtent/platformdata/redis/693839f e-6d93-4bec-8963-ba45f18ffc2e:/var/lib/redis --label isCloudronManaged=true --read-only -v /tmp -v /run registry.docker.com/cloudron/redis:3.8.0@sha256:54 a12252edbc326fd4d10e8c00836cc68776f3463f22366279f7cd8d4dafd20f 2026-03-09T17:44:10.579Z box:services Waiting for redis-693839fe-6d93-4bec-8963-ba45f18ffc2e 2026-03-09T17:44:30.583Z box:services Attempt 1 failed. Will retry: Network error waiting for redis-693839fe-6d93-4bec-8963-ba45f18ffc2e: The operation was aborted 2026-03-09T17:45:05.585Z box:services Attempt 2 failed. Will retry: Network error waiting for redis-693839fe-6d93-4bec-8963-ba45f18ffc2e: The operation was aborted 2026-03-09T17:45:40.585Z box:services Attempt 3 failed. Will retry: Network error waiting for redis-693839fe-6d93-4bec-8963-ba45f18ffc2e: The operation was aborted ``` It seems that redis can't write to /run/redis Any ideas? Thanks. BR Adam

@robi great find! will give it a try.

The new sidebar layout introduced in the recent versions is great. More and more apps are shifting towards this kind of layout, which is arguably much better for UI navigation. Even though I've used Cloudron for years, I sometimes find myself scrambling in the documentation to search for a very specific information. Having an external link button next to the heading, that points to the appropriate section in the documentation would be helpful. [image: 1773067888139-ef332c4b-d4a4-42b7-a13c-a783196cb61e-image.jpeg] [image: 1773068058647-68e922de-9251-4c03-81b1-5653bfca9018-image-resized.jpeg]

Yay ! my Bitcoin Core data sync reached 100%

ControlR One more vote for ControlR

So, feeling stupid (more than normal) for starting with ZNC (Zeronet Conservancy), ZNX (ZeronetX) is now packaged. Ignoring the vagaries of P2P and Tor, this does seem to be viable. Git repo : https://git.cloudron.io/timconsidine/cloudron-zeronet (same) has been refactored into 2 folders, ZNC just in case someone feels they want to take it over / use as a base, and ZNX. Docker image: tcmbp132021/cloudron-zeronet:v3.0.0 ZNX actually allows an ID to be created and ZNX-leaning sites seem to be alive. I absolutely see the value of Zeronet for different uses, including hiding in plain sight (for legitimate reasons), and it seems usable enough. Old/abandoned/un-peered sites can be ignored. Set up active sites. Haven't yet found a site to promote relocation of No.10 / Millbank PHQ to central Tehran, but I will keep looking.

Hello @timconsidine Good point. Will update the documentation.

@humptydumpty This is a big problem. I was shocked to see that as of 2026, only 4 out of 50 states had passed the "right to repair". But if Chinese AI companies can used "distillation" to create new AI models, then perhaps the same approach could be used to create a digital twin of a tractor and then replace proprietary software with open source software.