Verification Error “Something Went Wrong” — what to check first (before you retry)
Steve H.
Expert ★★★★★ 27,853 satisfied customers
Specialities: verification error triage (“Something went wrong”), account recovery step failures, MFA/2FA delivery and retry limits, browser cookies/session problems.
When verification shows “Something went wrong,” start with safe checks: time/date, cookies, network, updates, and retry limits (so you don’t trigger a lockout)
Technician
A verification error that simply says “Something went wrong” is usually not your fault. It often means the verification step can’t complete because of a temporary block, a session/cookie problem, or a small device setting (like time/date) that prevents the security check from finishing.
I don’t want you to keep retrying and accidentally trigger a longer cooldown. We’ll start with the least risky checks first.
Quick questions so I understand the situation:
1) Which platform is this (Google, Microsoft, Apple, banking, social media, etc.)?
2) Where do you see the message — in a web browser, in an app, or both?
3) Are you trying to receive a code by email, text message (SMS), or an authenticator app?
Technician
Let’s treat “Something went wrong” as a signal that something in the environment is blocking the verification step. A few common reasons (no technical jargon):
• Retry limits / cooldown: too many requests in a short time.
• Network issues: Wi-Fi filtering, weak signal, or a VPN/proxy used earlier.
• Device settings: wrong time/date/timezone can break secure codes.
• Browser/app session: cookies blocked, strict tracking protection, or an outdated app.
First: do you see the error immediately when you click “Send code,” or after you enter a code?
Technician
Two calm, low-risk checks (no account changes):
1) Time & date: On your phone and laptop, confirm “Set time automatically” is on and the timezone is correct. I know it sounds simple, but this one causes surprising verification failures.
2) One attempt, then pause: If you’ve already clicked “Send code” several times today, it’s safer to stop for a bit. Some systems silently limit attempts and show vague errors like this.
Also, were you traveling, using a new router, or did you install a privacy tool (VPN, DNS ad blocker, security app) around the time recovery happened?
Technician
Some verification pages need to contact several security services. If the router’s ad-blocking DNS or a browser blocker prevents those services from loading, the site may fail with a generic “Something went wrong” message.
Trust moment: I’m not going to ask you to turn off security everywhere. We’ll only do a safe test to see if the network is the trigger.
Safe diagnostic question (different order): does this happen on home Wi-Fi only, or also if you use a mobile hotspot (your phone’s internet shared to the laptop) for one single attempt?
Technician
The hotspot test is temporary and reversible. It doesn’t change your account, password, or recovery options. It only answers one question: is your home network blocking verification?
If you prefer not to do hotspot, we can still narrow it down with other low-risk checks:
• Try a different browser (Chrome vs Edge vs Safari) or a private window, for one attempt only.
• Temporarily pause the ad blocker only on the sign-in page, then turn it back on.
• Check for “too many attempts” or “try again later” wording anywhere on the page — sometimes it’s small.
When did it start — immediately after recovery, or after you updated the phone/laptop?
Technician
1) Post-recovery security sensitivity (stricter checks for a while).
2) A temporary cooldown from multiple verification requests.
Senior-friendly guidance: the safest approach is fewer attempts, better notes, and controlled testing — not repeated clicking.
Two more questions to keep it practical:
• Are you trying to verify with a landline or a mobile number that can receive texts?
• Do you have any other verification option listed, like “use another method,” a backup email, or a prompt on a trusted device?
Technician
Here’s a safe way to think about it:
• “Something went wrong” often appears when the system can’t send the code because of a limit, a network block, or a verification method that is temporarily unavailable.
• Missing backup emails can be a separate issue (spam, inbox rules, blocked senders, or delays).
Trust moment: I don’t want you to reset your password again “just to try something.” That can add more security checks.
If you can do one controlled test later: try the verification on mobile data (turn Wi-Fi off on your phone) for a single attempt. If that works but home Wi-Fi doesn’t, we’ve identified the cause without touching your account settings.
Technician
Write down:
• Exact wording (“Something went wrong,” “Try again later,” or anything else).
• Where it happens (web browser vs app; laptop vs phone).
• Network (home Wi-Fi vs mobile data/hotspot).
• Timing (right after recovery; after an update; how many attempts you made).
Security reminder: never share verification codes with anyone who messages you or calls you. Real verification should only happen inside the sign-in screen.
Technician
One last gentle tip: if you see any message that suggests a waiting period, treat it seriously. Waiting can feel frustrating, but it often allows the verification system to “cool down.”
If the error changes (for example, it starts offering a different method), note that too — it usually means the system is allowing verification again.
Quick answer: the accepted fix
Most “Something went wrong” verification errors improve when you do these safe checks (no risky account changes):
• Confirm automatic time/date and correct timezone on phone + computer.
• Avoid rapid retries — do one attempt, then pause if you see “try again later” (cooldown/retry limits).
• Test Wi-Fi vs mobile data/hotspot once to spot router/DNS ad-blocking or network filtering.
• Try a different browser or a private window (cookies/session issues), then stop if it repeats.
• Make short notes (error text, device, network, time) so support can understand the pattern.
Why “Something went wrong” happens during verification
This message is often a general error used when the system can’t complete a security step. Common triggers include retry limits after too many code requests, network blocking (router protection, DNS ad blockers, VPN/proxy), and session problems (cookies blocked, strict tracking settings, outdated browser/app). It can also appear more often right after account recovery because the platform applies stricter checks for a period of time.
Safe checks before you change passwords or recovery options
Start with changes you can easily reverse. Confirm the device time/date, try one sign-in attempt on a different network, and test a different browser or private window. Avoid repeated clicks on “Send code,” because that can extend cooldowns and reduce available verification methods. If emails are delayed, check spam, inbox rules, and blocked senders before requesting more messages.
Security tip: don’t share codes with anyone
Verification errors can attract scams.
If someone texts, emails, or calls asking for your verification code, password, or recovery link, treat it as suspicious. Real verification should happen only inside the sign-in screen for the service you are using. Stick to low-risk checks (time/date, network test, cookies) and keep short notes you can share with the platform’s support channels.
Disclaimer: This information is AI-generated and intended for general guidance only. Steps vary by device, region, and service. For exact instructions for your setup, consult a verified expert or the manufacturer’s support site.
Getting Started Is Easy
Low-risk diagnosis
Identify whether the verification loop is driven by risk signals, cookie/session persistence, or blocked security resources.
Reduce security friction
Learn why repeated attempts can trigger cooldowns and how to test safely without escalating lockouts.
Escalation-ready notes
Collect the exact prompts, timestamps, and environment differences so official support can triage faster.
FAQ
Why did the verification error “Something went wrong” start suddenly?
It often appears after a recovery attempt, many retries, or a change in your internet connection. The platform may apply stricter security checks for a period of time. Network filtering (router protection, DNS ad blockers, VPN) can also block the verification step. Start with low-risk checks before trying again.
Can this happen after an update?
Yes. After an update, an app may need a restart, or permissions/settings may change. A browser update can also change cookie or tracking protection rules. If verification suddenly fails after an update, try one attempt in a different browser or on mobile data. Avoid repeated retries while testing.
Is this a hardware problem or a settings problem?
Most of the time it’s a settings or connection issue, not broken hardware. Incorrect time/date, strict privacy settings, blocked cookies, or network filters are common causes. If you can sign in on one device but not another, that’s a strong clue it’s not hardware. A simple network comparison (Wi-Fi vs mobile data) can also confirm it.
Can this be fixed without service or repair?
Usually, yes. Many cases improve with safe checks: correct time/date, fewer retries, and testing a different network or browser. If a cooldown is active, waiting can be part of the solution. If it continues, keep notes (error text, device, network, time) so the provider can help faster.
Sources
- Microsoft Support — Troubleshoot Microsoft account verification code issues
- Google Account Help — Fix common issues with 2-Step Verification
- Apple Support — Get a verification code and sign in with two-factor authentication
- Microsoft Support — Common problems with two-step verification
Filed under: Account Access Help
Related articles
- Verification completed… so why am I still not receiving emails?
- Not receiving verification emails — I clicked “Send code” but nothing arrives
- Not receiving emails, but I can send — what do I check first?
- Invoice emails missing from inbox — I can’t find them anywhere
- Emails stopped arriving overnight — what to check first (without changing anything risky)
- Verified my email… and now emails stopped arriving — what do I check first?
- Emails stopped arriving after using a VPN — what to check first (safely)
- Emails stopped arriving after travel — am I missing new mail or is it blocked?
