Need to reinstall from scratch? Containers not starting/removed after upgrade from 11.7 to 11.8 failed

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).

This is very incomplete. Last night’s update seems to have caused pretty bad failure. If I can provide any more information please let me know.

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • AIO 11.7/8 / Server version unknown (was removed)
  • Operating system and version (e.g., Ubuntu 24.04):
    • ubuntu 24.04/docker
  • Web server and version (e.g, Apache 2.4.25):
    • apache (latest AIO update))
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • AIO
  • PHP version (e.g, 8.3):
    • whichever got shipped with dockerised AIO 11.7
  • Is this the first time you’ve seen this error? (Yes / No):
    • Yes
  • When did this problem seem to first start?
    • apparently during last night's update
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • AIO
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • no.

Summary of the issue you are facing:

(1) AIO docker containers stopped and aren’t starting up, apparently since last night’s attempted update to 11.8.

(3) nextcloud-aio-nextcloud container was initially still present (though stopped). Several attempts in AIO Interface to stop and start the containers were unsuccessful and eventually the n-a-n container has disappeared completely, but still shows as stopped in AIO.

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

  1. Not sure it can be replicated. Seems pretty catastrophic.

  2. The N-a-n container has disappeared and AIO doesn’t seem able to recreate it.

Log entries

Nextcloud

Please let me know if I can provde any other logs (with a non-existent n-a-n container).

2025-09-18T16:33:35.345465846Z Trying to fix docker.sock permissions internally...
2025-09-18T16:33:35.349263102Z Creating docker group internally with id 984
2025-09-18T16:33:35.721547961Z e[0;31mYou've set AIO_COMMUNITY_CONTAINERS but the option was removed.
2025-09-18T16:33:35.721574119Z The community containers get managed via the AIO interface now.e[0m
2025-09-18T16:33:35.976494367Z e[0;92mInitial startup of Nextcloud All-in-One complete!
2025-09-18T16:33:35.976538095Z You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!
2025-09-18T16:33:35.976545200Z E.g. https://internal.ip.of.this.server:8080
2025-09-18T16:33:35.976549807Z ⚠️ 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-09-18T16:33:35.976555873Z 
2025-09-18T16:33:35.976559861Z 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-09-18T16:33:35.976565107Z https://your-domain-that-points-to-this-server.tld:8443e[0m
2025-09-18T16:33:36.271444099Z /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-09-18T16:33:36.271472673Z   import pkg_resources
2025-09-18T16:33:37.351729371Z ++ head -1 /mnt/docker-aio-config/data/daily_backup_time
2025-09-18T16:33:37.353875469Z + BACKUP_TIME=23:45
2025-09-18T16:33:37.353911390Z + export BACKUP_TIME
2025-09-18T16:33:37.353918415Z + export DAILY_BACKUP=1
2025-09-18T16:33:37.353923539Z + DAILY_BACKUP=1
2025-09-18T16:33:37.353929105Z ++ sed -n 2p /mnt/docker-aio-config/data/daily_backup_time
2025-09-18T16:33:37.358343387Z + '[' '' '!=' automaticUpdatesAreNotEnabled ']'
2025-09-18T16:33:37.358372433Z + export AUTOMATIC_UPDATES=1
2025-09-18T16:33:37.358377905Z + AUTOMATIC_UPDATES=1
2025-09-18T16:33:37.358382662Z ++ sed -n 3p /mnt/docker-aio-config/data/daily_backup_time
2025-09-18T16:33:37.359825081Z + '[' '' '!=' successNotificationsAreNotEnabled ']'
2025-09-18T16:33:37.359848023Z + export SEND_SUCCESS_NOTIFICATIONS=1
2025-09-18T16:33:37.359852935Z + SEND_SUCCESS_NOTIFICATIONS=1
2025-09-18T16:33:37.359857732Z + set +x
2025-09-18T16:33:37.405971507Z [18-Sep-2025 16:33:37] NOTICE: fpm is running, pid 189
2025-09-18T16:33:37.406009650Z [18-Sep-2025 16:33:37] NOTICE: ready to handle connections
2025-09-18T16:33:37.411271225Z [Thu Sep 18 16:33:37.410600 2025] [mpm_event:notice] [pid 183:tid 183] AH00489: Apache/2.4.65 (Unix) OpenSSL/3.5.2 configured -- resuming normal operations
2025-09-18T16:33:37.411297864Z [Thu Sep 18 16:33:37.410654 2025] [core:notice] [pid 183:tid 183] AH00094: Command line: 'httpd -D FOREGROUND'
2025-09-18T16:33:37.416555121Z {"level":"info","ts":1758213217.415861,"msg":"maxprocs: Leaving GOMAXPROCS=8: CPU quota undefined"}
2025-09-18T16:33:37.416577094Z {"level":"info","ts":1758213217.4160771,"msg":"GOMEMLIMIT is updated","package":"github.com/KimMachineGun/automemlimit/memlimit","GOMEMLIMIT":121269790310,"previous":9223372036854775807}
2025-09-18T16:33:37.416580811Z {"level":"info","ts":1758213217.416119,"msg":"using config from file","file":"/Caddyfile"}
2025-09-18T16:33:37.417571078Z {"level":"info","ts":1758213217.4174411,"msg":"adapted config to JSON","adapter":"caddyfile"}
2025-09-18T16:33:37.421124752Z {"level":"info","ts":1758213217.4206748,"msg":"serving initial configuration"}
2025-09-18T16:37:35.786919787Z Deleting duplicate sessions
2025-09-18T17:00:33.761806114Z NOTICE: PHP message: Slim Application Error
2025-09-18T17:00:33.761858738Z Type: GuzzleHttp\Exception\ClientException
2025-09-18T17:00:33.761867709Z Code: 404
2025-09-18T17:00:33.761873554Z Message: Client error: `GET http://127.0.0.1/v1.41/containers/nextcloud-aio-nextcloud/logs?stdout=true&stderr=true&timestamps=true` resulted in a `404 Not Found` response:
2025-09-18T17:00:33.761881535Z {"message":"No such container: nextcloud-aio-nextcloud"}
2025-09-18T17:00:33.761888056Z File: /var/www/docker-aio/php/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php
2025-09-18T17:00:33.761894127Z Line: 111
2025-09-18T17:00:33.761899611Z Trace: #0 /var/www/docker-aio/php/vendor/guzzlehttp/guzzle/src/Middleware.php(72): GuzzleHttp\Exception\RequestException::create(Object(GuzzleHttp\Psr7\Request), Object(GuzzleHttp\Psr7\Response), NULL, Array, NULL)
2025-09-18T17:00:33.761907060Z #1 /var/www/docker-aio/php/vendor/guzzlehttp/promises/src/Promise.php(209): GuzzleHttp\Middleware::{closure:{closure:{closure:GuzzleHttp\Middleware::httpErrors():60}:61}:67}(Object(GuzzleHttp\Psr7\Response))
2025-09-18T17:00:33.761914567Z #2 /var/www/docker-aio/php/vendor/guzzlehttp/promises/src/Promise.php(158): GuzzleHttp\Promise\Promise::callHandler(1, Object(GuzzleHttp\Psr7\Response), NULL)
2025-09-18T17:00:33.761921268Z #3 /var/www/docker-aio/php/vendor/guzzlehttp/promises/src/TaskQueue.php(52): GuzzleHttp\Promise\Promise::{closure:GuzzleHttp\Promise\Promise::settle():156}()
2025-09-18T17:00:33.761927927Z #4 /var/www/docker-aio/php/vendor/guzzlehttp/promises/src/Promise.php(251): GuzzleHttp\Promise\TaskQueue->run(true)
2025-09-18T17:00:33.761934188Z #5 /var/www/docker-aio/php/vendor/guzzlehttp/promises/src/Promise.php(227): GuzzleHttp\Promise\Promise->invokeWaitFn()
2025-09-18T17:00:33.761940338Z #6 /var/www/docker-aio/php/vendor/guzzlehttp/promises/src/Promise.php(272): GuzzleHttp\Promise\Promise->waitIfPending()
2025-09-18T17:00:33.761946286Z #7 /var/www/docker-aio/php/vendor/guzzlehttp/promises/src/Promise.php(229): GuzzleHttp\Promise\Promise->invokeWaitList()
2025-09-18T17:00:33.761952326Z #8 /var/www/docker-aio/php/vendor/guzzlehttp/promises/src/Promise.php(69): GuzzleHttp\Promise\Promise->waitIfPending()
2025-09-18T17:00:33.761958540Z #9 /var/www/docker-aio/php/vendor/guzzlehttp/guzzle/src/Client.php(189): GuzzleHttp\Promise\Promise->wait()
2025-09-18T17:00:33.761985961Z #10 /var/www/docker-aio/php/vendor/guzzlehttp/guzzle/src/ClientTrait.php(44): GuzzleHttp\Client->request('GET', 'http://127.0.0....', Array)
2025-09-18T17:00:33.761994350Z #11 /var/www/docker-aio/php/src/Docker/DockerActionManager.php(146): GuzzleHttp\Client->get('http://127.0.0....')
2025-09-18T17:00:33.761999035Z #12 /var/www/docker-aio/php/src/Controller/DockerController.php(71): AIO\Docker\DockerActionManager->GetLogs('nextcloud-aio-n...')
2025-09-18T17:00:33.762004195Z #13 /var/www/docker-aio/php/vendor/slim/slim/Slim/Handlers/Strategies/RequestResponse.php(39): AIO\Controller\DockerController->GetLogs(Object(GuzzleHttp\Psr7\ServerRequest), Object(GuzzleHttp\Psr7\Response), Array)
2025-09-18T17:00:33.762009665Z #14 /var/www/docker-aio/php/vendor/slim/slim/Slim/Routing/Route.php(362): Slim\Handlers\Strategies\RequestResponse->__invoke(Array, Object(GuzzleHttp\Psr7\ServerRequest), Object(GuzzleHttp\Psr7\Response), Array)
2025-09-18T17:00:33.762015164Z #15 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(73): Slim\Routing\Route->handle(Object(GuzzleHttp\Psr7\ServerRequest))
2025-09-18T17:00:33.762020082Z #16 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(73): Slim\MiddlewareDispatcher->handle(Object(GuzzleHttp\Psr7\ServerRequest))
2025-09-18T17:00:33.762025074Z #17 /var/www/docker-aio/php/vendor/slim/slim/Slim/Routing/Route.php(321): Slim\MiddlewareDispatcher->handle(Object(GuzzleHttp\Psr7\ServerRequest))
2025-09-18T17:00:33.762029722Z #18 /var/www/docker-aio/php/vendor/slim/slim/Slim/Routing/RouteRunner.php(74): Slim\Routing\Route->run(Object(GuzzleHttp\Psr7\ServerRequest))
2025-09-18T17:00:33.762034342Z #19 /var/www/docker-aio/php/vendor/slim/csrf/src/Guard.php(482): Slim\Routing\RouteRunner->handle(Object(GuzzleHttp\Psr7\ServerRequest))
2025-09-18T17:00:33.762039171Z #20 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(178): Slim\Csrf\Guard->process(Object(GuzzleHttp\Psr7\ServerRequest), Object(Slim\Routing\RouteRunner))
2025-09-18T17:00:33.762044551Z #21 /var/www/docker-aio/php/vendor/slim/twig-view/src/TwigMiddleware.php(117): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
2025-09-18T17:00:33.762049713Z #22 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(129): Slim\Views\TwigMiddleware->process(Object(GuzzleHttp\Psr7\ServerRequest), Object(Psr\Http\Server\RequestHandlerInterface@anonymous))
2025-09-18T17:00:33.762055986Z #23 /var/www/docker-aio/php/src/Middleware/AuthMiddleware.php(36): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
2025-09-18T17:00:33.762060993Z #24 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(283): AIO\Middleware\AuthMiddleware->__invoke(Object(GuzzleHttp\Psr7\ServerRequest), Object(Psr\Http\Server\RequestHandlerInterface@anonymous))
2025-09-18T17:00:33.762066504Z #25 /var/www/docker-aio/php/vendor/slim/slim/Slim/Middleware/ErrorMiddleware.php(77): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
2025-09-18T17:00:33.762077113Z #26 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(129): Slim\Middleware\ErrorMiddleware->process(Object(GuzzleHttp\Psr7\ServerRequest), Object(Psr\Http\Server\RequestHandlerInterface@anonymous))
2025-09-18T17:00:33.762082519Z #27 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(73): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
2025-09-18T17:00:33.762087452Z #28 /var/www/docker-aio/php/vendor/slim/slim/Slim/App.php(209): Slim\MiddlewareDispatcher->handle(Object(GuzzleHttp\Psr7\ServerRequest))
2025-09-18T17:00:33.762092154Z #29 /var/www/docker-aio/php/vendor/slim/slim/Slim/App.php(193): Slim\App->handle(Object(GuzzleHttp\Psr7\ServerRequest))
2025-09-18T17:00:33.762096694Z #30 /var/www/docker-aio/php/public/index.php(198): Slim\App->run()
2025-09-18T17:00:33.762101144Z #31 {main}
2025-09-18T17:00:33.762104943Z Tips: To display error details in HTTP response set "displayErrorDetails" to true in the ErrorHandler constructor.

Web Browser

If the problem is related to the Web interface, open your browser inspector Console and Network tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.

PASTE

Web server / Reverse Proxy

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

PASTE HERE

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!):

inaccessible


Apps

The output of occ app:list (if possible).

Tips for increasing the likelihood of a response

  • Use the preformatted text formatting option in the editor for all log entries and configuration output.
  • If screenshots are useful, feel free to include them.
    • If possible, also include key error output in text form so it can be searched for.
  • Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.

This is the method I have been using for a long time to update Nextcloud AIO:
:backhand_index_pointing_right: Link to the procedure

Today I updated from 11.7.0 → 11.8.0 using the same approach on three different servers, and everything went smoothly without any issues.

It’s important to keep in mind that when a new release comes out, the source server is often overloaded. This means that pulling the Docker images that are part of the AIO package can take considerably longer. Another factor is, of course, the internet connection speed of the server itself.

Examples from my case:

  • Server 1 – update took about 20 minutes

  • Servers 2 and 3 – updates took almost 50 minutes

I am not sure about this. The images are hosted on ghcr.io this would mean AIO overloads GitHubs infrastructure? I doubt it…

1 Like

Thanks for your quick replies.

One day later and bracing myself for a clean reinstall, everything seems to be working like a charm.

How very strange and pleasant!

1 Like

Similar issue here.. While upgrading to 11.8.0 all containers came up except for Apache, which is in yellow and it’s marked as (starting). delete apache container and re-started containers. the system rebuild the apache container but still stuck at starting. however im able to access nextcloud either via the local ip and also via my web domain.

when i click on logs on the apache container, this is what i get:

2025-09-24T05:02:18.741257198Z Waiting for Nextcloud to start...
2025-09-24T05:02:23.749798460Z Connection to nextcloud-aio-nextcloud (172.18.0.12) 9000 port [tcp/*] succeeded!
2025-09-24T05:02:24.234787934Z /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-09-24T05:02:24.234829176Z   import pkg_resources
2025-09-24T05:02:25.336634330Z [Wed Sep 24 05:02:25.336009 2025] [mpm_event:notice] [pid 44:tid 44] AH00489: Apache/2.4.65 (Unix) configured -- resuming normal operations
2025-09-24T05:02:25.336683702Z [Wed Sep 24 05:02:25.336065 2025] [core:notice] [pid 44:tid 44] AH00094: Command line: '/usr/local/apache2/bin/httpd -D FOREGROUND'
2025-09-24T05:02:25.353513406Z {"level":"info","ts":1758690145.353277,"msg":"maxprocs: Leaving GOMAXPROCS=48: CPU quota undefined"}
2025-09-24T05:02:25.353939772Z {"level":"info","ts":1758690145.353601,"msg":"GOMEMLIMIT is updated","package":"github.com/KimMachineGun/automemlimit/memlimit","GOMEMLIMIT":151783147929,"previous":9223372036854775807}
2025-09-24T05:02:25.354003275Z {"level":"info","ts":1758690145.3536415,"msg":"using config from file","file":"/tmp/Caddyfile"}
2025-09-24T05:02:25.356404477Z {"level":"info","ts":1758690145.3561082,"msg":"adapted config to JSON","adapter":"caddyfile"}
2025-09-24T05:02:25.370012987Z {"level":"info","ts":1758690145.36968,"msg":"serving initial configuration"}


Any ideas ?

In addition to deleting Apache docker, did you also delete the Apache installation image?

Thanks for replying. I wouldn’t know how to delete the installation image. Also, did not want to delete things on the risk it might break the whole installation.

Running nextcloud AIO on an UnRaid server.

funny thing is everything appears to be working.

Im still able to access nextcloud via the web.

Error logs show this:

Error index NotPermittedExceptionCould not create folder “/appdata_oc2gmu9fypgs/appstore/app-discover-cache/68d3cf31-92a”, folder exists but unable to get cache entry
Debug admin_audit RuntimeExceptionThe loading of lazy AppConfig values have been triggered by app “admin_audit”

also from my cloudflare tunnel client:

025-09-24T11:04:24Z ERR error=“stream 1877 canceled by remote with error code 0” connIndex=3 event=1 ingressRule=0 originService=http://192.168.1.210:11000

Im always scared to update as things always break after an update.

You can find my tutorial here - Nextcloud AIO v10.1.1 - Apache Will Not Start - #19 by vawaver

hi, not using portainer but i figured your guide could be applied same way.

under unraid:

Deleted the apache image.

found bunch of orphaned images left from previous installs i guess and deleted those.

Went back to the containers page and now it says i have an update. It recreated apache container.

it now upgraded to 11.9.0

However, apache container still shows in yellow (starting) even though everything seems to be working.

on your guide it says to delete all containers, but i dont want to loose my configuration.

What container holds the configuration and which containers are ok to delete ?

nextcloud-aio-apache
started

nextcloud-aio-clamav
started

nextcloud-aio-collabora
started

nextcloud-aio-database
started

nextcloud-aio-fulltextsearch
started

nextcloud-aio-imaginary
started

nextcloud-aio-mastercontainer
started

nextcloud-aio-nextcloud
started

nextcloud-aio-notify-push
started

nextcloud-aio-redis
started

nextcloud-aio-talk
started

You don’t need to worry about deleting containers. In Docker, containers are just the “running instances.” All the important stuff — your database, Nextcloud config, settings — is stored in persistent volumes.

That means:

  • You can safely remove any of the Nextcloud AIO containers.

  • When you run docker compose up -d again, they will be recreated automatically.

  • As long as you don’t touch the volumes, none of your data or configuration will be lost.

So if something looks broken, removing containers is fine.

The only thing you must never delete are the volumes — that’s where your data lives.