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...

@nebulon Hi, I'm loving Cloudron so far! Could you please approve me as well so I can vote on the app wishlist?

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.

Hello @JueBam Did you get this resolved or is further assistance required?

@girish @james Thanks!

@David-0 the Service Account Username should be set to cn=admin,ou=system,dc=cloudron and Service Account Password should be the Bind password. There are two separate LDAP servers - internal one and an external one. The external facing one can be authenticated against by the one and only "virtual admin user" i.e the admin CN above. Cloudron admin and Cloudron users don't have the permissions to search for other users in the external facing server.

Given the confidential nature of this, please write to us at support@cloudron.io if they need some information on our side.

Fixed here - https://git.cloudron.io/platform/box/-/commit/ac7001b96e176e540ede9bb81e3fcb17ae7f6416

@webliska Is this resolved now?

Hello @CaeruleusAqua Please assist me in understanding this issue better. I want to figure out if is just a single filename or path and filename causing this issue. For this please go into the web terminal of your nextcloud and go into your /app/data/ folder. cd /app/data/ Please run the following command. It will find the deepest path and the longest filename. With these details I can further debug this issue. find . -type d | awk -F/ '{if(NF>max){max=NF; path=$0}} END{print "Max depth:", max-1, "Path:", path}'; \ find . -type f | awk -F/ '{if(length($NF)>max){max=length($NF); file=$0}} END{print "Longest filename length:", max, "File:", file}' Also can you please provide details about your backup provider?