frazzle - Hello, been trying to setup nextcloud...
# troubleshootingf
frazzle._
09/14/2025, 9:46 PMHello, been trying to setup nextcloud's ldap backend for the past few days and having no luck, experience has been extremely weird. Anyone have an idea what's going wrong?
a
Answer Overflow
09/14/2025, 9:46 PMmessage has been deleted
f
frazzle._
09/14/2025, 9:48 PMI followed the example config listed on the repo here: https://github.com/lldap/lldap/blob/main/example_configs/nextcloud.md
My nextcloud connects to lldap without any issues, even shows the groups in the accounts page after the first run and the accounts numbers in groups, and the number of accounts.
Completely prevents me from logging in via lldap and eventually all the groups disappear and the users.
frazzle._
09/14/2025, 9:50 PMfrazzle._
09/14/2025, 9:51 PMn
nitnelave
09/14/2025, 9:51 PMSeems that the login for lldap_user_one fails, and it detects that all the accounts are gone or something like that
nitnelave
09/14/2025, 9:52 PMCan you log in as that user in LLDAP?
nitnelave
09/14/2025, 9:52 PMCan you post the LLDAP verbose logs when synchronizing with nextcloud?
f
frazzle._
09/14/2025, 9:52 PMYes these users work fine in LLDAP themselves.
I'll see if I can get LLDAP logs
frazzle._
09/14/2025, 10:16 PMturned on
LLDAP_VERBOSE=truefrazzle._
09/14/2025, 10:16 PMlldap log (redacted everything sensitive), lldap_user_one, and lldap_user_two should line up correctly.
https://cdn.discordapp.com/attachments/1416902983345639434/1416910618895585333/message.txt?ex=68c89058&is=68c73ed8&hm=f473afe1f33b57c0858b4948ff858c37129f758e145a61e46f4dc26e5d2f3635&
n
nitnelave
09/14/2025, 10:30 PMI can't be sure, but the issue might be that the bind user for nextcloud doesn't have sufficient privileges. Is it a member of (at least) lldap_strict_readonly? Or any other lldap\_ built-in groups?
nitnelave
09/14/2025, 10:32 PMThere's also something in the command logs you gave me about not matching DC, though I suspect it was redacted because it's example.com
f
frazzle._
09/14/2025, 10:35 PMit's only got lldap_strict_readonly
n
nitnelave
09/14/2025, 10:36 PMWhat is the bind user redacted to in your examples?
f
frazzle._
09/14/2025, 10:36 PMlldap_ro_account
n
nitnelave
09/14/2025, 10:37 PMThe logs you gave me of LLDAP show a normal user doing normal user things, successfully
nitnelave
09/14/2025, 10:38 PMI can't extrapolate too much from that
f
frazzle._
09/14/2025, 10:39 PMwould destroying nextcloud and all the data, and recreating the initial ldap connection for the first time help? I can do that again with lldap verbose mode on the whole time
n
nitnelave
09/14/2025, 10:40 PMThat can't hurt, but I don't know when I'd have the time to go through that much logging 😄
f
frazzle._
09/14/2025, 10:41 PMyeah I figured. Wonder if trying an older nextcloud version would somehow help, cause it's such a weird issue
n
nitnelave
09/14/2025, 10:42 PMI need to get some LLMs to summarize the logs
f
frazzle._
09/14/2025, 10:42 PMi'll get the full dump with the same scenario after my pizza 😆
n
nitnelave
09/14/2025, 10:43 PMI'll be asleep by then, but send it over!
frazzle._
09/14/2025, 11:42 PMsteps taken:
1. stopped nextcloud
2. wiped nextcloud
3. restarted lldap
4. started nextcloud
5. logged into nextcloud as admin
6. enabled debug logs
7. logged out
8. ran nextcloud ldap config setup commands
9. tried to login as ldap_user_one
10. logged into nextcloud as admin
11. dumped logs of both
lldap_user_one -> login user
lldap_ro_account -> bind account
n
nitnelave
09/15/2025, 11:44 PMI don't know whether that's the issue, but you have a trailing
\nf
frazzle._
09/16/2025, 4:08 PMthat was it, a new line character in
LLDAP_LDAP_BASE_DN_FILEn
nitnelave
09/16/2025, 4:09 PMGreat! It might be something we can add, a check for weird characters in the DC
f
frazzle._
09/16/2025, 4:10 PMyeah a warning or something for certain symbols so others don't end up with this issue, in my case it's because I was using a _FILE, with nano that seemingly auto adds a new line on save. Had to manually hexdump to see and then trunicate to get rid of it >.>
n
nitnelave
09/16/2025, 10:48 PMhttps://github.com/lldap/lldap/pull/1297 < made it so you can have a trailing newline, it'll get normalized when parsing.