AIO: apache container unhealthy

Last night the aio apache container became unhealthy according to portainer. I noticed this because all clients lost the connection and also the website was not reachable anymore. The connection times out. The aio settings website is reachable though and all containers are shown as green. The apache container’s log is not very helpfull:

Waiting for Nextcloud to start...
Waiting for Nextcloud to start...
Waiting for Nextcloud to start...
Waiting for Nextcloud to start...
Waiting for Nextcloud to start...
{"level":"info","ts":1689916886.7371073,"msg":"using provided configuration","config_file":"/tmp/Caddyfile","config_adapter":""}
{"level":"info","ts":1689916886.7992942,"msg":"failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Receive-Buffer-Size for details."}
[Fri Jul 21 05:21:26.973569 2023] [mpm_event:notice] [pid 90:tid 139921399200584] AH00489: Apache/2.4.57 (Unix) configured -- resuming normal operations
[Fri Jul 21 05:21:26.973672 2023] [core:notice] [pid 90:tid 139921399200584] AH00094: Command line: '/usr/local/apache2/bin/httpd -D FOREGROUND'

Restarting the containers - did not help.
Restarting the server - did also not help.
Trying to connect from outside the local network does not help either.

What elese could I check or try?

Hi, can you run the following command on the server and post ths output here?

sudo docker inspect nextcloud-aio-apache
curl http://localhost:11000/login

Also can you post your reverse proxy condig here? And is the reverse proxy running in a container or on rhe host on the same server?

Will do so, when I am back home.

I did not install/configure any reverse proxy but just AIO. So anything running should be part of AIO.

Ah I see. Then possibly your public ip-address has changed and was not updated via ddclient in your dns config of yor domain?

Can you also check fhe port 443 is still correctly forwarded in your router?

Thanks for the support! The problem solved itself, i.e. when I came back home the server was reachable. Probably you were right that there was some issue with the ddns.

I guess the result of the docker inspection is not helpful anymore, since it works again?

Have a nice weekend!

1 Like

Indeed. Great that you were able to solve it!

Thanks, you too!