Support intro
Sorry to hear you’re facing problems. 
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:
- Official documentation (searchable and regularly updated)
- How to topics and FAQs
- Forum search
(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).
The Basics
- Nextcloud Server version (e.g., 29.x.x):
- 35.0.2.2 (upgraded from 34.0.5.1)
- Operating system and version (e.g., Ubuntu 24.04):
- Ubuntu 24.04.5 LTS
- Web server and version (e.g, Apache 2.4.25):
- AIO built-in Apache container
- Reverse proxy and version _(e.g. nginx 1.27.2)
- Apache 2.4.67 (Ubuntu), on a separate VM
- PHP version (e.g, 8.3):
- 8.4.27 (AIO Nextcloud container)
- Is this the first time you’ve seen this error? (Yes / No):
- No. Deck has been disabled after earlier upgrades too, but I only have logs from the latest one (34 → 35).
- When did this problem seem to first start?
- Latest occurrence: the automatic AIO upgrade from 34.0.5 to 35.0.2
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
- AIO (
nextcloud/all-in-one:latest), automatic updates after daily backup
- AIO (
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
- No
Summary of the issue you are facing:
During the AIO upgrade to Nextcloud 35, AIO disables some apps (groupfolders, deck, richdocuments, side_menu) and then runs occ app:update --all before re-enabling them.
The Team Folders (groupfolders) update 22.0.6 → 23.0.1 crashes while the app is disabled, and the crash aborts the whole app:update --all run. Every app after groupfolders in the queue is not updated.
On one instance, Deck came after groupfolders. It stayed on 1.18.6, which is not compatible with NC 35, so AIO could not re-enable it. Deck was updated to 1.19.2 later in the same run, but was never re-enabled, so it had to be enabled manually.
On the other instance, Deck happened to come before groupfolders, got updated in time and was re-enabled without problems.
groupfolders itself recovered: the 23.0.1 code was already in place, so AIO could re-enable it, and the repair step “Adjust Groupfolders with wrong default quotas” then ran fine. So the repair step (WrongDefaultQuotaRepairStep) seems to fail only while the app is disabled.
The same error has shown up before when groupfolders was disabled during an update: Groupfolders all gone without manual update
Is this a known groupfolders issue? And could AIO run app:update per app, so that one crashing app doesn’t block updates for the rest?
Steps to replicate it (hint: details matter!):
-
AIO with Nextcloud 34.0.5, groupfolders 22.0.6 and Deck 1.18.6 enabled
-
Let AIO upgrade to Nextcloud 35.0.2 (AIO disables groupfolders and Deck before the upgrade)
-
occ app:update --allcrashes on groupfolders. This happened on both instances.
Whether Deck is affected depends on the order app:update --all processes the apps in, which differed between the two instances. If Deck comes after groupfolders, it is never updated and can’t be re-enabled. If it comes before, it is updated in time and everything looks fine despite the crash. I don’t know what decides that order.
Log entries
Nextcloud
No full stack trace in nextcloud.log. The error was only printed to the console by occ. From AIO’s /var/www/html/data/update.log:
Disabling apps before the update to make the update procedure safer. This can take a while...
groupfolders 22.0.6 disabled
deck 1.18.6 disabled
richdocuments 11.1.2 disabled
side_menu 6.2.0 disabled
...
Update successful
...
groupfolders new version available: 23.0.1
In SimpleContainer.php line 114:
Could not resolve OCA\GroupFolders\ACL\UserMapping\IUserMappingManager! Class can not be instantiated
In SimpleContainer.php line 135:
Could not resolve OCA\GroupFolders\ACL\UserMapping\IUserMappingManager! Class can not be instantiated
app:update [--all] [--showonly] [--showcurrent] [--allow-unstable] [--] [<app-id>]
Restoring app statuses. This may take a while...
Enabling deck...
The deck app could not be re-enabled, probably because it is not compatible with the new Nextcloud version.
...
Enabling groupfolders...
...
- Adjust Groupfolders with wrong default quotas
...
deck new version available: 1.19.2
deck updated
Web Browser
Not relevant (happens during the CLI upgrade).
Web server / Reverse Proxy
Not relevant.
Configuration
Nextcloud
Can provide occ config:list system if needed.
Apps
Current state: groupfolders 23.0.1 and deck 1.19.2, both enabled. Can provide the full occ app:list if needed.
Workaround
A nightly cron job on the host, after the AIO backup/update window:
0 3 * * * for app in deck groupfolders; do docker exec --user www-data nextcloud-aio-nextcloud php occ app:update "$app"; docker exec --user www-data nextcloud-aio-nextcloud php occ app:enable "$app"; done