-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some users can't reset their password #6570
Comments
Hi, Can you check your local jobs of type But I improved email logging in 99091da |
There's no failed jobs and I couldn't find any relevant information in the logs either. I can't see that there's any email jobs created for the users who's reporting that they haven't got any email. So either Peertube fails to create the job or the users fails to reset their password. |
Can you ask him/her to try again and check in your peertube or nginx logs if the |
We need to redesign the audit log but in the meantime I added more "classic" logs in fc771a6 You can filter log entries using Parse logs:
Or by username (for example
|
Thanks. We'll upgrade to Peertube 6.3 as soon as it's released and see if we can debug further what happens. |
It seems email stopped working for us in 6.2.1. No errors to be found in the logs. Will also upgrade to 6.3 see if it makes a difference. |
Please create a dedicated issue with server debug logs enabled @kontrollanten Do you have news? |
No, we haven't updated yet |
I may have found the reason causing this issue. We just had a user who tried to reset his email but it failed due to the registered email was capitalized, whilst he typed his email in lower case. Related to #6383 |
In order to not force users to be case sensitive when asking for password reset or resend email verification. When there's multiple emails where the only difference in the local is the capitalized letters, in those cases the users has to be case sensitive. closes Chocobozzz#6570
In order to not force users to be case sensitive when asking for password reset or resend email verification. When there's multiple emails where the only difference in the local is the capitalized letters, in those cases the users has to be case sensitive. closes Chocobozzz#6570
Allow case insensitive email when there's no other candidate. closes Chocobozzz#6570
In order to not force users to be case sensitive when asking for password reset or resend email verification. When there's multiple emails where the only difference in the local is the capitalized letters, in those cases the users has to be case sensitive. closes Chocobozzz#6570
Allow case insensitive email when there's no other candidate. closes Chocobozzz#6570
In order to not force users to be case sensitive when asking for password reset or resend email verification. When there's multiple emails where the only difference in the local is the capitalized letters, in those cases the users has to be case sensitive. closes Chocobozzz#6570
Allow case insensitive email when there's no other candidate. closes Chocobozzz#6570
Allow case insensitive email when there's no other candidate. closes Chocobozzz#6570
Describe the current behavior
We get a lot of emails from users that says that they've requested a password reset, but they don't receive any email. When I search for their email, user id and username in the logs and audit log I can't find anything.
Relevant config:
Whilst I know it works for other users. Possible causes:
To investigate this further we may need to add more logging to determine what's going wrong. As far as I can see there's no audit logs for password resets, can we add that? Also we could add some info log here to tell that an email is being prepared.
PeerTube/server/core/lib/job-queue/job-queue.ts
Line 355 in a06c2ea
Steps to reproduce
Describe the expected behavior
No response
Additional information
PeerTube instance:
Browser name, version and platforms on which you could reproduce the bug:
Link to browser console log if relevant:
Link to server log if relevant (
journalctl
or/var/www/peertube/storage/logs/
):The text was updated successfully, but these errors were encountered: