Updated to AIO 11.10.0, now my Apache container is stuck on "starting..."

Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. :heart:

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • AIO 11.10.0
  • Operating system and version (e.g., Ubuntu 24.04):
    • Unraid 7.1.4
  • Web server and version (e.g, Apache 2.4.25):
    • Apache container
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • using Cloudflare Tunnel
  • PHP version (e.g, 8.3):
    • whatever the container installed
  • Is this the first time you’ve seen this error? (Yes / No):
    • yes
  • When did this problem seem to first start?
    • right after updating to 11.10.0
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • docker on Unraid
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • Cloudflare tunnel

Summary of the issue you are facing:

First I made a backup with Borg, then I pushed the button on the main AIO interface page (the one on port 7282) to update to new version. It says the update was successful, but the Apache container is stuck on “Starting.” Checking the Docker tab on Unraid shows that all containers are running except for nextcloud-aio-borgbackup and -watchtower, which are both stopped.

Incredibly, I can still access Nextcloud though the usual domain, and it seems to be working just fine.

Steps to replicate it (hint: details matter!):

Log entries

Web server / Reverse Proxy

The output of your Apache log in /var/log/____:

2025-10-19T09:37:06.080377981Z Waiting for Nextcloud to start...
2025-10-19T09:37:11.083501286Z Waiting for Nextcloud to start...
2025-10-19T09:37:16.085967071Z Waiting for Nextcloud to start...
2025-10-19T09:37:21.089914957Z Waiting for Nextcloud to start...
2025-10-19T09:37:26.092095435Z Connection to nextcloud-aio-nextcloud (172.19.0.10) 9000 port [tcp/*] succeeded!
2025-10-19T09:37:26.335628284Z /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-10-19T09:37:26.335655558Z   import pkg_resources
2025-10-19T09:37:27.394351239Z {"level":"info","ts":1760866647.393801,"msg":"maxprocs: Leaving GOMAXPROCS=12: CPU quota undefined"}
2025-10-19T09:37:27.394568814Z {"level":"info","ts":1760866647.3940475,"msg":"GOMEMLIMIT is updated","package":"github.com/KimMachineGun/automemlimit/memlimit","GOMEMLIMIT":30094995456,"previous":9223372036854775807}
2025-10-19T09:37:27.394593089Z {"level":"info","ts":1760866647.3940961,"msg":"using config from file","file":"/tmp/Caddyfile"}
2025-10-19T09:37:27.395995163Z {"level":"info","ts":1760866647.395784,"msg":"adapted config to JSON","adapter":"caddyfile"}
2025-10-19T09:37:27.399382565Z [Sun Oct 19 09:37:27.399195 2025] [mpm_event:notice] [pid 45:tid 45] AH00489: Apache/2.4.65 (Unix) configured -- resuming normal operations
2025-10-19T09:37:27.399407655Z [Sun Oct 19 09:37:27.399224 2025] [core:notice] [pid 45:tid 45] AH00094: Command line: '/usr/local/apache2/bin/httpd -D FOREGROUND'
2025-10-19T09:37:27.403380335Z {"level":"info","ts":1760866647.402989,"msg":"serving initial configuration"}


Configuration

Nextcloud

The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):

Not sure where to find it, sorry

Yeah, so that’s it. Weird that nextcloud is still running but not running according to the main interface. I’m pretty new to this stuff, so any help would be super appreciated! Thank you in advance!

Hey,
check my post here- Nextcloud AIO v10.1.1 - Apache Will Not Start - #19 by vawaver

Hey, thanks for replying to this so quick. Wish I could have done the same…

Just want to check one thing:

    1. Stop all containers as usual.
    2. Delete all stopped containers in Portainer, including the problematic one.

Do you mean ALL stopped containers, including the mastercontainer?

It was good point. I have added info to the tutorial.
Of course exclude nextcloud-aio-mastercontainer.
It must remain the only one running.
Otherwise, it is impossible to start containers from Nextcloud AIO admin interface.

Yeah, sorry, just my neuro-spiciness rearing its head. :wink:

I guess one more thing. Since there is no way for me to stop the containers on the AIO page, is it okay for me to go to my Unraid Docker settings page and stop them there? And if i do that, will i need to stop and restart the mastercontainer to update the AIO settings page?

I don’t have experience with Unraid, so if you have the option to stop the containers directly from the Docker settings page, go ahead and do that. I’m not aware of a situation where you can’t stop containers from the AIO interface — maybe that’s specific to Unraid.

You can also restart the mastercontainer if you want; there’s nothing wrong with that.

Hi again,

So I followed your advice, stopped everything, deleted all other containers, deleted the image for the container “wouldn’t start” (apache) and restarted…. and right back to where I started, except now on the Unraid Docker control panel it says there is an update for the mastercontainer and would I like Unraid to update it for me?

It just blows my mind that through all this, the apache container is in fact running just fine. It just can’t seem to convince the AIO admin page that it is. Maybe you’re right: maybe this is an Unraid problem…

I don’t have any experience with Unraid, so I can’t really comment on how its Docker integration behaves internally. But if Unraid is offering an update for the mastercontainer, it should be safe to apply it — that’s basically the same as pulling the latest image manually.

Well, isn’t this interesting?

So I stopped the containers (except master), and clicked the button for Unraid to upgrade the master. The log said it was already running the most up-to-date version of Nextcloud, so it just exited. At least then the flag on the control panel finally switched from “click to update” to “up-to-date”.

But then, lo and behold, the AIO admin page finally acknowledged that all containers were running! This doesn’t really make sense to me, but there we are.

Thank you so much for your advice! What a long, strange trip it’s been…

1 Like