Nevermind, it was just a matter of being patient. Everything was set up correctly. For anyone else using Namecheap, it takes a minute for the DNS to sync. Give it some time (quite a bit more than you think) and it'll work.

Maybe https://forum.cloudron.io/topic/1579/var-lib-docker-overlay2-getting-full?_=1760112116784 is helpful: @nebulon said in /var/lib/docker/overlay2 getting full: For a start, docker images are often quite large, composed of a multitude of filesystem layers on top of each other. To mitigate the problem a bit, all Cloudron apps share the same base image, that helps a bit. The appsdata folder really only contains the data from within the apps, so that heavily depends on your own usage. The application code, so to speak, is inside those docker images.

I updated redis to 8.2.2 - https://git.cloudron.io/platform/box/-/commit/3547be34010a737d9fbd5aed5bb9e787eeff5456

Cloudron 9 has pretty much the same flow here. Maybe we have to revisit what the main app cloning use-case is, to figure out a better flow there.

Hello @dffla For the Appstore you need to create a Cloudron.io account and use that for the login. Your own server/cloudron account is not the same as the Cloudron.io account.

@andreasdueren you're welcome, I forgot to post the Hetzner docs, they also have a bit of information on that. Speeds are fine, never had any issues with various kinds of media.

This should be fixed in Cloudron 9, where a backup failure notification email can be configured per user.

Awesome. Many thanks. And this is not a goodbye, I have a lot of other apps here, and planning to work on more

There are a bunch posts on the forum reporting errors with forwards / redirect, and specifically when in come to double forward and SRS rewrite (hence very similar to this one). Would it be helpful to list them?

@jayonrails said in queryNs ESERVFAIL example.com - on all domains?: Hi, I cannot change the DNS Server settings in my domain settings for a domain, because Cloudron says: queryNs ESERVFAIL example.com When trying on the terminal as stated here: @girish said in Domain setup shows 'queryNs ESERVFAIL': @SignalScout On the server, please try host -t NS example.com 127.0.0.1 . Does that work? Sometimes, it takes a bit for the NS of a new domain to propagate. One just has to wait it out. root@my ~ # host -t NS example.com example.com name server root-dns.netcup.net. example.com name server third-dns.netcup.net. example.com name server second-dns.netcup.net. root@my ~ # host -t NS example.com 127.0.0.1 ;; communications error to 127.0.0.1#53: connection refused ;; communications error to 127.0.0.1#53: connection refused ;; no servers could be reached I don't know how to fix that, I cannot get my domains running. The result is the same for all domains, so I think it is a general error on my server. How to get deeper on this? Troubleshooter says: root@my ~ # cloudron-support --troubleshoot Vendor: Hetzner Product: Linux: 6.8.0-52-generic Ubuntu: noble 24.04 Processor: AMD Ryzen 5 3600 6-Core Processor BIOS AMD Ryzen 5 3600 6-Core Processor Unknown CPU @ 3.6GHz x 12 RAM: 65758340KB Disk: /dev/md2 26G [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] nginx is running [OK] dashboard cert is valid [OK] dashboard is reachable via loopback [OK] box v8.2.4 is running [OK] netplan is good [OK] DNS is resolving via systemd-resolved [OK] Dashboard is reachable via domain name [WARN] Domain example-host.de and real estate agents london expiry check skipped because whois does not have this information [OK] unbound is running I am lost and don't know what to do next, I appreciate any tips on this. Best Jay Thanks for bringing this up. An SERVFAIL on all domains usually points to either a misconfiguration in DNS settings or an upstream resolver issue. Double-checking the domain’s authoritative nameservers and ensuring there’s no DNSSEC misconfiguration often helps. Curious to know if you already tested with an external tool like dig or nslookup outside of Cloudron to see if the problem persists?

@joseph Thanks Joseph. Issue was resolved by following steps on email and subscriptions are now linked correctly.

@ccfu This is a very good news... I'm glad that you're not having any problem... I think Hetzner is one of best provider worldwide, but about S3 and Storage boxes they have still to improve their service... I'm also glad that Exoscale met your pricing needs...

Not sure if many are aware of the Cloudron status page https://status.cloudron.io/status/cloudron, so I am just leaving this here.

Hello @tadeas Is this still an issue or can this topic be marked as solved?

Hello @webliska After our private chat and the suggestion to add IPv6 is this still an issue, or can I mark this topic as solved?

Marking this topic as solved since no more input was given from user @jorrg

Hello @mbarria Since there was no more update in this topic can I assume this resolved itself?

Hello @Lomeu Did you figure this out or is this still an issue?

Closing this since no more user details were given.

Closing this issue for now since no further details where provided.