JohnBeePowel - Hey everyone. I've just installe...
Hey everyone. I've just installed LLDAP in a docker container. It seems to work well with Jellyfin. I want to get the password reset to work.
Right now it doesn't work. I set it up with my throwaway Gmail account, I generated an app password and it put it in the toml file. When I tried password reset, it doesn't send a password. Am I missing a configuration?
Solution:Jump to solution
[smtp_options]
enable_password_reset=true
server="smtp.gmail.com"
port=465
smtp_encryption = "TLS"...
29 Replies
Here is my config
Can you post the verbose LLDAP logs?
here's the logs. I scrubbed some info.
That's a long log 😄
I don't see a password reset request in the last part, once you enabled verbose logs
I wasnt sure what to grab. So you think i didnt set it properly ? I used docker to deploy it, then after starting it and testing it out, i edited the toml file.
Can you start it in verbose mode, try to reset the password, and send me just these logs?
I restarted the container, tried a password reset and grabbed those logs.
I'm sorry, but I don't see it in the logs...
Not sure what's going on
What do you get in the frontend?
(how are you doing a password reset?)
I go to the front end, on port 17170, click on "forgot your password", type my email and click "reset my password". Then I get the message "token was sent to your mail"
You type your email, right? 😄
Not password
Yes exactly
I don't see anything matching that in the server logs
Do you get errors in the web console?
Do you see a request to /auth/reset/step1 ?
And step2
(or are these the wrong logs?)
I'm looking at the logs from the docker plugin on OpenMediaVault. Is there another log I can search from inside the container ?
Nope, that's the one
To be clear, this is exactly the log format I'm expecting, there's just no message corresponding to the queries
Maybe is it from a previous restart?
(though they're from 2 minutes before your message, so...)
The timestamp is the good one. I'm looking at live logs while I try the password reset. Here is the docker-compose.yml
Getting back to the developer console on the browser, do you get errors? Do you see the queries?
Here you can see that I request /login. But as soon a I go to "/reset-password/step1" there's a bunch of other messages. When I go back to /login i can see the message show up in the log, but nothing to "/reset-password/step1".
Aha, I see
Can you clear the cache and retry?
You're getting 304s, not modified
(the request shouldn't be a get)
Are on latest or stable?
How do i do that ? I delete the docker container completely ?
stable
Clear the browser cache
Or incognito mode
That might have been fixed in latest? I don't remember
now we're getting somewhere
lldap-1 | 2024-09-02T15:53:34.904399722+00:00 WARN │ ┝━ 🚧 [warn]: Error sending email: lettre::transport::smtp::Error {
lldap-1 | kind: Connection,
lldap-1 | source: lettre::transport::smtp::Error {
lldap-1 | kind: Connection,
lldap-1 | source: Custom {
lldap-1 | kind: InvalidData,
lldap-1 | error: CorruptMessage,
lldap-1 | },
lldap-1 | },
lldap-1 | }
lldap-1 | 2024-09-02T15:53:34.904401610+00:00 INFO │ ┕━ ｉ [info]: Reset token:
Seems I have an issue.
That's usually TLS vs STARTTLS
You want the "SSL" port from your provider, and configure LLDAP with TLS
In particular, you don't want the TLS port from the provider, because SMTP docs universally suck and it means STARTTLS, which is bad and should be avoided
I get an error 500 with TLS, but a connexion error to gmail with STARTTLS. My provider here is a gmail account. So should it be TLS ?
For gmail, use TLS and port 465
And an app password
I got the app password
with port 465 the account is not recognized
Solution
[smtp_options]
enable_password_reset=true
server="smtp.gmail.com"
port=465
smtp_encryption = "TLS"
user="[email protected]"
password="app password"
from="LLDAP Admin (Password Reset) <[email protected]>"
reply_to="Do not reply <[email protected]>"
Got it working. I just need to fix a few other things. I got it working with encryption="TLS" and port=465. I also made a mistake on the app password.