solved by adjusting existing DNS A Record entry. Changing from aaaa:bbbb:cccc:dddd:: to aaaa:bbbb:cccc:dddd::1
C
CodeResearcher
@CodeResearcher
Posts
-
setup get stuck in waitForDns -
setup get stuck in waitForDnsHi all,
looking for some support regarding the initial setup of cloudron.
My domain is registered by namecheap.com. Unfortunately I'm not fullfilling the criteria by namecheap for using an API key. Therefore I used Wildcard as a DNS Provider. But the setup gets stuck. Log file is repeating those entries:
2025-07-12T20:21:36.032Z box:dns/waitfordns waitForDns: nameservers are ["dns1.registrar-servers.com","dns2.registrar-servers.com"] 2025-07-12T20:21:36.033Z box:dns/waitfordns resolveIp: Checking AAAA for my.my-domain.net at 156.154.132.200 2025-07-12T20:21:36.041Z box:dns/waitfordns isChangeSynced: my.my-domain.net (AAAA) was resolved to aaaa:bbbb:cccc:dddd:: at NS dns1.registrar-servers.com (156.154.132.200). Expecting aaaa:bbbb:cccc:dddd::1. M> 2025-07-12T20:21:36.041Z box:dns/waitfordns resolveIp: Checking AAAA for my.my-domain.net at 2610:a1:1024::200 2025-07-12T20:21:36.071Z box:dns/waitfordns isChangeSynced: my.my-domain.net (AAAA) was resolved to aaaa:bbbb:cccc:dddd:: at NS dns1.registrar-servers.com (2610:a1:1024::200). Expecting aaaa:bbbb:cccc:dddd::1.> 2025-07-12T20:21:36.071Z box:dns/waitfordns waitForDns: my.my-domain.net at ns dns1.registrar-servers.com: not done 2025-07-12T20:21:36.071Z box:dns/waitfordns Attempt 91 failed. Will retry: ETRYAGAIN
I looks like IPv6 address don't match. My IPv6 address is aaaa:bbbb:cccc:dddd:: it's expecting aaaa:bbbb:cccc:dddd::1. Any idea how this can be solved?
-
Typesense - Fast, typo tolerant, fuzzy search engine for building delightful search experiencesany plans to add this to the app store soon?