The Basics
- Nextcloud Server version (e.g., 29.x.x):
replace me
- Operating system and version (e.g., Ubuntu 24.04):
UGreen NAS OS
- Is this the first time you’ve seen this error? (Yes / No):
YES
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
AIO
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
NO
Summary of the issue you are facing:
Hey,
I am really sorry to ask for help here for this probably very stupid question, but I struggle to understand the issue.
I set up AIO on my UGreen NAS without issues, used the myfritz-address my FritzBox provided, worked perfectly. We now moved to a new place, where I cannot use my old FritzBox any more as our provider now is fibreglass.
this being said, I reconnected everything, got myself a ddnss.org-domain, used the great explanation in the aio-documentation for switching domains, have ports 80 and 443 forwarded in the new fritzbox, and now I get this:
Looks similar to this: https://github.com/nextcloud/all-in-one/discussions/2105, but the error is different: "type":"urn:ietf:params:acme:error:malformed","title":"","detail":"Unable to contact \"XXXXXXXX.ddnss.org\" at \"2a04:6ec1:1:4::3:7d91\", no IPv4 addresses to try as fallback","instance":"","subproblems":null
In parallel, from the internal network, I get the FritzBox-Backend-Login page at this domain, even though 443 is forwarded, it is not a DS-lite connection, IPv4 is native in FritzBox, and external connection via https to the fritzbox is off.
I cannot find any threads here or elsewhere in nextcloud fora, which deal with this issue…I’d appreciate, if someone could assist…what did I do wrong in setting up the domain?
Log entries
Here’s the full log of the issue:
2025-09-13T01:33:32.017568749Z Waiting for Nextcloud to start... 2025-09-13T01:33:37.053290252Z Waiting for Nextcloud to start... 2025-09-13T01:33:42.055801348Z Waiting for Nextcloud to start... 2025-09-13T01:33:47.058161394Z Waiting for Nextcloud to start... 2025-09-13T01:33:52.060009394Z Waiting for Nextcloud to start... 2025-09-13T01:33:57.064341175Z Connection to nextcloud-aio-nextcloud (172.18.0.9) 9000 port [tcp/*] succeeded! (...) 2025-09-13T01:34:03.059636331Z {"level":"error","ts":1757727243.0588431,"msg":"challenge failed","identifier":"XXXXXXXX.ddnss.org","challenge_type":"tls-alpn-01","problem":{"type":"urn:ietf:params:acme:error:malformed","title":"","detail":"Unable to contact \"XXXXXXXX.ddnss.org\" at \"2a04:6ec1:1:4::3:7d91\", no IPv4 addresses to try as fallback","instance":"","subproblems":null},"stacktrace":"github.com/mholt/acmez/v3.(*Client).pollAuthorization\n\tgithub.com/mholt/acmez/v3@v3.1.2/client.go:557\ngithub.com/mholt/acmez/v3.(*Client).solveChallenges\n\tgithub.com/mholt/acmez/v3@v3.1.2/client.go:378\ngithub.com/mholt/acmez/v3.(*Client).ObtainCertificate\n\tgithub.com/mholt/acmez/v3@v3.1.2/client.go:136\ngithub.com/caddyserver/certmagic.(*ACMEIssuer).doIssue\n\tgithub.com/caddyserver/certmagic@v0.24.0/acmeissuer.go:489\ngithub.com/caddyserver/certmagic.(*ACMEIssuer).Issue\n\tgithub.com/caddyserver/certmagic@v0.24.0/acmeissuer.go:382\ngithub.com/caddyserver/caddy/v2/modules/caddytls.(*ACMEIssuer).Issue\n\tgithub.com/caddyserver/caddy/v2@v2.10.2/modules/caddytls/acmeissuer.go:288\ngithub.com/caddyserver/certmagic.(*Config).obtainCert.func2\n\tgithub.com/caddyserver/certmagic@v0.24.0/config.go:626\ngithub.com/caddyserver/certmagic.doWithRetry\n\tgithub.com/caddyserver/certmagic@v0.24.0/async.go:104\ngithub.com/caddyserver/certmagic.(*Config).obtainCert\n\tgithub.com/caddyserver/certmagic@v0.24.0/config.go:700\ngithub.com/caddyserver/certmagic.(*Config).ObtainCertAsync\n\tgithub.com/caddyserver/certmagic@v0.24.0/config.go:505\ngithub.com/caddyserver/certmagic.(*Config).manageOne.func1\n\tgithub.com/caddyserver/certmagic@v0.24.0/config.go:415\ngithub.com/caddyserver/certmagic.(*jobManager).worker\n\tgithub.com/caddyserver/certmagic@v0.24.0/async.go:73"}
see here: