Problem when try to reset password in production

Hey guys i have problem when i try to send the reset password email, i have the same configuration in .env production and local... i mean the same configuration for email configuration, smtp, password, username, etc... Now when i send the email password in local, i receive the email, if you see the screenshot, the message say (We have emailed your password reset link) but when i send the email reset password in production i have problems, the message is other (password.sent) and i have an error in the log. do you have any idea about this problem?
[2025-04-25 06:26:12] production.ERROR: Filament\Notifications\Auth\ResetPassword has been attempted too many times. {"exception":"[object] (Illuminate\\Queue\\MaxAttemptsExceededException(code: 0): Filament\\Notifications\\Auth\\ResetPassword has been attempted too many times. at /home/forge/mywebsite.com/vendor/laravel/framework/src/Illuminate/Queue/MaxAttemptsExceededException.php:24)
[stacktrace]
[2025-04-25 06:26:12] production.ERROR: Filament\Notifications\Auth\ResetPassword has been attempted too many times. {"exception":"[object] (Illuminate\\Queue\\MaxAttemptsExceededException(code: 0): Filament\\Notifications\\Auth\\ResetPassword has been attempted too many times. at /home/forge/mywebsite.com/vendor/laravel/framework/src/Illuminate/Queue/MaxAttemptsExceededException.php:24)
[stacktrace]
i use jobs, queues and driver database in local and production
No description
No description
3 Replies
TranceCode
TranceCodeOP5d ago
Any idea about this problem?
Dennis Koch
Dennis Koch4d ago
Passwords sent sounds like your translation files are missing or you use a bad locale Are there other errors before „tried too many times“? Maybe your mail config is bad? I’d recommend to set the database driver to sync for debugging to see if you get a different error
TranceCode
TranceCodeOP2d ago
Hey bro, finally this is not a problem with filament, i make an investigation and the problem is that azure block my ip or vps, for that reason i have this message in production, really bad but hope that azure unlock the vps or i will migrate to AWS SES... both are really convenient for the price... Thank you @Dennis Koch

Did you find this page helpful?