Ok, so checking docker images, it seems that everything was pulled but the Nextcloud latest version. I manually pulled Nextcloud latest version and restarted the update process. It seems to have worked on updating the instance to the latest version but hit quiet some issues like all apps were deactivated and it in order to activate base apps like Calendar i had to allow Untested apps.
I still see this though…
Im not sure this is the best workaround
I used a snapshot of the server to restore to an earlier date and to Nextcloud AIO v9.6.0 again. I waited 2 days considering the limits i hit earlier but i still have the same issue. Is there something wrong with the updater?
Even registering a free account with docker hub did not solve the issue. I doubt it is docker hub related. After running update and start the containers, it does not pull the new containers.
REPOSITORY TAG IMAGE ID CREATED SIZE
nextcloud/all-in-one latest e9ce9a27aefa 2 weeks ago 245MB
nextcloud/aio-watchtower latest cd447ea281c8 2 weeks ago 29MB
nextcloud/aio-borgbackup latest 1ea28b89b336 2 weeks ago 72.7MB
nextcloud/aio-nextcloud latest 6049c2e90ab8 2 months ago 1.06GB
nextcloud/aio-imaginary latest 8a81119e8ae5 2 months ago 126MB
nextcloud/aio-collabora latest 26f4d77ac1a4 2 months ago 1.42GB
nextcloud/aio-talk-recording latest 307117ced11a 2 months ago 528MB
nextcloud/aio-talk latest a00c4bac1c45 2 months ago 162MB
nextcloud/aio-fulltextsearch latest 517d7f628ae7 2 months ago 1.27GB
nextcloud/aio-postgresql latest 237b9093e62b 2 months ago 246MB
nextcloud/aio-apache latest 029156775f62 2 months ago 173MB
nextcloud/aio-clamav latest eaa7cd1bc516 2 months ago 320MB
nextcloud/aio-notify-push latest 18ea26374a47 2 months ago 11MB
nextcloud/aio-watchtower 2a9b21c6caca 2 months ago 23.2MB
nextcloud/aio-redis latest e7575f791c1f 2 months ago 43.5MB
This error keeps poping up:
024-11-30T10:45:26.933613386Z Tips: To display error details in HTTP response set "displayErrorDetails" to true in the ErrorHandler constructor.
2024-11-30T10:45:27.509784674Z NOTICE: PHP message: 404 Not Found
2024-11-30T10:45:27.509817925Z Type: Slim\Exception\HttpNotFoundException
2024-11-30T10:45:27.509834433Z Code: 404
2024-11-30T10:45:27.509837368Z Message: Not found.
2024-11-30T10:45:27.509839805Z File: /var/www/docker-aio/php/vendor/slim/slim/Slim/Middleware/RoutingMiddleware.php
2024-11-30T10:45:27.509842351Z Line: 76
2024-11-30T10:45:27.509844796Z Trace: #0 /var/www/docker-aio/php/vendor/slim/slim/Slim/Routing/RouteRunner.php(62): Slim\Middleware\RoutingMiddleware->performRouting(Object(GuzzleHttp\Psr7\ServerRequest))
2024-11-30T10:45:27.509848078Z #1 /var/www/docker-aio/php/vendor/slim/csrf/src/Guard.php(482): Slim\Routing\RouteRunner->handle(Object(GuzzleHttp\Psr7\ServerRequest))
2024-11-30T10:45:27.509850786Z #2 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(177): Slim\Csrf\Guard->process(Object(GuzzleHttp\Psr7\ServerRequest), Object(Slim\Routing\RouteRunner))
2024-11-30T10:45:27.509853592Z #3 /var/www/docker-aio/php/vendor/slim/twig-view/src/TwigMiddleware.php(117): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
2024-11-30T10:45:27.509856331Z #4 /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))
2024-11-30T10:45:27.509859214Z #5 /var/www/docker-aio/php/src/Middleware/AuthMiddleware.php(36): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
2024-11-30T10:45:27.509861954Z #6 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(280): AIO\Middleware\AuthMiddleware->__invoke(Object(GuzzleHttp\Psr7\ServerRequest), Object(Psr\Http\Server\RequestHandlerInterface@anonymous))
2024-11-30T10:45:27.509864893Z #7 /var/www/docker-aio/php/vendor/slim/slim/Slim/Middleware/ErrorMiddleware.php(77): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
2024-11-30T10:45:27.509867628Z #8 /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))
2024-11-30T10:45:27.509870523Z #9 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(73): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
2024-11-30T10:45:27.509874676Z #10 /var/www/docker-aio/php/vendor/slim/slim/Slim/App.php(209): Slim\MiddlewareDispatcher->handle(Object(GuzzleHttp\Psr7\ServerRequest))
2024-11-30T10:45:27.509877291Z #11 /var/www/docker-aio/php/vendor/slim/slim/Slim/App.php(193): Slim\App->handle(Object(GuzzleHttp\Psr7\ServerRequest))
2024-11-30T10:45:27.509879913Z #12 /var/www/docker-aio/php/public/index.php(188): Slim\App->run()
2024-11-30T10:45:27.509882498Z #13 {main}
Does not seem to autoupdate so i used this workaround. Curious to see what happens on the next update, ill try.
Stopped the containers. Pulled every container latest image from inside the server and then started the update. Updated and enabled the apps I had before the update, and it’s working fine.
Thanks for all the assistance.
How come you did not have 9.8? For future reference: Is it possible to upgrade step by step instead of straight to 10.0?
I also had alot of issues updating , i got around it when i found someone found the ind commands to stop the containers directly, instead of in the AIO dash. after i did that and retried the update on the dash, it got me to the OP’s , of doing it, and then it showing still needed updated. i did 3 times, nad the last time worked. (assuming step by step updates) like i got 3 or 5 updates behind. (tho i run updater on the command line every few days. (tho still have to update the AIO seperately, which …)
It usually jumps to the latest version.
Are you hosting on Digital Ocean? I never had this issue on Hetzner. I dont know if i mentioned it above but i had to create a dockerhub account and use that to pull instead of anonymously to bypass the limit rate.
nope. self hosting.
if server is up, and clients connected, i often cant SSH in. if i can ssh, the clients arent connected.
if both are unavailable, i reset. then update in terminal, and a few hours, clients connect. /shrug
AIO was easy to install, harder to maintain than other setups ive tried. But its working 
My experience has been different, AIO saved me tons of time manually updating everything. This was the only time i hit this issue which is weird but i blame DO 
. Your ssh issue is very weird though, it should not be related to Nextcloud.