Apache container in restart loop after update

ℹ️ Support
, , ,
2

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!