Skip to content
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

Too many incorrect password!!!! #11986

Closed
5 tasks done
shiliu2023 opened this issue Dec 23, 2024 · 2 comments
Closed
5 tasks done

Too many incorrect password!!!! #11986

shiliu2023 opened this issue Dec 23, 2024 · 2 comments

Comments

@shiliu2023
Copy link

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

lasted

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I'm using Docker to run Dify and I got the password wrong a few times and it's giving me this error "Too many incorrect password attempts. Please try again later." Can anyone help me resolve it?

✔️ Expected Behavior

I want login

❌ Actual Behavior

No response

Copy link

dosubot bot commented Dec 23, 2024

To resolve the "Too many incorrect password attempts" error when using Docker to run Dify, you can reset the password using the following command if you deployed with Docker Compose:

docker exec -it docker-api-1 flask reset-password

You will be prompted to enter your email address and a new password twice. This will reset the password and should help resolve the issue.

Additionally, if you still face issues, you can connect to your Redis container and run the FLUSHALL command to reset all rate limiting data, including the stored login attempt counters that are causing the lockout. Be cautious when using FLUSHALL in production environments, as it will clear all data in Redis [1][2].

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

@crazywoola
Copy link
Member

Duplicated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants