Replies: 4 comments 4 replies
-
Did you try to create another user? |
Beta Was this translation helpful? Give feedback.
-
Could it be that email_verified_at is empty? I had the same error when this field was empty. Laravel normally redirects the user to the verify email page, but for some reason Filament doesn't seem to do that. |
Beta Was this translation helpful? Give feedback.
-
The error message can be misleading. |
Beta Was this translation helpful? Give feedback.
-
I'm having this same issue on my production environment on an app I rolled out last week. I have 3 panels, 2 of which are internal only, and one is client facing. All my internal folks can login just fine, but clients can't. I have the
Did anyone figure this out? What makes this more confusing is that I can't reproduce it locally, but it's happening in production. Totally lost on what might be the root cause. |
Beta Was this translation helpful? Give feedback.
-
Package
Other
Package Version
^3.2
How can we help you?
I tried logging in with correct credentials and this is what I encounter. My friend is using windows and we pulled from master and did all the composer and npm without an error and imported the same database. He was able to login but in my case I got 'These credentials do not match our records.'. I even try to change it's password but still got the same error. I use this seeder to change password and I double check if the password is really password123 and still have the same error 'These credentials do not match our records.'
Beta Was this translation helpful? Give feedback.
All reactions