The issue here was that unbound was not working. Because of that, all the docker image updates are failing like so: 2022-12-06T03:38:02.801Z box:shell startGraphite exec: docker run --restart=always -d --name="graphite" --hostname graphite --net cloudron --net-alias graphite --log-driver syslog --log-opt syslog-address=udp://127.0.0.1:2514 --log-opt syslog-format=rfc5424 --log-opt tag=graphite -m 429916160 --memory-swap 536870912 --dns 172.18.0.1 --dns-search=. -p 127.0.0.1:2003:2003 -v "/home/yellowtent/platformdata/graphite:/var/lib/graphite" --label isCloudronManaged=true --read-only -v /tmp -v /run "cloudron/graphite:3.2.0@sha256:182e5cae69fbddc703cb9f91be909452065c7ae159e9836cc88317c7a00f0e62" Box GET /api/v1/appstore/apps?repository=core 424 Failed Dependency getaddrinfo EAI_AGAIN api.cloudron.io 10.852 ms - 89 2022-12-06T03:38:03.581Z box:shell startGraphite (stdout): null 2022-12-06T03:38:03.581Z box:shell startGraphite (stderr): Unable to find image 'cloudron/graphite:3.2.0@sha256:182e5cae69fbddc703cb9f91be909452065c7ae159e9836cc88317c7a00f0e62' locally docker: Error response from daemon: Get "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io on 127.0.0.1:53: server misbehaving. See 'docker run --help'. It was hard to figure why unbound is not working, all queries fail with ESERVFAIL (VM, Hyper-V, router, many things here). It's some networking related issue hard to diagnose without getting a full hand on the setup. The workaround was to add a file called /etc/unbound/unbound.conf.d/forward-everything.conf with the following: forward-zone: name: "." forward-addr: 1.1.1.1 forward-addr: 8.8.8.8 Then, systemctl restart unbound . After that, host cloudron.io 127.0.0.1 should work. Finally, systemctl restart box will then bring up all the containers again.

@girish said in Delete Local Backups: Documented at https://docs.cloudron.io/backups/#old-local-backups small typo there s/snapshots/snapshot

@msbt said in Can't manage existing email address since v7.3.4 update: for debugging, lmk if needed Not needed. Just takes a really long time to fetch for domains with bigger maildata.

@girish thank you

Not sure I completely understood your questions... but just add the DNS for my.cloud.host.name to point to the server and you should be able to access the dashboard from there. Is this a VPS or some home server? The deceptive warning is probably not related to all this.

@nebulon you were right. With the new version 7.3 the restore worked immediately and now baserow is running again. Thank you for the great support!

@jdaviescoates said in Multiple servers on a paid license: Probably wont be for quite a while, I think Yes, work on this is still months away. We have a bunch of things we want to fix before we do multi-host. Also, the multi-host when it happens will anyways have a different pricing structure (I don't know what that is). But as always, existing customers will always get some better pricing than what we go with (we always grandfather, never change prices on existing customers).

@girish sweet- that worked! I saw that's also what you said here: https://forum.cloudron.io/topic/5457/site-is-not-reachable/7 And is basically what's described in the troubleshooting as well. At first this was just an issue with the uninstalled containers, but then when I restarted for a cloudron update it took down the whole thing, which made me think ngnix really was broken Thank you!

Issue was https://forum.cloudron.io/topic/6506/after-a-reboot-nginx-does-not-start

@redegelde said in server cloudron install ubuntu 22.04: The fiddle was after installing Cloudron. Cloudron tells you not to do so in the banner if you login over SSH after installation ^^ Everything you can do or change is documentated in the docs. @redegelde said in server cloudron install ubuntu 22.04: What is/are the good workaround to move from one to other vps The easiest way for a fresh installation is setting up a new VPS with Cloudron and restore from a recent backup during setup. For migrating Mastodons user management I can't give you any advice but there are various topics regarding this if you look through the Cloudron forum.

@girish OK

@martinkbs this is on contabo correct? I will give it a try to see why the installation fails.

@nebulon Thank you for the quick reply. I just emailed with the dashboard domain.

Yes, I did remount the shares.

@subven Thanks for the details I will also trying this later today.. I appreciate the help. It is different to wrap your head around the Cloudron way of thinking....

@jdaviescoates that was quick!

@girish Okay, that is super easy, thank you very much!

@opensourced said in Persistent custom nginx configuration: plugins which are available for free are crapy and I dont trust them fyi Wordfence is not crappy (imho everyone running WordPress should install it) and would easily sort this for you