AIO apache unhealthy

I installed a new nextcloud instance with the aio container. All went well so far but there is one problem that worries me a bit.

Nextcloud seems to be up and running and I can upload files without problems.
But the nextcloud-aio-apache container is always shown as unhealthy even though the webserver is up and running. I did not notice any major issues other than the instance became unresponsive and containers had to be restarted once after switching between some menus.

On the AIO page everything seems normal:

Looking at the container logs in portainer I see the following which doesn’t look very helpful:

Waiting for Nextcloud to start...
Waiting for Nextcloud to start...
Waiting for Nextcloud to start...
Waiting for Nextcloud to start...

INF ts=1691100124.4294064 msg=using provided configuration config_file=/tmp/Caddyfile config_adapter=

[Fri Aug 04 00:02:04.430015 2023] [mpm_event:notice] [pid 35:tid 139849690676040] AH00489: Apache/2.4.57 (Unix) configured -- resuming normal operations

[Fri Aug 04 00:02:04.430037 2023] [core:notice] [pid 35:tid 139849690676040] AH00094: Command line: '/usr/local/apache2/bin/httpd -D FOREGROUND'

I am a bit worried I could run into problems further down the road so I would appreciate some help what could be the issue.

I am running Nextcloud on Oracle Linux 9.2

EDIT: I am running Nextcloud behind Nginx Proxy Manager which is running on another host if this is relevant in any way.

My docker compose looks like this:

          image: nextcloud/all-in-one:latest
          restart: always
          container_name: nextcloud-aio-mastercontainer
            - nextcloud_aio_mastercontainer:/mnt/docker-aio-config
            - /var/run/docker.sock:/var/run/docker.sock:ro
            - 8080:8080
            - APACHE_PORT=11000
            - APACHE_IP_BINDING=
            - nextcloud-aio

          name: nextcloud_aio_mastercontainer

          name: nextcloud-aio
          driver: bridge

See Nextcloud AIO Unhealthy 502 Errors in Logs - #13 by pmorch