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

Forgot password feature not sending the verification code email #12154

Open
5 tasks done
deca-irae opened this issue Dec 27, 2024 · 2 comments
Open
5 tasks done

Forgot password feature not sending the verification code email #12154

deca-irae opened this issue Dec 27, 2024 · 2 comments
Labels
🐞 bug Something isn't working 🤔 cant-reproduce We can not reproduce it or the information is limited

Comments

@deca-irae
Copy link

deca-irae commented Dec 27, 2024

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

0.14.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

SMTP-related settings in the .env are all set. Values are also within the Dify API container environment variables. Email sending was working prior to 0.14.1.

Nginx logs seem to show that the email was successfully sent but I haven't received any email.
image

Also checked our SMTP service in AWS and it seems like nothing was received for sending.
image

✔️ Expected Behavior

Verification code email for resetting the password is received.

❌ Actual Behavior

No verification code email was received.

@dosubot dosubot bot added the 🐞 bug Something isn't working label Dec 27, 2024
Copy link

dosubot bot commented Dec 27, 2024

I found a similar open issue that might help you resolve the problem. The suggested solution is to ensure that the Mail parameters in the .env file are correctly set. Here's a sample configuration:

MAIL_TYPE: ''
MAIL_DEFAULT_SEND_FROM: 'YOUR EMAIL FROM (eg: no-reply <[email protected]>)'
SMTP_SERVER: 'your.smtp.server'
SMTP_PORT: 465
SMTP_USERNAME: 'your_smtp_username'
SMTP_PASSWORD: 'your_smtp_password'
SMTP_USE_TLS: 'true'
SMTP_OPPORTUNISTIC_TLS: 'false'

Make sure to replace 'your.smtp.server', 'your_smtp_username', and 'your_smtp_password' with your actual SMTP server details. After making these changes, restart the service using:

docker compose down
docker compose up -d

If you still do not receive the emails, verify that the email service is functioning correctly and check if the email has been placed in the spam folder. You can find more details in the related issue here [1].

To continue talking to Dosu, mention @dosu.


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

@deca-irae
Copy link
Author

I found a similar open issue that might help you resolve the problem. The suggested solution is to ensure that the Mail parameters in the .env file are correctly set. Here's a sample configuration:

MAIL_TYPE: ''
MAIL_DEFAULT_SEND_FROM: 'YOUR EMAIL FROM (eg: no-reply <[email protected]>)'
SMTP_SERVER: 'your.smtp.server'
SMTP_PORT: 465
SMTP_USERNAME: 'your_smtp_username'
SMTP_PASSWORD: 'your_smtp_password'
SMTP_USE_TLS: 'true'
SMTP_OPPORTUNISTIC_TLS: 'false'

Make sure to replace 'your.smtp.server', 'your_smtp_username', and 'your_smtp_password' with your actual SMTP server details. After making these changes, restart the service using:

docker compose down
docker compose up -d

If you still do not receive the emails, verify that the email service is functioning correctly and check if the email has been placed in the spam folder. You can find more details in the related issue here [1].

To continue talking to Dosu, mention @dosu.

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

As I've said above, all mail parameters in the .env are correctly set. The verification code was also able to be sent prior to v.0.14.1.

@crazywoola crazywoola added the 🤔 cant-reproduce We can not reproduce it or the information is limited label Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working 🤔 cant-reproduce We can not reproduce it or the information is limited
Projects
None yet
Development

No branches or pull requests

2 participants