Apache container in restart loop after update

The Basics

  • Nextcloud Server version
    • Latest on AIO v11.5.0 with daily backup and update
  • Operating system and version
    • Linux Mint 22.1
  • Web server and version
    • Latest
  • Reverse proxy and version
    • None
  • PHP version:
    • AIO standard
  • Is this the first time you’ve seen this error?
    • Yes
  • When did this problem seem to first start?
    • Today, right after/during automatic update
  • Installation method
    • AIO
  • Are you using CloudfIare, mod_security, or similar?
    • No

Summary of the issue you are facing:

As of today - most likely after tonight’s automatic update - the Apache container is in a restart loop; all other containers are running.

The container’s configuration is as installed.

It was running fine yesterday.

I have already restarted the machine, same problem.

It appears, looking at the mastercontainer’s log, that the update was not finished properly but the AIO menu says, all containers are up to date.

Before I try resetting to a backup, are there other ways to get the container started properly or to finish/redo the update?

Log entries

Mastercontainer
2025-08-12T04:01:40.596708219Z Trying to fix docker.sock permissions internally...
2025-08-12T04:01:40.601397398Z Adding internal www-data to group root
2025-08-12T04:01:40.990537811Z WARNING: DOCKER_INSECURE_NO_IPTABLES_RAW is set
2025-08-12T04:01:40.990593477Z WARNING: daemon is not using the default seccomp profile
2025-08-12T04:01:41.025483042Z WARNING: DOCKER_INSECURE_NO_IPTABLES_RAW is set
2025-08-12T04:01:41.025511664Z WARNING: daemon is not using the default seccomp profile
2025-08-12T04:01:41.343044953Z e[0;92mInitial startup of Nextcloud All-in-One complete!
2025-08-12T04:01:41.343130251Z You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!
2025-08-12T04:01:41.343156139Z E.g. https://internal.ip.of.this.server:8080
2025-08-12T04:01:41.343176137Z ⚠️ Important: do always use an ip-address if you access this port and not a domain as HSTS might block access to it later!
2025-08-12T04:01:41.343243666Z 
2025-08-12T04:01:41.343265306Z If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via:
2025-08-12T04:01:41.343284698Z https://your-domain-that-points-to-this-server.tld:8443e[0m
2025-08-12T04:01:41.573293622Z /usr/lib/python3.12/site-packages/supervisor/options.py:13: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81.
2025-08-12T04:01:41.573318201Z   import pkg_resources
2025-08-12T04:01:42.640013612Z ++ head -1 /mnt/docker-aio-config/data/daily_backup_time
2025-08-12T04:01:42.640041948Z + BACKUP_TIME=04:00
2025-08-12T04:01:42.640047122Z + export BACKUP_TIME
2025-08-12T04:01:42.640050821Z + export DAILY_BACKUP=1
2025-08-12T04:01:42.640054333Z + DAILY_BACKUP=1
2025-08-12T04:01:42.640058329Z ++ sed -n 2p /mnt/docker-aio-config/data/daily_backup_time
2025-08-12T04:01:42.640062219Z + '[' '' '!=' automaticUpdatesAreNotEnabled ']'
2025-08-12T04:01:42.640065823Z + export AUTOMATIC_UPDATES=1
2025-08-12T04:01:42.640069511Z + AUTOMATIC_UPDATES=1
2025-08-12T04:01:42.640073267Z ++ sed -n 3p /mnt/docker-aio-config/data/daily_backup_time
2025-08-12T04:01:42.640477319Z + '[' successNotificationsAreNotEnabled '!=' successNotificationsAreNotEnabled ']'
2025-08-12T04:01:42.640489134Z + export SEND_SUCCESS_NOTIFICATIONS=0
2025-08-12T04:01:42.640494286Z + SEND_SUCCESS_NOTIFICATIONS=0
2025-08-12T04:01:42.640498234Z + set +x
2025-08-12T04:01:42.642220543Z Daily backup script has started
2025-08-12T04:01:42.686871655Z [Tue Aug 12 04:01:42.686409 2025] [mpm_event:notice] [pid 158:tid 158] AH00489: Apache/2.4.65 (Unix) OpenSSL/3.5.1 configured -- resuming normal operations
2025-08-12T04:01:42.686897222Z [Tue Aug 12 04:01:42.686462 2025] [core:notice] [pid 158:tid 158] AH00094: Command line: 'httpd -D FOREGROUND'
2025-08-12T04:01:42.693969514Z [12-Aug-2025 04:01:42] NOTICE: fpm is running, pid 164
2025-08-12T04:01:42.693989765Z [12-Aug-2025 04:01:42] NOTICE: ready to handle connections
2025-08-12T04:01:42.697472572Z {"level":"info","ts":1754971302.6971133,"msg":"maxprocs: Leaving GOMAXPROCS=8: CPU quota undefined"}
2025-08-12T04:01:42.697550536Z {"level":"info","ts":1754971302.697367,"msg":"GOMEMLIMIT is updated","package":"github.com/KimMachineGun/automemlimit/memlimit","GOMEMLIMIT":30288778444,"previous":9223372036854775807}
2025-08-12T04:01:42.697558341Z {"level":"info","ts":1754971302.6974251,"msg":"using config from file","file":"/Caddyfile"}
2025-08-12T04:01:42.699934765Z {"level":"info","ts":1754971302.699096,"msg":"adapted config to JSON","adapter":"caddyfile"}
2025-08-12T04:01:42.704985391Z {"level":"info","ts":1754971302.7043624,"msg":"serving initial configuration"}
2025-08-12T04:01:42.716781929Z Connection to nextcloud-aio-apache (172.18.0.11) 443 port [tcp/https] succeeded!
2025-08-12T04:01:42.756064855Z Starting mastercontainer update...
2025-08-12T04:01:42.756164944Z (The script might get exited due to that. In order to update all the other containers correctly, you need to run this script with the same settings a second time.)
2025-08-12T04:01:44.173002953Z Waiting for watchtower to stop
2025-08-12T04:02:14.239914277Z Updating container images...

The Apache container log is empty.

Hi Grom,

if your Apache container got stuck in a restart loop after the automatic update to Nextcloud AIO v11.5.0 — while all other containers are running fine and the AIO interface still shows everything as up-to-date — I’d recommend trying the approach that has worked well for me in similar cases.


My proven routine for fixing a stuck Apache container

  1. Stop all containers via the local Nextcloud AIO interface.
  2. Log into Portainer and remove all stopped containers, including the Apache container.
  3. Also remove the Apache installation image — not just the container.
  4. Let the system pull a fresh image and recreate the container.

This ensures that any corrupted or incomplete image is replaced, which has solved exactly this kind of issue for me multiple times.


For more details, see my step-by-step guide here:

:link: Nextcloud AIO v10.1.1 – Apache Will Not Start (#19)


Hopefully, this will get your Apache container out of the restart loop.
Good luck getting it sorted!

This has worked, thanks a lot!