Hey! It's a bit hard to debug like this. Does the server correctly generate the server key when it starts? Is it persisted between restarts? Alternatively, are you using the server key seed?

Thanks for your reply! I was not sure what info you need, sorry for that. Server key: How can I verify this? Should this be a new file in the data folder? This is what my data folder contains (resarted multiple times): lldap_config.toml, private_key, users.db Persistent: Yes, I pointed my data folder in my Portainer stack to the folder /home/Configs/lldap/data. Which seems to work, the files were created and after rebooting the container everything is the same like before the reboot. **Server key seed: **Not using server seed, at least I didn't make any deliberate settings for that. Log: I changed the verbosity to "true" and restarted the container. Where can I find the logs? There seems to be no log file in the data folder.

Yeah, that was the private key file I was talking about

Here's the log, does this help you narrow down the root cause? https://cdn.discordapp.com/attachments/1152181623912153129/1152188086596407306/message.txt

It's a bit too noisy. Could you restart the container, try to log in, stop it, and give me the entire log? (Including the config at the beginning)

Sure, here you go: https://cdn.discordapp.com/attachments/1152181623912153129/1152189879082565642/message.txt

That's an old LLDAP! Could you upgrade to stable?

My stack is actually image: nitnelave/lldap:stable I changed it to image: nitnelave/lldap:0.5 Which gave me this error: failed to pull images of the stack: lldap Pulling lldap Error Error response from daemon: manifest for nitnelave/lldap:0.5 not found: manifest unknown: manifest unknown With image: nitnelave/lldap:latest I can deploy it again, it also says LLDAP version 0.5.1-alpha on the login page, but I'm having the same issue with it. BTW, I changed it back to latest, just like it was initially, and it says version 0.5 on the login page. No idea why the logs tell otherwise.

Ah, that's because you pulled the new image in the meantime 🙂

Did that, but nothing has changed... Still the same error. https://cdn.discordapp.com/attachments/1152181623912153129/1152197345484742707/message.txt

Yeah, that's weird, I see the login request, so the failure must be client side

I open the IP http://192.168.2.124:17170/ I enter admin as username I enter the password that I specified in the config file. I tried it in an Incognito tab as well as on another machine. Everywhere the same result.

The only thing I can think of is that the password is genuinely wrong 😄

I already tried to delete the users.db file and let it recreate by restarting the container, but I get the same result. I just did it again, just to be sure, and it's still the same. I even copied the password from my config file to rule out any typos, but it's not working, no matter what I try. 😦

Hmm, what if you delete the DB and set the key_seed to a random string in the config?

How do I set the key_seed? I can't find that value in the config file. The ldapsearch command also gives me an "Invalid credentials (49)" error. (I replaced password with my actual password 😉 )

Just add the key_seed key/value

Did that, sill the same. I also tried deploying it classically with a docker-compose.yml file and docker-compose up -d, just to take out Portainer of the equation. Nothing changes... I really don't understand what's going wrong here.

Huh, that's a real head scratcher

I got it working by changing those values in the stack / docker-compose instead of the config file. Thanks for your help!!!

My pleasure! I'm glad you got it working 🙂