Account connection opens but nothing happens: troubleshooting guide

TL;DR — If you click "Connect account" and nothing seems to happen, the most common causes are a blocked pop-up, browser extensions blocking the login window, or third-party cookies/session storage being blocked. Start by trying the connection in a private/incognito window with extensions disabled, then retry in your provider's dashboard. Reading time: ~6 min

The scenario

It is the middle of a normal workday, you are trying to connect Google, Microsoft, GitHub, or another external account to your app, and the button just sits there. No success message, no error banner, maybe a spinner flashes for a second and disappears. You try again, maybe in another tab, and still nothing changes in the dashboard. It feels like the app ignored you, and now you are not sure whether to keep clicking or stop before you make it worse.

Symptoms

• You click Connect account, Sign in with Google, Authorize, or similar, and no new window appears.
• A new window briefly opens and immediately closes, but the account still shows as Not connected.
• The page refreshes and returns to the same screen with no confirmation.
• You see browser messages like:
  • Pop-up blocked
  • This page was prevented from setting cookies
  • Third-party cookies blocked
  • ERR_BLOCKED_BY_CLIENT
• In the browser developer console (the browser's built-in debug panel), you may see lines like:
  • Failed to open popup window
  • Blocked a frame with origin ...
  • Cookie “...” has been rejected
  • 401 Unauthorized
  • 403 Forbidden
  • redirect_uri_mismatch
  • invalid_state
• The account provider login page works, but after approval you land back on the app and nothing is connected.

Likely causes

Step-by-step diagnosis

1. Try the connection in a private/incognito window first.

   • Menu path: Browser menu → New Incognito Window or New Private Window.
   • Then sign into your app and click Connect account again.
   • This is your problem if: it works in private/incognito.
   • Jump to: Fixes → Privacy setting, ad blocker, or extension blocked the login flow or Fixes → Third-party cookies or cross-site storage blocked.

2. Check for a blocked pop-up.

   • Menu path: Click Connect account, then look at the right side of the browser address bar for a pop-up blocked icon.
   • In many browsers you can click it and choose Always allow pop-ups and redirects from this site.
   • This is your problem if: allowing pop-ups makes the provider login window appear.
   • Jump to: Fixes → Pop-up blocked by the browser.

3. Temporarily disable extensions for this test.

   • Menu path: Browser menu → Extensions → disable ad blockers, privacy tools, script blockers, and password-manager autofill helpers one by one.
   • Retry the connection after disabling them.
   • This is your problem if: the connection works after one extension is disabled.
   • Jump to: Fixes → Privacy setting, ad blocker, or extension blocked the login flow.

4. Check cookie/privacy settings.

   • Menu path: Browser Settings → search for cookies or third-party cookies.
   • Temporarily allow third-party cookies, or add site exceptions for your app domain and the provider domain.
   • This is your problem if: after allowing cookies, the login completes and the account shows as connected.
   • Jump to: Fixes → Third-party cookies or cross-site storage blocked.

5. Retry with the correct provider account in a clean session.

   • Open a private/incognito window, go directly to the provider first (for example Google, Microsoft, GitHub), sign out, then return to your app and start the connection again.
   • This is your problem if: you are prompted to choose an account again and the connection succeeds with the right one.
   • Jump to: Fixes → You are already signed into the wrong account or a stale session is stuck.

6. If you manage the provider app settings, verify the redirect/callback URL.

   • Menu path: In your provider's dashboard (for example Google Cloud, Microsoft Entra, GitHub OAuth app), open the application/client used for the connection and find Redirect URI, Callback URL, or Authorized redirect URLs.
   • Compare it exactly to the callback URL shown in your app's setup instructions.
   • This is your problem if: even one character differs, including http vs https, trailing slash, subdomain, or path.
   • Jump to: Fixes → Redirect URL mismatch in the connected provider.

7. Test from another network.

   • Disconnect from office VPN or corporate Wi‑Fi and try from a mobile hotspot.
   • This is your problem if: the connection works on the hotspot but not on the original network.
   • Jump to: Fixes → Network or firewall blocks the provider login domain.

8. Check for browser console errors before contacting support.

   • Menu path: Browser menu → More tools → Developer tools → Console.
   • Retry the connection and copy the red error lines.
   • This is your problem if: you see errors like ERR_BLOCKED_BY_CLIENT, redirect_uri_mismatch, invalid_state, or repeated 401/403 requests.
   • Jump to: the matching fix below, or send the exact errors to support.

Fixes

Pop-up blocked by the browser

1. Click the pop-up blocked icon in the address bar.
2. Choose Always allow pop-ups and redirects from [site].
3. Refresh the page and click Connect account again.

If you need the browser setting path:

• Chrome: Settings → Privacy and security → Site settings → Pop-ups and redirects
• Edge: Settings → Cookies and site permissions → Pop-ups and redirects
• Firefox: Settings → Privacy & Security → Permissions → Block pop-up windows
• Safari: Settings → Websites → Pop-up Windows

Verify it worked: clicking Connect account opens the provider login/approval window and the app returns with the account marked Connected.

Privacy setting, ad blocker, or extension blocked the login flow

1. Disable extensions that commonly interfere: ad blockers, anti-tracking tools, script blockers, privacy extensions.
2. Retry the connection.
3. Re-enable extensions one at a time to find the one causing the issue.
4. Add an allow rule for your app domain and the provider domain in that extension.

Common browser path:

• Chrome/Edge: Menu → Extensions → Manage Extensions
• Firefox: Menu → Add-ons and themes → Extensions
• Safari: Settings → Extensions

If you see this console error, it strongly points here:

ERR_BLOCKED_BY_CLIENT

Verify it worked: the connection succeeds with the extension disabled, and still succeeds after you add an allow rule and re-enable it.

Third-party cookies or cross-site storage blocked

1. Open browser settings and search for third-party cookies.
2. Temporarily allow third-party cookies, or add site exceptions for:
   • your app domain
   • the identity provider domain (for example accounts.google.com, login.microsoftonline.com, github.com)
3. Refresh the app and start the connection again.

Typical paths:

• Chrome: Settings → Privacy and security → Third-party cookies
• Edge: Settings → Cookies and site permissions → Manage and delete cookies and site data
• Firefox: Settings → Privacy & Security → Enhanced Tracking Protection
• Safari: Settings → Privacy

Verify it worked: after approval at the provider, you return to the app and the account stays connected instead of silently returning to the same screen.

Redirect URL mismatch in the connected provider

If you control the provider app/client settings, update the callback URL to exactly match the one your app expects.

Examples of what must match exactly:

https://app.example.com/oauth/callback
https://app.example.com/oauth/callback/
http://app.example.com/oauth/callback
https://www.example.com/oauth/callback

These are all different.

Typical provider path:

• In your provider's dashboard, open the application/client used for sign-in.
• Find Redirect URI, Callback URL, or Authorized redirect URLs.
• Paste the exact callback URL from your app's setup page.
• Save changes, then retry the connection.

If you see one of these errors, this is likely the cause:

redirect_uri_mismatch
invalid_request

Verify it worked: the provider approval page completes without error and returns to the app with the account shown as Connected.

You are already signed into the wrong account or a stale session is stuck

1. Open a private/incognito window.
2. Go to the provider site directly and sign out of all accounts there.
3. Return to your app in the same private/incognito window.
4. Start the connection again and choose the correct account when prompted.

If the app has a Disconnect button for the half-finished connection, click that first, then retry.

If you see this error, it often points to a stale session:

invalid_state
session expired

Verify it worked: you are asked to choose the account again, and the selected account appears correctly in the app after approval.

Network or firewall blocks the provider login domain

1. Disconnect from VPN if you are on one.
2. Try the same connection from a different network, such as a mobile hotspot.
3. If it works there, ask your IT team to allow the provider login domain and your app domain.

Examples of domains that often need to be allowed:

accounts.google.com
login.microsoftonline.com
github.com
<your-app-domain>

Verify it worked: the connection fails on the original network but succeeds on the hotspot; after the allow rule is added, it succeeds on the original network too.

Temporary outage or JavaScript error on the page

1. Refresh the page fully.
   • Windows/Linux: Ctrl+Shift+R
   • macOS: Cmd+Shift+R
2. Open the browser console and retry the action.
3. Copy the red error lines and send them to support along with the time of the test and your browser version.

Example errors to capture:

Uncaught TypeError: Cannot read properties of undefined
401 Unauthorized
403 Forbidden
500 Internal Server Error

Verify it worked: after a refresh or after support resolves the issue, the connection completes normally without red console errors.

Prevention

• Add your app and provider domains to browser/site allow lists before onboarding users. Keep a short internal checklist like:

Allow pop-ups for: https://app.example.com
Allow cookies for: https://app.example.com
Allow provider login: https://accounts.google.com

• If you manage OAuth settings, store callback URLs in one source of truth and copy from there into each provider dashboard. Example checklist file:

Production callback: https://app.example.com/oauth/callback
Staging callback: https://staging.example.com/oauth/callback

• Test account connection in a clean browser profile before releasing changes. A simple release check can be:

1. Open private window
2. Connect Google test account
3. Disconnect
4. Reconnect Microsoft test account

• Add front-end error monitoring for failed connection flows so support can see real errors instead of "nothing happened". Capture at least:

{
  "event": "oauth_connect_failed",
  "provider": "google",
  "error": "redirect_uri_mismatch",
  "browser": "Chrome 141",
  "path": "/settings/integrations"
}

• If your team controls the app, log callback failures server-side with the provider name and reason. Useful fields:

{
  "provider": "microsoft",
  "status": 400,
  "error": "invalid_state",
  "user_id": "12345"
}

• Keep a customer-facing fallback path in your help docs: "If the connect button does nothing, retry in a private/incognito window with extensions disabled." That one step resolves a large share of these cases quickly.

This article was written by an AI system and published pending human review. Verify anything you intend to act on.