Nextcloud AIO v10.1.1 - Apache Will Not Start

ℹ️ Support
,
19

I have updated my Nextcloud AIO to v.10.1.1 few minutes ago and let me share my experience how to solve some troubles.

Here’s how I typically update my Nextcloud AIO setup, along with some tips to handle potential issues during the process.

  1. Stopping and Recreating Containers:
    I start by using the local Nextcloud AIO interface to stop all containers. Then, I log into Portainer and delete all stopped containers except for the mastercontainer. After deleting the containers, I allow the system to recreate them through the local Nextcloud AIO interface.

    This approach usually works well for standard updates. However, there are cases where additional steps may be required.

  2. When Containers Don’t Start Properly:
    If a container fails to start or is marked as “unhealthy” (e.g., the “apache” container), I’ve found that the installation image for that specific container might not have been downloaded correctly. In such cases, I follow these steps:

    • Stop all containers as usual.
    • Delete all stopped containers in Portainer, including the problematic one.
    • Additionally, delete the installation image (in Portainer) for the Docker container that failed to start or was marked as unhealthy.
    • Let the system redownload the image and recreate the container.

    This ensures that any potentially corrupted or incomplete image is replaced, and it has resolved issues for me multiple times.

  3. Cleaning Up Old Images:
    Once everything is running properly and the update has completed successfully, I go back to Portainer and delete all old unused Nextcloud images. This step helps free up disk space and keeps the system tidy.

By including these steps, you can handle updates effectively and troubleshoot any problems that might arise. Let me know if you have any questions or need more details!