Problem
The Nextcloud settings disappear from Advanced settings in UDM/UMC, and newly created users are no longer automatically enabled for Nextcloud.
Confirmed with UCS 5.2-7 and Nextcloud 32.0.12-0 in a domain with multiple Nextcloud installations.
Investigation
Check whether the Nextcloud Extended Attributes are still registered:
udm settings/extended_attribute list --filter name=nextcloudUserEnabled
If no object is returned, check the App Center logs of recently installed or removed Nextcloud instances:
zgrep -E 'Aborting|Going to remove Nextcloud|Removing DN: cn=nextcloud' /var/log/univention/appcenter.log*
In the affected environment, the logs showed an installation rollback followed by deletion of these three LDAP objects:
- nextcloudUserQuota
- nextcloudUserEnabled
- nextcloudGroupEnabled
Existing users with objectClass=nextcloudUser remained in LDAP, but newly created users did not receive the object class.
Root Cause
A failed Nextcloud installation on an additional Member Server triggered an automatic App Center rollback.
During rollback, the generic App Center cleanup deleted the domain-wide Nextcloud Extended Attributes, although Nextcloud remained installed on many other servers.
The LDAP schema remained loaded, but the UDM integration was removed.
The issue is tracked in Bugzilla.
Solution
Restore the Nextcloud schema registration and Extended Attributes on a Member Server with the Nextcloud App Center application installed:
univention-app register nextcloud --attributes --do-it --username Administrator
Verify that the Nextcloud Extended Attributes are registered again:
udm settings/extended_attribute list --filter name=nextcloudUserEnabled
The Nextcloud settings should now be available in UDM/UMC again.
Users created while the Extended Attributes were missing may still lack objectClass=nextcloudUser. They must be enabled separately.
On a Nextcloud server, obtain the user filter configured for initial Nextcloud activation:
FILTER="$(ucr get nextcloud/ucs/modifyUsersFilter)"
echo "$FILTER"
Ensure the filter is not empty. It normally excludes system accounts and users already having the nextcloudUser object class.
Preview the affected users:
udm users/user list --filter "$FILTER" | sed -n 's/^DN: //p'
Review the results carefully. If all listed users should be enabled for Nextcloud, update them using:
udm users/user list --filter "$FILTER" | sed -n 's/^DN: //p' | while IFS= read -r dn; do
udm users/user modify --dn "$dn" --set nextcloudEnabled=1
done
The line-based loop preserves spaces in user DNs.
Verify a corrected user:
univention-ldapsearch -LLL -b "<USER_DN>" -s base '(objectClass=*)' objectClass nextcloudEnabled
Expected attributes:
objectClass: nextcloudUser
nextcloudEnabled: 1