User limit reached warning despite correct user count

[fs1n]

The Issue:

I'm running Nextcloud AIO with the LDAP user backend. Users are filtered via a single LDAP group containing ~43 members, plus 11 manually created local accounts ... so I'd expect a total of ~54 users.

Instead, Nextcloud reports 97 total users and is warning me that I've reached the user limit.

Output of occ user:report:

+------------------+----+
| Account Report   |    |
+------------------+----+
| Database         | 11 |
| LDAP             | 86 |
|                  |    |
| total users      | 97 |
|                  |    |
| user directories | 2  |
| active users     | 41 |
| disabled users   | 1  |
+------------------+----+

Output of occ user:list | wc -l:

52

If I search for LDAP remnant users i find 1 Deactivated and ldap:show-remnants shows me 3 Users

What I'd expect

• ~43 LDAP users (scoped via group filter) (Base DN is the Forrests root)
• 11 local database users
• Total: ~54

So my questions are

• Where do the extra ~43 LDAP users come from?
• Is this a known issue with group-scoped LDAP configs when the Base DN is set at the forest root?

I currently have this issue with Nextcloud Hub 26 Winter (33.0.3) and LDAP LDAP user and group backend (1.24.0) but I saw this in earlier versions to.

[szaimen]

Hi, can you check https://docs.nextcloud.com/server/stable/admin_manual/configuration_user/user_auth_ldap_cleanup.html?

[fs1n]

Hi @szaimen , I found the issue. Before the discussion, I had already checked the article you sent me.

The solution is simple. I created two LDAP configurations, one for each available Domain Controller. Although Nextcloud does not create a user for each configuration, it counts each user twice.

Edit:
https://docs.nextcloud.com/server/stable/admin_manual/configuration_user/user_auth_ldap.html (Set Replica correctly in one config)