frazzle
09/14/2025, 9:46 PMAnswer Overflow
09/14/2025, 9:46 PMfrazzle
09/14/2025, 9:48 PMfrazzle
09/14/2025, 9:50 PMfrazzle
09/14/2025, 9:51 PMnitnelave
09/14/2025, 9:51 PMnitnelave
09/14/2025, 9:52 PMnitnelave
09/14/2025, 9:52 PMfrazzle
09/14/2025, 9:52 PMfrazzle
09/14/2025, 10:16 PMLLDAP_VERBOSE=true, restarted lldap and nextcloud.
ran these 3 cmds on nextcloud:frazzle
09/14/2025, 10:16 PMnitnelave
09/14/2025, 10:30 PMnitnelave
09/14/2025, 10:32 PMfrazzle
09/14/2025, 10:35 PMnitnelave
09/14/2025, 10:36 PMfrazzle
09/14/2025, 10:36 PMnitnelave
09/14/2025, 10:37 PMnitnelave
09/14/2025, 10:38 PMfrazzle
09/14/2025, 10:39 PMnitnelave
09/14/2025, 10:40 PMfrazzle
09/14/2025, 10:41 PMnitnelave
09/14/2025, 10:42 PMfrazzle
09/14/2025, 10:42 PMnitnelave
09/14/2025, 10:43 PMfrazzle
09/14/2025, 11:42 PMnitnelave
09/15/2025, 11:44 PM\n in your DC, I think on the LLDAP side, in the configfrazzle
09/16/2025, 4:08 PMLLDAP_LDAP_BASE_DN_FILE and now all is good, surprised nothing else was affected by this. Thanks for the helpnitnelave
09/16/2025, 4:09 PMfrazzle
09/16/2025, 4:10 PMnitnelave
09/16/2025, 10:48 PM