When you try to sign in to the OmniStor app on iPhone or Android and it doesn't work, the cause usually falls into one of these: account, password, service URL, two-factor authentication, mobile device binding, or network. This article walks you through scenarios so you can find the matching fix.
Two quick checks first
Before digging deeper:
- Is your network working? Try opening another website to confirm.
- Is the service URL correct? Confirm spelling with your IT administrator — especially the
https://prefix and that there's no extra character or whitespace at the end.
If both are fine, match your scenario below.
Scenario 1: "Wrong account or password"
The most common situation. Possible causes:
Typo
- Account names are usually case-sensitive — check capitalization and that you haven't added or dropped characters.
- The password field may be silently changed by phone autocorrect. Tap the eye icon to show the password and verify before submitting.
Wrong account type
- If you're using a Windows AD/LDAP account, confirm the password matches your work computer/email login.
- If you're using a standalone OmniStor account (created by an administrator in OSM), confirm you haven't confused it with your AD account.
Password expired or reset
- Your organization may require periodic password changes — your old password may have expired.
- An administrator may have just reset your password — check your work inbox for a reset notification.
Scenario 2: Account locked
Repeated wrong-password attempts can temporarily lock your account.
What to do:
- Wait a while and retry: Some organizations have auto-unlock.
- Contact your administrator for manual unlock: If you need access urgently.
To avoid this: If you're unsure of your password, use the Forgot Password flow rather than retrying repeatedly.
Scenario 3: Forgot password
If you have a standalone OmniStor account (created by an admin in OSM):
- On the sign-in page, tap Forgot Password.
- Enter your OmniStor ID and verification code.
- The system sends a password reset notification to your email.
- Follow the email instructions to reset.
- Sign in with the new password.
If you use an AD/LDAP account:
- Use your organization's standard corporate password reset process (usually the same as your work computer/email password).
- OmniStor doesn't handle AD password resets.
If you use an SSO account:
- Use your organization's identity platform's password reset process.
- OmniStor doesn't handle SSO password resets either.
Scenario 4: A two-factor verification page appears after sign-in
OmniStor 2.22.0+ supports two-factor authentication (2FA). If you see a verification code page:
- Check your email for a one-time password (OTP).
- Enter the code within 15 minutes.
- Correct code → sign-in succeeds.
- Wrong code or past 15 minutes → sign in again and request a new code.
2FA is currently supported for Navigate / iOS / Android. Other clients can still use password/SSO sign-in.
Didn't receive the email:
- Check your spam folder.
- Confirm the email address on file with OmniStor is correct — ask your admin to update if wrong.
- Wait a few minutes — email is sometimes delayed.
- Still nothing — contact your administrator to verify 2FA configuration.
Scenario 5: A mobile device binding page appears after sign-in
If your organization has enabled mobile device binding, you'll be guided through binding the first time you sign in on this phone/tablet:
- Follow the on-screen instructions to complete binding.
- Once done, sign-in proceeds normally.
Scenario 6: After SSO, the app doesn't respond
When you choose Single Sign-On, the OmniStor app redirects to your organization's identity platform. If you get stuck there:
- You see the org sign-in page but can't sign in → That's a message from your organization's identity system, not OmniStor. Follow the on-page guidance, or contact the IT team that manages organizational accounts.
- The popup never appears or stays blank → Check your network and whether your browser is blocking popups, then retry.
- SSO succeeds but the app doesn't respond → Quit the app, relaunch, and try again.
Scenario 7: Connection error / can't reach the server
If you can't even get to the credentials page, or you're stuck on a loading screen:
- Check the network: Can your phone reach other websites?
- Check the service URL: Did you type it correctly? Is it still valid?
- Try switching networks: From Wi-Fi to mobile data (or vice versa) — sometimes the issue is environmental.
- Corporate VPN: If the service URL is only reachable via your company network, confirm you're connected to VPN.
- App version too old: Try updating from the App Store / Play Store.
Quick decision table
| What you're seeing | Most likely cause | First step |
|---|---|---|
| Wrong account or password | Typo or expired password | Verify carefully; use Forgot Password |
| Account locked | Too many failed attempts | Wait for auto-unlock or contact admin |
| 2FA verification page | 2FA is enabled | Check email for the code |
| Mobile device binding page | First-time sign-in on this device | Follow on-screen binding steps |
| SSO flow stuck | Org identity system issue | Follow org page guidance or contact IT |
| Can't even reach the server | Network/URL/version issue | Check network, confirm URL, update app |
Still stuck?
Send the following to your administrator or support team:
- The full error message (screenshot ideal).
- Which sign-in method (Standard / AD/LDAP / SSO).
- The service URL you entered.
- Device model and OS version (iPhone 14 / iOS 17, Galaxy S23 / Android 13, etc.).
- OmniStor app version (check on the App Store / Play Store, or in Settings).
- Approximate time you tried to sign in.
- Whether quitting the app and relaunching changes anything.