# Apache AIO container unhealthy, IP4/6 issue?

**URL:** <https://help.nextcloud.com/t/apache-aio-container-unhealthy-ip4-6-issue/202034>\
**Category:** ℹ️ Support\
**Tags:** docker, apache, aio, ipv6, docker-compose\
**Created:** [August 29, 2024, 11:01am UTC](https://help.nextcloud.com/t/apache-aio-container-unhealthy-ip4-6-issue/202034 "2024-08-29T11:01:03Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ren\_Tier](https://help.nextcloud.com/user_avatar/help.nextcloud.com/ren_tier/32/51299_2.png) [@Ren\_Tier](https://help.nextcloud.com/u/Ren_Tier)\
**Post date:** [August 29, 2024, 11:01am UTC](https://help.nextcloud.com/t/apache-aio-container-unhealthy-ip4-6-issue/202034/1 "2024-08-29T11:01:03Z")

</div>

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

```

---

<div class="post-metadata">

**Author:** ![devnull](https://help.nextcloud.com/user_avatar/help.nextcloud.com/devnull/32/27793_2.png) [@devnull](https://help.nextcloud.com/u/devnull)\
**Post date:** [August 29, 2024, 11:39am UTC](https://help.nextcloud.com/t/apache-aio-container-unhealthy-ip4-6-issue/202034/2 "2024-08-29T11:39:49Z")

</div>

Maybe you must set configurationen in you Nextcloud `config.php`. Only examples.

```auto
'trusted_domains' => 
array (
  0 => 'localhost',
  1 => 'your.domain.com', // Ihre Domain
  2 => 'your_ipv6_address', // Ihre IPv6-Adresse
),

```

[documentation](https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/config_sample_php_parameters.html#trusted-domains)

`'overwrite.cli.url' => 'https://your.domain.com',`

[documentation](https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/config_sample_php_parameters.html#overwrite-cli-url)

---

<div class="post-metadata">

**Author:** ![Ren\_Tier](https://help.nextcloud.com/user_avatar/help.nextcloud.com/ren_tier/32/51299_2.png) [@Ren\_Tier](https://help.nextcloud.com/u/Ren_Tier)\
**Post date:** [August 29, 2024, 6:19pm UTC](https://help.nextcloud.com/t/apache-aio-container-unhealthy-ip4-6-issue/202034/3 "2024-08-29T18:19:20Z")

</div>

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](https://github.com/nextcloud/all-in-one/discussions/4674) and solved in [all-in-one/docker-ipv6-support.md at main · nextcloud/all-in-one · GitHub](https://github.com/nextcloud/all-in-one/blob/main/docker-ipv6-support.md).

---

<div class="post-metadata">

**Author:** ![system](https://help.nextcloud.com/user_avatar/help.nextcloud.com/system/32/29333_2.png) [@system](https://help.nextcloud.com/u/system)\
**Post date:** [September 6, 2024, 6:20pm UTC](https://help.nextcloud.com/t/apache-aio-container-unhealthy-ip4-6-issue/202034/4 "2024-09-06T18:20:04Z")

</div>

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.