Unused or stopped? I ran these commands after stopping all but the mastercontainer via the AIO portal:
docker ps -a --filter "status=exited"
docker rm $(docker ps -aq --filter "status=exited")
Not sure if there is something else you are talking about though. Given the reference page for docker, I believe the docker container prune command and what I did (more manual) accomplish the same thing.
When I restarted AIO (after compose down/up), it did prompt me to download updated images.
Unfortunately, recreating all the containers did NOT fix the issue. The was a crash again early this morning. At this point, it does not look memory related and is persisting beyond the container rebuilds. I did grab logs again and can post those if needed.
If anyone has any other suggestions or requests, I am open to anything at this point. Thank you.
root@vps:~# free -h
total used free shared buff/cache available
Mem: 15Gi 2.7Gi 268Mi 257Mi 13Gi 12Gi
Swap: 511Mi 511Mi 196Ki
root@vps:~# docker stats --no-stream --format "$(date): {{.Name}} {{.MemUsage}}"
Mon Apr 27 10:08:18 EDT 2026: nextcloud-aio-nextcloud 3.203MiB / 15.52GiB
Mon Apr 27 10:08:18 EDT 2026: nextcloud-aio-imaginary 9.914MiB / 15.52GiB
Mon Apr 27 10:08:18 EDT 2026: nextcloud-aio-redis 4.965MiB / 15.52GiB
Mon Apr 27 10:08:18 EDT 2026: nextcloud-aio-database 184.9MiB / 15.52GiB
Mon Apr 27 10:08:18 EDT 2026: nextcloud-aio-notify-push 1.32MiB / 15.52GiB
Mon Apr 27 10:08:18 EDT 2026: nextcloud-aio-collabora 57.89MiB / 15.52GiB
Mon Apr 27 10:08:18 EDT 2026: nextcloud-aio-mastercontainer 68.21MiB / 15.52GiB
Hi, we are trying to improve the php config in Fix intermittent 502 Bad Gateway: PHP-FPM request_terminate_timeout + process_idle_timeout by Copilot · Pull Request #8013 · nextcloud/all-in-one · GitHub in the next release to try to prevent such problems from happening.
This is now released with v13.0.0 Beta. Testing and feedback is welcome! See GitHub - nextcloud/all-in-one: 📦 The official Nextcloud installation method. Provides easy deployment and maintenance with most features included in this one Nextcloud instance. · GitHub
Thank you. I will install it and try it.
Unfortunately, that still did not work. I had a crash again this morning. Same thing with the 502 Bad Gateway.
root@vps:~# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
c9bb1b3df454 ghcr.io/nextcloud-releases/aio-apache:beta "/start.sh /usr/bin/…" 5 hours ago Created nextcloud-aio-apache
f8c9bfea7d09 ghcr.io/nextcloud-releases/aio-nextcloud:beta "/start.sh /usr/bin/…" 5 hours ago Up 5 hours (unhealthy) 9000/tcp nextcloud-aio-nextcloud
3f297cf0707a ghcr.io/nextcloud-releases/aio-imaginary:beta "/start.sh" 5 hours ago Up 5 hours (healthy) nextcloud-aio-imaginary
86d33b4d9d1b ghcr.io/nextcloud-releases/aio-redis:beta "/start.sh" 5 hours ago Up 5 hours (healthy) 6379/tcp nextcloud-aio-redis
39eda8378a73 ghcr.io/nextcloud-releases/aio-postgresql:beta "/start.sh" 5 hours ago Up 5 hours (healthy) 5432/tcp nextcloud-aio-database
842251471d5a ghcr.io/nextcloud-releases/aio-notify-push:beta "/start.sh" 5 hours ago Up 5 hours (healthy) nextcloud-aio-notify-push
31099e7ebebf ghcr.io/nextcloud-releases/aio-collabora:beta "/start.sh" 5 hours ago Up 13 minutes (healthy) 9980/tcp nextcloud-aio-collabora
997807c7cc7a ghcr.io/nextcloud-releases/aio-borgbackup:beta "/start.sh" 5 hours ago Exited (0) 5 hours ago nextcloud-aio-borgbackup
3ab137b71d6d ghcr.io/nextcloud-releases/aio-watchtower:beta "/start.sh" 5 hours ago Exited (0) 5 hours ago nextcloud-aio-watchtower
dce6539aebf9 ghcr.io/nextcloud-releases/all-in-one:beta "/start.sh" 3 days ago Up 3 days (healthy) 80/tcp, 8443/tcp, 9000/tcp, 0.0.0.0:8080->8080/tcp nextcloud-aio-mastercontainer
root@vps:~# free -h
total used free shared buff/cache available
Mem: 15Gi 2.3Gi 341Mi 277Mi 13Gi 13Gi
Swap: 511Mi 511Mi 644Ki
root@vps:~# docker stats --no-stream --format "$(date): {{.Name}} {{.MemUsage}}"
Mon May 11 10:25:19 EDT 2026: nextcloud-aio-nextcloud 3.93MiB / 15.52GiB
Mon May 11 10:25:19 EDT 2026: nextcloud-aio-imaginary 9.66MiB / 15.52GiB
Mon May 11 10:25:19 EDT 2026: nextcloud-aio-redis 7.27MiB / 15.52GiB
Mon May 11 10:25:19 EDT 2026: nextcloud-aio-database 209MiB / 15.52GiB
Mon May 11 10:25:19 EDT 2026: nextcloud-aio-notify-push 1.145MiB / 15.52GiB
Mon May 11 10:25:19 EDT 2026: nextcloud-aio-collabora 58.07MiB / 15.52GiB
Mon May 11 10:25:19 EDT 2026: nextcloud-aio-mastercontainer 58.18MiB / 15.52GiB
One thing I have noticed is that the aio-collabora container is always restarting it seems. These are all from the past 3 days (1 per day). I have never seen the aio-collabora container be up longer than 14 minutes. I assume this is intended as part of the fix in the 13.0.x version. If not, then it might be a symptom of the larger crash issue.
I have not had a crash since the last time I posted 5 days ago.
root@vps:/etc# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
dcbea79e465f ghcr.io/nextcloud-releases/aio-apache:beta "/start.sh /usr/bin/…" 10 hours ago Up 10 hours (healthy) 80/tcp, 0.0.0.0:11000->11000/tcp nextcloud-aio-apache
dfa2ee428b1b ghcr.io/nextcloud-releases/aio-nextcloud:beta "/start.sh /usr/bin/…" 10 hours ago Up 10 hours (healthy) 9000/tcp nextcloud-aio-nextcloud
6d49c39cb553 ghcr.io/nextcloud-releases/aio-imaginary:beta "/start.sh" 10 hours ago Up 10 hours (healthy) nextcloud-aio-imaginary
7b441caa9bae ghcr.io/nextcloud-releases/aio-redis:beta "/start.sh" 10 hours ago Up 10 hours (healthy) 6379/tcp nextcloud-aio-redis
17b2f446aea7 ghcr.io/nextcloud-releases/aio-postgresql:beta "/start.sh" 10 hours ago Up 10 hours (healthy) 5432/tcp nextcloud-aio-database
715172a8bf2d ghcr.io/nextcloud-releases/aio-notify-push:beta "/start.sh" 10 hours ago Up 10 hours (healthy) nextcloud-aio-notify-push
0bf365a0e813 ghcr.io/nextcloud-releases/aio-collabora:beta "/start.sh" 10 hours ago Up 2 minutes (healthy) 9980/tcp nextcloud-aio-collabora
3655433d2400 ghcr.io/nextcloud-releases/aio-borgbackup:beta "/start.sh" 10 hours ago Exited (0) 10 hours ago nextcloud-aio-borgbackup
c547c4dd4c6a ghcr.io/nextcloud-releases/aio-watchtower:beta "/start.sh" 10 hours ago Exited (0) 10 hours ago nextcloud-aio-watchtower
dce6539aebf9 ghcr.io/nextcloud-releases/all-in-one:beta "/start.sh" 6 days ago Up 3 days (healthy) 80/tcp, 8443/tcp, 9000/tcp, 0.0.0.0:8080->8080/tcp nextcloud-aio-mastercontainer
root@vps:/etc# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
9f8a554a074c ghcr.io/nextcloud-releases/aio-apache:beta "/start.sh /usr/bin/…" 7 hours ago Up 7 hours (healthy) 80/tcp, 0.0.0.0:11000->11000/tcp nextcloud-aio-apache
774380923a5f ghcr.io/nextcloud-releases/aio-nextcloud:beta "/start.sh /usr/bin/…" 7 hours ago Up 7 hours (healthy) 9000/tcp nextcloud-aio-nextcloud
647b5998985e ghcr.io/nextcloud-releases/aio-imaginary:beta "/start.sh" 7 hours ago Up 7 hours (healthy) nextcloud-aio-imaginary
5327d484b25f ghcr.io/nextcloud-releases/aio-redis:beta "/start.sh" 7 hours ago Up 7 hours (healthy) 6379/tcp nextcloud-aio-redis
cf28c4107116 ghcr.io/nextcloud-releases/aio-postgresql:beta "/start.sh" 7 hours ago Up 7 hours (healthy) 5432/tcp nextcloud-aio-database
d3b7991765c7 ghcr.io/nextcloud-releases/aio-notify-push:beta "/start.sh" 7 hours ago Up 7 hours (healthy) nextcloud-aio-notify-push
8fca57061507 ghcr.io/nextcloud-releases/aio-collabora:beta "/start.sh" 7 hours ago Up 3 minutes (healthy) 9980/tcp nextcloud-aio-collabora
5cd3f774d2d8 ghcr.io/nextcloud-releases/aio-borgbackup:beta "/start.sh" 7 hours ago Exited (0) 7 hours ago nextcloud-aio-borgbackup
44ad7ae5d8cf ghcr.io/nextcloud-releases/aio-watchtower:beta "/start.sh" 7 hours ago Exited (0) 7 hours ago nextcloud-aio-watchtower
dce6539aebf9 ghcr.io/nextcloud-releases/all-in-one:beta "/start.sh" 7 days ago Up 4 days (healthy) 80/tcp, 8443/tcp, 9000/tcp, 0.0.0.0:8080->8080/tcp nextcloud-aio-mastercontainer
root@vps:/etc# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
e31dc69be239 ghcr.io/nextcloud-releases/aio-apache:beta "/start.sh /usr/bin/…" 3 hours ago Up 3 hours (healthy) 80/tcp, 0.0.0.0:11000->11000/tcp nextcloud-aio-apache
867788b1dd45 ghcr.io/nextcloud-releases/aio-nextcloud:beta "/start.sh /usr/bin/…" 3 hours ago Up 3 hours (healthy) 9000/tcp nextcloud-aio-nextcloud
66b18d15b65a ghcr.io/nextcloud-releases/aio-imaginary:beta "/start.sh" 3 hours ago Up 3 hours (healthy) nextcloud-aio-imaginary
4ca28b0af465 ghcr.io/nextcloud-releases/aio-redis:beta "/start.sh" 3 hours ago Up 3 hours (healthy) 6379/tcp nextcloud-aio-redis
068c4f8c7315 ghcr.io/nextcloud-releases/aio-postgresql:beta "/start.sh" 3 hours ago Up 3 hours (healthy) 5432/tcp nextcloud-aio-database
c0506fe5b69b ghcr.io/nextcloud-releases/aio-notify-push:beta "/start.sh" 3 hours ago Up 3 hours (healthy) nextcloud-aio-notify-push
80bbd3a0d53b ghcr.io/nextcloud-releases/aio-collabora:beta "/start.sh" 3 hours ago Up 14 minutes (healthy) 9980/tcp nextcloud-aio-collabora
c283ccc50fc1 ghcr.io/nextcloud-releases/aio-borgbackup:beta "/start.sh" 3 hours ago Exited (0) 3 hours ago nextcloud-aio-borgbackup
5d2fa20a1ea2 ghcr.io/nextcloud-releases/aio-watchtower:beta "/start.sh" 3 hours ago Exited (0) 3 hours ago nextcloud-aio-watchtower
1e57110fd422 ghcr.io/nextcloud-releases/all-in-one:beta "/start.sh" 3 hours ago Up 3 hours (healthy) 80/tcp, 8443/tcp, 9000/tcp, 0.0.0.0:8080->8080/tcp nextcloud-aio-mastercontainer
Ok, in the time since my last post, we decided to spin up a new server. Same exact configuration on CPU, RAM, Drives, and model. Moved the necessary docker volumes and compose file over and spun it all up. So far, no crashes since doing that. Additionally the nextcloud-aio-collabora container is behaving.
Assuming this good behavior continues, I will close out the thread in a few days and consider it resolved by two things:
Unfortunately, I am still having “crashes” and 502 Bad Gateway errors. Even after moving to a new server and starting with fresh images. It does seem to be a slightly different crash though than before. It has now happened twice. I have logs somewhere, but am traveling at the moment so may not get to post them until later.
The nextcloud-aio-apache container is in a Created state, but not started. Just curious if anyone else has seen this Created status?
Here is what I see in docker ps:
root@vps:~# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
df3a42f1b6ab ghcr.io/nextcloud-releases/aio-apache:latest "/start.sh /usr/bin/…" 5 hours ago Created nextcloud-aio-apache
6779ac75f250 ghcr.io/nextcloud-releases/aio-nextcloud:latest "/start.sh /usr/bin/…" 5 hours ago Exited (137) 2 minutes ago 9000/tcp nextcloud-aio-nextcloud
c7a9e99f2467 ghcr.io/nextcloud-releases/aio-imaginary:latest "/start.sh" 5 hours ago Exited (0) 8 seconds ago nextcloud-aio-imaginary
b7c3b0b5c02a ghcr.io/nextcloud-releases/aio-redis:latest "/start.sh" 5 hours ago Exited (0) 8 seconds ago nextcloud-aio-redis
b1b3ca7ddb44 ghcr.io/nextcloud-releases/aio-postgresql:latest "/start.sh" 5 hours ago Exited (0) 7 seconds ago nextcloud-aio-database
da7dccd04873 ghcr.io/nextcloud-releases/aio-notify-push:latest "/start.sh" 5 hours ago Exited (143) 8 seconds ago nextcloud-aio-notify-push
0618f5ac2b33 ghcr.io/nextcloud-releases/aio-collabora:latest "/start.sh" 5 hours ago Exited (0) 7 seconds ago nextcloud-aio-collabora
c7df95de617c ghcr.io/nextcloud-releases/aio-borgbackup:latest "/start.sh" 5 hours ago Exited (0) 5 hours ago nextcloud-aio-borgbackup
95eb424e9eb8 ghcr.io/nextcloud-releases/aio-watchtower:latest "/start.sh" 5 hours ago Exited (0) 5 hours ago nextcloud-aio-watchtower
In order to fix it, I have to do the following:
nextcloud-aio-apache containerWell, still having the nextcloud-aio-apache container is in a Created state crash every 4 - 5 days. I finally realized it was inevitable and likely something I would just have to live with. So, I figured out how to restart everything via bash. Those commands are here. The docker ps -a are just so I can see the progress. The docker exec at the end will restart all the NextCloud AIO sub-containers.
cd /var/lib/docker
docker ps -a
docker container prune -f
docker ps -a
docker compose down
docker ps -a
docker rm -f $(docker container ls -q --filter name=nextcloud*)
docker ps -a
service docker restart
docker compose up -d --pull always
docker ps -a
docker exec -it nextcloud-aio-mastercontainer sudo -u www-data php /var/www/docker-aio/php/src/Cron/StartAndUpdateContainers.php
docker ps -a
From there I started thinking about how to automate this so I wasn’t having to manually do it every time the site crashed. It could be hours between when it crashed and when I noticed or someone messaged me. I figured a website checking script would probably do what I needed. I searched and found one and then adopted it in to a bash script.
Here is that checking script that also does the restart when it encounters a 503. It also sends me an email and text (Verizon email-to-text). I am using mutt/msmtp for this on Ubuntu sending through Gmail. I am not covering that setup, but can if someone really needs it.
#!/bin/bash
#Purpose = Checker to see if Storage site is up. If 502 error, restart docker.
#START
# Variables
RECIPIENT="DanGilbertTX@aol.com"
TEXTRECIPIENT="8888675309@vtext.com"
SUBJECT="Forced to reset 502 for Storage on $(date +%A", "%B" "%d", "%Y)"
MESSAGE="The script found a 502 error and executed the reset script on Storage for docker. Please check to make sure it worked."
NON502SUBJECT="The website is down for Storage for an unknwon reason on $(date +%A", "%B" "%d", "%Y)"
NON502MESSAGE="The website is down for Storage for some unknown reason. Please check it."
response=$(/usr/bin/curl -s -o /dev/null -w "%{http_code}" https://storage.myredactedsite.org/s/Shared)
if [ "${response}" == "200" ]; then
# Everything looks good. No need for a notification.
echo "Website is up and working!"
elif [ "${response}" == "502" ]; then
echo "502 error. Resetting docker."
cd /var/lib/docker
/usr/bin/docker container prune -f
/usr/bin/docker compose down
/usr/bin/docker rm -f $(docker container ls -q --filter name=nextcloud*)
/usr/sbin/service docker restart
/usr/bin/docker compose up -d --pull always
/usr/bin/docker exec -it nextcloud-aio-mastercontainer sudo -u www-data php /var/www/docker-aio/php/src/Cron/StartAndUpdateContainers.php
echo $MESSAGE | /usr/bin/mutt -F "/root/.muttrc" -s "$SUBJECT" "$RECIPIENT"
echo $MESSAGE | /usr/bin/mutt -F "/root/.muttrc" -s "$SUBJECT" "$TEXTRECIPIENT"
else
echo "Website is down!"
echo $NON502MESSAGE | /usr/bin/mutt -F "/root/.muttrc" -s "$NON502SUBJECT" "$RECIPIENT"
fi
After testing it multiple times to make sure it works and sends email/text, I added it to cron to run every 15 minutes. I figure that it as a very acceptable RTO.
Also, make sure to chmod 755 Storage.Website.Errors.sh so that bash can execute the script.
*/15 * * * * /root/Storage.Website.Errors.sh
NOTE: I am running it as root and that is “bad”, however I know the risks and decided on it anyway. YMMV. You do you boo.
Finally, I would LOVE to fix the root cause, but I can live with this solution for a long time. Especially since it is now “automated” to fix itself for the standard 502 crash I am experiencing. I also learned a bit about scripting for docker and NC AIO during this process, so that is a bonus.
Marking it solved for now even though the root cause is not remediated. There is a solution to restart the services upon failure that will suffice.