Hello,
I have the Nextcloud-Apache AIO container in an unhealthy status.
I run the [nc -z '$domain' 443] test as described in
[https://help.nextcloud.com/t/nextcloud-aio-unhealthy-502-errors-in-logs/163989/4],
and found that the test by default targets IPv4 (nc -6 ... works fine).
This is because I have a DS-Lite connection over cable,
which means I don't have a universally routable IPv4 address, but rather IPv6.
I can access NC over IP6 and could live with the "unhealthy" status,
but I am receiving a number of additional warnings on the admin page,
which are likely related to this issue and are quite annoying.
Most of them are related to "trusted_domains or the overwrite.cli.url."
I'll skip the lengthy warnings; I believe the issue is found.
What and where can I do? I would like to keep IPv4 in my local network.
Maybe you must set configurationen in you Nextcloud config.php. Only examples.
'trusted_domains' =>
array (
0 => 'localhost',
1 => 'your.domain.com', // Ihre Domain
2 => 'your_ipv6_address', // Ihre IPv6-Adresse
),
'overwrite.cli.url' => 'https://your.domain.com',
Thank you for now, I will do that. But first, I need to fix what I’ve messed up so far.
Edit:
No, it’s not that simple. It’s an IPv6 Docker issue, as described in Rootless, IPv6, Caddy as Proxy: Domain Check fails/External IP not reachable from out of the Container · nextcloud/all-in-one · Discussion #4674 · GitHub and solved in all-in-one/docker-ipv6-support.md at main · nextcloud/all-in-one · GitHub.
1 Like
This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.