Getting a vague “Something went wrong” right as you try to sign in is frustrating because it doesn’t tell you what failed: the connection, the login page, or your saved session.
Here’s a clean, practical checklist you can run through in about 10 minutes.
Before you start: if the app shows a specific error code anywhere, screenshot it. That tiny detail can change what you do next.
1. Check if the service is down (not you)
If the app’s servers are having issues, nothing on your device will fix it.
- Try signing in on a different device or on the web (if available).
- Search the app name + “status” or check their official social account for outage posts.
- If you can browse the app’s help pages but can’t authenticate, that often points to an auth outage.
If it’s a server-side problem, your best move is to wait and try again later (and avoid repeated attempts that might trigger temporary lockouts).
2. Toggle airplane mode, then switch networks
That generic error commonly happens when the connection is “kind of working” but unstable during the secure sign-in handshake.
- Turn on Airplane mode for 10 seconds, then turn it off.
- Switch between Wi‑Fi and mobile data.
- If you’re on Wi‑Fi, reboot the router if you can.
A quick network change forces a new route and DNS path, which can immediately clear the issue.
3. Disable VPN, iCloud Private Relay, and ad blockers (temporarily)
Sign-in flows often rely on redirects and security checks that VPNs and privacy relays can interfere with.
- Turn off VPN.
- On iPhone, try disabling iCloud Private Relay (if enabled).
- If you use a DNS/ad-blocking app (or “Private DNS” on Android), pause it briefly.
After you sign in successfully, you can re-enable these one by one.
4. Force close the app, then restart your phone
Some login errors are just a stuck session or a background process that didn’t finish properly.
- Force close the app completely (not just go back to the home screen).
- Restart your phone/tablet.
- Try signing in again once the device is fully back up.
It’s simple, but it clears a surprising number of “Something went wrong” loops.
5. Clear cached login data (cookies/site data) in the right place
Many apps use an embedded web view for login. That means browser cookies and cached redirects can break authentication.
- Android: Settings → Apps → (your app) → Storage → Clear cache. If needed, Clear storage/data (this signs you out and resets the app).
- iPhone/iPad: If the app uses Safari for sign-in, try Settings → Safari → Clear History and Website Data (this affects Safari too).
- Web: Clear cookies/site data for that specific site, not your whole browser, if possible.
If you clear storage/data, you may need to re-download offline content or re-enter settings.
6. Update the app (and your OS), then try again
Authentication methods change (security fixes, new endpoints), and older app builds can fail with generic errors.
- Update the app from the App Store / Google Play / your browser extension store.
- Install pending OS updates (iOS/Android/Windows/macOS) if they’re available.
If the app updated recently and sign-in started failing right after, note that timing—it helps if you need to contact support.
7. Make sure your device time and region are correct
Secure sign-in depends on certificates and timestamps. If your clock is off, logins can fail with unhelpful messages.
- Enable Set time automatically (and correct time zone).
- Restart the app and retry login.
This is especially common after traveling or changing SIMs.
8. Try an alternative sign-in method (and avoid repeated wrong attempts)
If you normally sign in with Google/Apple/Facebook, try email + password (or the reverse), if the app allows it.
- If there’s a “Continue with…” option, switch to another provider.
- If you suspect the password is wrong, use “Forgot password” instead of guessing—too many attempts can trigger a temporary block.
- Check your email for security prompts (new device approval, suspicious login alerts).
If you have 2FA enabled, confirm you’re receiving codes and that your authenticator app is working.
Final thoughts
Most “Something went wrong” sign-in errors come down to network/VPN interference or stale cached session data. Running the steps above in order usually resolves it without needing support.
If none of these work, collect screenshots, note the time it started, and contact the app’s support—those details help them trace authentication logs quickly.