Dify1.14.1，配置邮箱注册报错，有懂的嘛

Discussion
1

dify@dify-api-v114x-5c5d87f48c-zdql4:/app/api/controllers/console/auth$ nl -ba email_register.py | sed -n ‘104,116p’

104

105 # Verified, revoke the first token

106 # AccountService.revoke_email_register_token(args.token)

107

108 # Refresh token data by generating a new token

109 # _, new_token = AccountService.generate_email_register_token(

110 # user_email, code=args.code, additional_data={“phase”: “register”}

111 # )

112

113 AccountService.reset_email_register_error_rate_limit(user_email)

114 return {“is_valid”: True, “email”: normalized_token_email, “token”: args.token}

这种如何解决，是跟很更新镜像版本嘛

2

我用的1.14.2版本是可以正常配置、识别，功能也正常

3

大佬，可以分享下deployment的配置嘛，我想比较下看看想同步看下有没有问题，我现在邮箱配置可以发送成功了，验证也可以，但是用户设置密码和重复密码后，开始还是注册不了，当时就设置了管理员进入work space配置模型接入了，但是新用户的注册还是卡在了设置密码后的提交

4

api容器就报这个错

2026-06-12 09:54:52,371.371 DEBUG [Dummy-771] [handler.py:104] - Can only upgrade connection if using GET method.
2026-06-12 09:54:52,377.377 INFO [Dummy-771] [handler.py:242] 1bb64a6e1ca5581c83c8250204320d6b - 172.16.1.106 - - [2026-06-12 09:54:52] “POST /console/api/email-register HTTP/1.1” 400 420 0.006211
2026-06-12 09:55:23,134.134 DEBUG [Dummy-772] [handler.py:68] - Initializing WebSocket
2026-06-12 09:55:23,134.134 DEBUG [Dummy-772] [handler.py:100] - Validating WebSocket request
2026-06-12 09:55:23,140.140 INFO [Dummy-772] [handler.py:242] da4f32654acd564eb4575bfc178aefc7 - 172.16.1.106 - - [2026-06-12 09:55:23] “GET /console/api/account/profile HTTP/1.1” 200 636 0.006782
2026-06-12 09:56:12,222.222 DEBUG [Dummy-668] [handler.py:68] - Initializing WebSocket
2026-06-12 09:56:12,222.222 DEBUG [Dummy-668] [handler.py:100] - Validating WebSocket request
2026-06-12 09:56:12,222.222 DEBUG [Dummy-668] [handler.py:104] - Can only upgrade connection if using GET method.
2026-06-12 09:56:12,230.230 INFO [Dummy-668] [handler.py:242] bfad7017dc935f81aa4d5f58bf3b50e2 - 172.16.1.106 - - [2026-06-12 09:56:12] “POST /console/api/email-register HTTP/1.1” 400 420 0.008464

web页面提示

{
“code”: “invalid_or_expired_token”,
“message”: “The token is invalid or has expired.”,
“status”: 400
}