AIO NC does no longer start: Slim Application Error

The Basics

  • Is this the first time you’ve seen this error? (Yes / No):
    • yes
  • When did this problem seem to first start?
    • yesterday
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • AIO on Linux Mint
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • no

Summary of the issue you are facing:

Cannot access management interface at <local ip>/8080. Nextcloud stopped working.
Bare with me I’m a beginner. Both with Nextcloud as with docker.
I’ve installed Nextcloud a month ago and it has been running fine up to yesterday. I have made backups but first like to understand how I can fix this in the easy way.
As I could not access the web interface I stopped all docker instances from the commandline. Then I started only nextcloud-aio-mastercontainer again.
What I’ve found is the output of docker logs nextcloud-aio-mastercontainer

NOTICE: PHP message: Slim Application Error
Type: Exception
Code: 0
Message: Could not create the nextcloud-aio network: {"message":"client version 1.41 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version"

This sound easy but I have no clue what client is meant here. I tried several commands but cannot find anything containing the version 1.41 (and I cannot use the web interface)
I’m afraid to purge anything as the installation contains 150GB photos.
The output of docker network inspect nextcloud-aio is

[
    {
        "Name": "nextcloud-aio",
        "Id": "cfed52b4ca3d3374f91fa4d0fa491613fb3dd68bfbf88535ea2b9442bcbab017",
        "Created": "2025-10-05T12:12:08.866278153+02:00",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv4": true,
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": [
                {
                    "Subnet": "172.18.0.0/16",
                    "IPRange": "",
                    "Gateway": "172.18.0.1"
                }
            ]
        },
        "Internal": false,
        "Attachable": false,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Options": {},
        "Labels": {},
        "Containers": {
            "6ec37afa9eeb9fc54b4411ec5684b105d768fc1207b59c3d0893458f5cd4bed9": {
                "Name": "nextcloud-aio-mastercontainer",
                "EndpointID": "80690d18759df88d85a1defa0f237bad843eaf2b58eb83717ed97329b57c0c59",
                "MacAddress": "de:ab:9b:76:bb:d7",
                "IPv4Address": "172.18.0.2/16",
                "IPv6Address": ""
            }
        },
        "Status": {
            "IPAM": {
                "Subnets": {
                    "172.18.0.0/16": {
                        "IPsInUse": 4,
                        "DynamicIPsAvailable": 65532
                    }
                }
            }
        }
    }
]

And why would this happen all of a sudden? I was not updating anything.
I hope someone can help with some guidance on the next step in trouble shooting.

This is a bug. See Latest AIO mastercontainer fails with latest Docker · Issue #7096 · nextcloud/all-in-one · GitHub

1 Like

Ah thanks!
So docker got updated. Now I realize I have automated updates enabled for host OS and that indeed ran yesterday.
I would not have thought this could actually break a running instance.

I think I’ve now downgraded all relevant packages:

apt-get install docker-ce=5:28.5.2-1~debian.13~trixie
apt-get install docker-ce-cli=5:28.5.2-1~debian.13~trixie
apt-get install docker-ce-rootless-extras=5:28.5.2-1~debian.13~trixie
apt-get install containerd.io=1.7.29-1~debian.13~trixie

I still get the same error message (client version 1.41 is too old. Minimum supported API version is 1.44).
Apparently there is another package involved as docker version shows this:

docker version
Client: Docker Engine - Community
 Version:           28.5.2
 API version:       1.51
 Go version:        go1.25.3
 Git commit:        ecc6942
 Built:             Wed Nov  5 14:43:33 2025
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          29.0.0
  API version:      1.52 (minimum version 1.44)
  Go version:       go1.25.4
  Git commit:       d105562
  Built:            Mon Nov 10 21:46:28 2025
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.7.29
  GitCommit:        442cb34bda9a6a0fed82a2ca7cade05c5c749582
 runc:
  Version:          1.3.3
  GitCommit:        v1.3.3-0-gd842d771
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

I downgraded the package updates from the last three days (except intel-microcode and the webcam..):

fswebcam
containerd.io
intel-microcode
docker-ce-rootless-extras
docker-ce
docker-ce-cli

This might not entirely be Nextcloud related, but more users might stumble on this issue and probable search for a quick way to fix as well.

1 Like

I think automatic updates reverted the packages :sleeping_face:
The commands to revert are correct though:

apt list -a docker-ce docker-ce-cli docker-ce-rootless-extras containerd.io 
Listing... Done
containerd.io/trixie 2.1.5-1~debian.13~trixie amd64 [upgradable from: 1.7.29-1~debian.13~trixie]
containerd.io/trixie,now 1.7.29-1~debian.13~trixie amd64 [installed,upgradable to: 2.1.5-1~debian.13~trixie]
containerd.io/trixie 1.7.28-2~debian.13~trixie amd64
containerd.io/trixie 1.7.28-1~debian.13~trixie amd64
containerd.io/trixie 1.7.28-0~debian.13~trixie amd64
containerd.io/trixie 1.7.27-1 amd64

docker-ce-cli/trixie 5:29.0.0-1~debian.13~trixie amd64 [upgradable from: 5:28.5.2-1~debian.13~trixie]
docker-ce-cli/trixie,now 5:28.5.2-1~debian.13~trixie amd64 [installed,upgradable to: 5:29.0.0-1~debian.13~trixie]
docker-ce-cli/trixie 5:28.5.1-1~debian.13~trixie amd64
docker-ce-cli/trixie 5:28.5.0-1~debian.13~trixie amd64
docker-ce-cli/trixie 5:28.4.0-1~debian.13~trixie amd64
docker-ce-cli/trixie 5:28.3.3-1~debian.13~trixie amd64
docker-ce-cli/trixie 5:28.3.2-1~debian.13~trixie amd64
docker-ce-cli/trixie 5:28.3.1-1~debian.13~trixie amd64
docker-ce-cli/trixie 5:28.3.0-1~debian.13~trixie amd64
docker-ce-cli/trixie 5:28.2.2-1~debian.13~trixie amd64
docker-ce-cli/trixie 5:28.2.1-1~debian.13~trixie amd64
docker-ce-cli/trixie 5:28.2.0-1~debian.13~trixie amd64
docker-ce-cli/trixie 5:28.1.1-1~debian.13~trixie amd64
docker-ce-cli/trixie 5:28.1.0-1~debian.13~trixie amd64

docker-ce-rootless-extras/trixie 5:29.0.0-1~debian.13~trixie amd64 [upgradable from: 5:28.5.2-1~debian.13~trixie]
docker-ce-rootless-extras/trixie,now 5:28.5.2-1~debian.13~trixie amd64 [installed,upgradable to: 5:29.0.0-1~debian.13~trixie]
docker-ce-rootless-extras/trixie 5:28.5.1-1~debian.13~trixie amd64
docker-ce-rootless-extras/trixie 5:28.5.0-1~debian.13~trixie amd64
docker-ce-rootless-extras/trixie 5:28.4.0-1~debian.13~trixie amd64
docker-ce-rootless-extras/trixie 5:28.3.3-1~debian.13~trixie amd64
docker-ce-rootless-extras/trixie 5:28.3.2-1~debian.13~trixie amd64
docker-ce-rootless-extras/trixie 5:28.3.1-1~debian.13~trixie amd64
docker-ce-rootless-extras/trixie 5:28.3.0-1~debian.13~trixie amd64
docker-ce-rootless-extras/trixie 5:28.2.2-1~debian.13~trixie amd64
docker-ce-rootless-extras/trixie 5:28.2.1-1~debian.13~trixie amd64
docker-ce-rootless-extras/trixie 5:28.2.0-1~debian.13~trixie amd64
docker-ce-rootless-extras/trixie 5:28.1.1-1~debian.13~trixie amd64
docker-ce-rootless-extras/trixie 5:28.1.0-1~debian.13~trixie amd64

docker-ce/trixie 5:29.0.0-1~debian.13~trixie amd64 [upgradable from: 5:28.5.2-1~debian.13~trixie]
docker-ce/trixie,now 5:28.5.2-1~debian.13~trixie amd64 [installed,upgradable to: 5:29.0.0-1~debian.13~trixie]
docker-ce/trixie 5:28.5.1-1~debian.13~trixie amd64
docker-ce/trixie 5:28.5.0-1~debian.13~trixie amd64
docker-ce/trixie 5:28.4.0-1~debian.13~trixie amd64
docker-ce/trixie 5:28.3.3-1~debian.13~trixie amd64
docker-ce/trixie 5:28.3.2-1~debian.13~trixie amd64
docker-ce/trixie 5:28.3.1-1~debian.13~trixie amd64
docker-ce/trixie 5:28.3.0-1~debian.13~trixie amd64
docker-ce/trixie 5:28.2.2-1~debian.13~trixie amd64
docker-ce/trixie 5:28.2.1-1~debian.13~trixie amd64
docker-ce/trixie 5:28.2.0-1~debian.13~trixie amd64
docker-ce/trixie 5:28.1.1-1~debian.13~trixie amd64
docker-ce/trixie 5:28.1.0-1~debian.13~trixie amd64

Nextcloud runs again…

This should prevent the packages from being upgraded:

apt-mark hold docker-ce docker-ce-cli docker-ce-rootless-extras

And this allows them to be upgraded again once the issues with the new version have been fixed.

apt-mark unhold docker-ce docker-ce-cli docker-ce-rootless-extras
3 Likes

fab! I had exactly this too! I recon something similar to this its only on lxc containers which I have too but my nextcloud on a vps server…apt install -y --allow-downgrades containerd.io=1.7.28-1~debian.13~trixie

same problem here and i have also downgrade version:

sudo apt-mark hold docker-ce docker-ce-cli containerd.io

root@omvba ~ [SIGINT]# docker version
Client: Docker Engine - Community
Version: 28.5.2
API version: 1.51
Go version: go1.25.3
Git commit: ecc6942
Built: Wed Nov 5 14:43:25 2025
OS/Arch: linux/amd64
Context: default

Server: Docker Engine - Community
Engine:
Version: 28.5.2
API version: 1.51 (minimum version 1.24)
Go version: go1.25.3
Git commit: 89c5e8f
Built: Wed Nov 5 14:43:25 2025
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: v1.7.29
GitCommit: 442cb34bda9a6a0fed82a2ca7cade05c5c749582
runc:
Version: 1.3.3
GitCommit: v1.3.3-0-gd842d771
docker-init:
Version: 0.19.0
GitCommit: de40ad0

but now i have rabbitmq not starting in onlyoffice

root@omvba ~ [SIGPIPE|2]# docker logs nextcloud-aio-onlyoffice -n 10
Waiting for connection to the localhost host on port 5672
Waiting for connection to the localhost host on port 5672
Waiting for connection to the localhost host on port 5672
Waiting for connection to the localhost host on port 5672
Waiting for connection to the localhost host on port 5672
Waiting for connection to the localhost host on port 5672
Waiting for connection to the localhost host on port 5672
Waiting for connection to the localhost host on port 5672
Waiting for connection to the localhost host on port 5672
Waiting for connection to the localhost host on port 5672

root@omvba ~# docker logs nextcloud-aio-nextcloud -n 10
Waiting for OnlyOffice to become available…
Waiting for OnlyOffice to become available…
Waiting for OnlyOffice to become available…
Waiting for OnlyOffice to become available…
Waiting for OnlyOffice to become available…
Waiting for OnlyOffice to become available…
Waiting for OnlyOffice to become available…
Waiting for OnlyOffice to become available…
Waiting for OnlyOffice to become available…
Waiting for OnlyOffice to become available…

How can i solve that?

in olyoffice container i got this error:

find: ‘/var/www/onlyoffice/Data/certs’: No such file or directory
/etc/init.d/rabbitmq-server: 10: ulimit: error setting limit (Operation not permitted)
Connection to localhost (::1) 5432 port [tcp/postgresql] succeeded!

root@omvba ~# docker logs nextcloud-aio-notify-push -n 10
Waiting for Nextcloud to start…
Waiting for Nextcloud to start…
Waiting for Nextcloud to start…
Waiting for Nextcloud to start…
Waiting for Nextcloud to start…
Waiting for Nextcloud to start…
Waiting for Nextcloud to start…
Waiting for Nextcloud to start…
Waiting for Nextcloud to start…
Waiting for Nextcloud to start…

root@omvba ~ [0|1]# docker logs nextcloud-aio-redis -n 10
1:signal-handler (1762898941) Received SIGTERM scheduling shutdown…
1:M 11 Nov 2025 22:09:01.113 # Redis is now ready to exit, bye bye…
Memory overcommit is disabled but necessary for safe operation
See https://github.com/nextcloud/all-in-one/discussions/1731 how to enable overcommit
Redis has started
1:C 11 Nov 2025 22:14:03.259 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see vm.max_map_count growing steadily when vm.overcommit_memory is 2 · Issue #1328 · jemalloc/jemalloc · GitHub . To fix this issue add ‘vm.overcommit_memory = 1’ to /etc/sysctl.conf and then reboot or run the command ‘sysctl vm.overcommit_memory=1’ for this to take effect.
Memory overcommit is disabled but necessary for safe operation
See Redis: Warning `Memory overcommit must be enabled` · nextcloud/all-in-one · Discussion #1731 · GitHub how to enable overcommit
Redis has started
1:C 11 Nov 2025 22:28:49.193 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see vm.max_map_count growing steadily when vm.overcommit_memory is 2 · Issue #1328 · jemalloc/jemalloc · GitHub . To fix this issue add ‘vm.overcommit_memory = 1’ to /etc/sysctl.conf and then reboot or run the command ‘sysctl vm.overcommit_memory=1’ for this to take effect.

root@omvba ~# docker logs nextcloud-aio-apache -n 10
Waiting for Nextcloud to start…
Waiting for Nextcloud to start…
Waiting for Nextcloud to start…
Waiting for Nextcloud to start…
Waiting for Nextcloud to start…
Waiting for Nextcloud to start…
Waiting for Nextcloud to start…
Waiting for Nextcloud to start…
Waiting for Nextcloud to start…
Waiting for Nextcloud to start…

@szaimen how to solve that?

Does the Community-Docker-Image suffer from the same problem?

i had to startup the rabbitmq with command rabbitmq-server -detached.

but if reboot the nas server then i stuck in the same problem @szaimen

In my case, it seems the following command allowed me to access the AIO interface:

sudo docker exec nextcloud-aio-mastercontainer bash -lc "sed -i 's/1.41/1.44/g' /var/www/docker-aio/php/src/Docker/DockerActionManager.php"

While we wait for the next official image, I assume this is a safe way to restore normality. Correct me if I’m wrong!

5 Likes

Yes, that should solve the issue with the AIO container. For those with other containers that are not yet compatible with the new API, the following might be a better solution: Latest AIO mastercontainer fails with latest Docker · Issue #7096 · nextcloud/all-in-one · GitHub

However, if I understand correctly, both of the above workarounds only change the API version that the container, or Docker service, expects. If functions have actually been removed from Docker that a container still wants to use, problems may still arise. Therefore, the safest solution would probably still be to downgrade Docker until the issues are resolved.

Here are my notes on how to do this:

:warning: I created these for an older version of Docker because of a problem with Mailcow at the time. So don’t forget to adjust the version numbers accordingly!

Downgrade packages

Show old versions:

apt-cache policy docker-ce
apt-cache policy docker-ce-cli
apt-cache policy docker-ce-rootless-extras

Example output:

docker-ce:
  Installiert:           5:24.0.0-1~debian.11~bullseye
  Installationskandidat: 5:24.0.0-1~debian.11~bullseye
  Versionstabelle:
 *** 5:24.0.0-1~debian.11~bullseye 500
        500 https://download.docker.com/linux/debian bullseye/stable amd64 Packages
        100 /var/lib/dpkg/status
     5:23.0.6-1~debian.11~bullseye 500
        500 https://download.docker.com/linux/debian bullseye/stable amd64 Packages
     5:23.0.5-1~debian.11~bullseye 500
        500 https://download.docker.com/linux/debian bullseye/stable amd64 Packages
     5:23.0.4-1~debian.11~bullseye 500
        500 https://download.docker.com/linux/debian bullseye/stable amd64 Packages
     5:23.0.3-1~debian.11~bullseye 500
        500 https://download.docker.com/linux/debian bullseye/stable amd64 Packages
     5:23.0.2-1~debian.11~bullseye 500
        500 https://download.docker.com/linux/debian bullseye/stable amd64 Packages
     5:23.0.1-1~debian.11~bullseye 500
        500 https://download.docker.com/linux/debian bullseye/stable amd64 Packages

Downgrade packages:

apt install docker-ce=5:23.0.6-1~debian.11~bullseye
apt install docker-ce-cli=5:23.0.6-1~debian.11~bullseye
apt install docker-ce-rootless-extras=5:23.0.6-1~debian.11~bullseye

To prevent the packages from being updated again, the packages must be put on hold:

apt-mark hold docker-ce docker-ce-cli docker-ce-rootless-extras

Allowing the packages to be updated again:

apt-mark unhold docker-ce docker-ce-cli docker-ce-rootless-extras
2 Likes

This is now fixed with v12.0.0 Beta. Testing and feedback is welcome! See https://github.com/nextcloud/all-in-one#how-to-switch-the-channel

4 Likes

Just upgraded my test instance to v12.0.0 and it works with Docker version 29.0.0. No Slim Application Error anymore :slight_smile: :+1:

2 Likes

And NOW i am seeing a blank page when i open the nextcloud login page. Its just nothing, but a blue background..

Hi team.. I was able to fix this.. but can you help me understand when can i switch back to latest version instead of using beta version

The same way you switched to the beta. By switching the tag back from beta to latest: https://github.com/nextcloud/all-in-one#how-to-switch-the-channel

1 Like