12ine (12ine) asked a question.
"Unable to sign in" error for Okta on only one device
I currently have access to two laptops, but I can only sign in to my Okta account from one of them. When I try to sign in on the other, it gives me the "Unable to sign in" error. From there, it doesn't send any of the verification options. It isn't an issue with my device, as I receive the verification codes when logging into Okta from the other laptop.
- I've cleared my cache and browser information.
- I've restarted the laptop with the issue and my phone that should receive the verification code.
- I was able to login on the laptop with the issue just fine yesterday.
- I've verified the date and time and restarted the laptop a second time, following the advice for a similar issue that was posted about a year ago.
- I verified the network connection, and no issues there.
I need to be able to login on the laptop that's have the issue, as I will not have access to any others a
Hello @12ine (12ine) , thank you for contacting Okta Community.
The error "Unable to sign in" is usually caused by a policy or a rule that's not being met.
If you are an employee or contractor of a company that has an Okta Org, please contact their IT Support or Help Desk team. They will have access to see the logs on your profile and determine the cause of the error.
If you are an admin of the org, please check the logs right after a failed login attempt. To see the logs for one user account only, you can go to the user's profile (from Directory > People) and on their profile, click "View logs". From there, look for anything that says "Challenge" or "Denied." It should show you a requirement that was not met, such as "Catch-all Rule". You can click the requirement (in this example, "Catch-all Rule") to see more details. It could be an IP that's being blocked, a VPN giving you a location outside the allowed network zone, or a matter related to an unmanaged or unenrolled device—it depends on what configuration the org has. Either way, the starting point for this kind of error is in the logs.
Here are some articles on the matter:
System Log - what this is and how to use the tool
Getting Started with Okta System Logs - this contains links to a few additional resources under Related References
Regards.
--
Help others in the community by liking or hitting Select as Best if this response helped you.