Skip to main content

Broker Connection Failed? Fix TradeLyser Link

A broker connection failed message blocks trade sync, live P&L, and accurate journaling until authorization succeeds again. This guide explains why TradeLyser cannot link to Zerodha, Fyers, Angel One, Upstox, 5Paisa, and other supported Indian brokers—and gives a practical order of fixes from credentials and API settings to browser and network issues.

Connection is separate from import: even perfect CSV history will not update automatically until the account shows Connected. Use this page alongside Trades Not Syncing when sync fails after you restore the link.

What “connection failed” means​

TradeLyser must complete one of two flows:

  1. OAuth (redirect login) — You sign in on the broker’s page and grant consent. TradeLyser receives a short-lived token.
  2. API key flow — You paste Client ID, API key, and secret (and sometimes redirect URL) from the broker developer portal.

If any step is rejected—wrong password, disabled API, mismatched redirect URL, popup blocked, or broker downtime—the UI shows Connection Failed or stalls on “Connecting…”.

Quick checklist​

CheckPass?
Broker website login works in a normal browser tab☐
API / developer access enabled in broker portal☐
Correct broker selected in TradeLyser connect wizard☐
Popups and third-party cookies allowed for OAuth☐
VPN or corporate firewall not blocking broker domains☐
No maintenance banner on broker status page☐

Common issues and detailed fixes​

1. Invalid or outdated credentials​

Symptoms: Immediate failure after entering username/password; “invalid credentials”; API key rejected.

Password changes at the broker do not automatically update TradeLyser. API keys copied with trailing spaces or from an old app registration also fail validation.

Fix:

  1. Log in to the broker site directly (not through TradeLyser) to confirm the password works.
  2. In TradeLyser, open Settings → Accounts → Reconnect or remove and add the account using the correct guide:
  3. For API brokers, generate a new key pair in the portal, paste fresh values, save, then connect.

Never share API secrets in email or chat—support will ask you to rotate keys instead.

2. OAuth session expired or incomplete​

Symptoms: Worked yesterday; today fails at redirect; blank page after broker login.

Zerodha Kite and Fyers commonly require daily authorization for third-party apps. Closing the OAuth window before the success redirect leaves TradeLyser unauthorized.

Fix:

  1. Click Reconnect on the account card.
  2. Complete the full broker login, 2FA, and Allow / Authorize screen.
  3. Wait until TradeLyser returns to the app with a success toast—do not navigate away early.
  4. Confirm status Connected on view connection status.

If you use multiple Kite profiles, ensure you authorize the same Client ID tied to the trading account you added in TradeLyser.

3. Broker API not enabled or misconfigured​

Symptoms: Error referencing API, redirect URI, or “access denied”; connection never reaches login.

Many brokers require you to enable API access, create an app, and whitelist redirect URLs before third-party tools work.

Fix:

  1. Open the broker’s API / Developer / SmartAPI section.
  2. Enable trading or read permissions required for trade history (read-only is insufficient if the broker bundles permissions).
  3. Set redirect URL exactly as shown in TradeLyser’s connect screen (scheme, host, no trailing slash mismatch).
  4. Regenerate keys if the app was deleted or set to inactive.
  5. Retry connection from TradeLyser.

Angel One SmartAPI and Upstox v2 setups are especially sensitive to redirect URI typos.

4. Browser, popup, and cache issues​

Symptoms: Stuck on connecting; OAuth window does not open; works in one browser only.

Ad blockers, privacy extensions, and strict third-party cookie settings block OAuth redirects. Stale cache can serve old connect scripts.

Fix:

  1. Allow popups for app.tradelyser.com and your broker domain.
  2. Try Chrome or Edge (recommended) in a private/incognito window with extensions disabled.
  3. Hard refresh: Ctrl+F5 (Windows) or Cmd+Shift+R (Mac).
  4. Clear site data for TradeLyser once, then reconnect.
  5. Disable VPN temporarily—some VPN nodes are blocked by brokers.

For UI loading problems after login, see Dashboard Not Loading.

5. Network, firewall, and DNS​

Symptoms: Timeout; “network error”; works on mobile data but not office Wi‑Fi.

Corporate networks and ISP filters sometimes block broker API endpoints or WebSocket handshakes.

Fix:

  1. Switch to mobile hotspot to isolate network policy.
  2. Disable VPN or proxy.
  3. Flush DNS or try another DNS resolver if only one broker domain fails.
  4. Retry after 15 minutes if the broker reports regional latency.

6. Wrong broker or account type selected​

Symptoms: Connection “succeeds” but wrong ledger; equity vs commodity mismatch.

Selecting the wrong broker template maps fields incorrectly and may fail validation for your file or API payload.

Fix:

  1. Disconnect the incorrect account (disconnect broker).
  2. Add again and pick the exact broker and segment you trade.
  3. For multiple logins, use add multiple accounts with clear labels.

7. Broker maintenance or incident​

Symptoms: Failure across all users; broker app also unstable; known incident posts.

Fix:

  1. Verify status on the broker’s official channel.
  2. Retry after maintenance window.
  3. Import critical sessions via CSV until API returns.
  4. Resume sync with sync broker trades.

Verification workflow (do in order)​

  1. Independent broker login — Proves credentials are valid.
  2. API portal — App active, redirect URL correct, keys fresh.
  3. Reconnect in TradeLyser — Full OAuth or API flow to success state.
  4. Connection status — Green Connected, no warning banners.
  5. Test sync — Manual sync imports at least zero new rows without auth error (sync guide).
  6. Sync History — Latest job Success (sync history).

If step 5 fails but step 4 passes, continue with Trades Not Syncing—the link is live but data pipeline needs separate fixes.

OAuth vs API key: which flow am I using?​

FlowTypical brokersYour responsibility
OAuth redirectZerodha, FyersDaily or periodic re-login; allow popups
API keys + secretAngel One, Upstox, othersKeep portal app active; rotate keys safely

The connect wizard in TradeLyser states which fields are required. Do not mix Zerodha API keys into the Fyers flow or vice versa.

Security best practices​

  • Rotate API keys if you suspect they were exposed.
  • Use broker portals to revoke old app tokens you no longer need.
  • Enable login alerts on your TradeLyser account.
  • Review secure your account if you share devices.

TradeLyser staff will never ask for your broker password.

When to contact support​

Email support@tradelyser.com after the verification workflow if:

  • Broker login works but TradeLyser fails on every browser
  • Error message references an internal code you cannot resolve
  • OAuth redirect returns an error page from the broker

Include: broker name, screenshot of the error, browser and OS, time of attempt (IST), and whether incognito mode changed the result. See Contact Support for the full template.

Frequently asked questions​

Do I need a paid broker plan to connect?​

Requirements vary by broker; most retail Kite and Fyers users connect with standard accounts if API/OAuth is enabled. Check your broker’s API documentation.

Why does Zerodha need login every day?​

Kite’s third-party token policy limits session length for security. Reconnect is normal, not a TradeLyser bug.

Can I connect the same broker twice?​

You can connect multiple accounts if they are different client IDs; duplicate labels for the same login cause confusion—use multiple accounts carefully.

Will disconnecting delete my trades?​

Disconnect stops future sync; existing journal trades remain unless you delete them separately.

Connection works but sync fails—is this the right guide?​

Partially. Fix connection first, then trades not syncing.

Does 2FA break OAuth?​

No if you complete 2FA on the broker page during redirect. Automated scripts cannot bypass 2FA—that is expected.

Are API keys stored securely?​

TradeLyser encrypts credentials at rest; still treat keys as secrets and rotate if leaked.

Connection error messages (what they usually mean)​

Message or behaviorInterpretationNext step
Invalid redirect URIPortal app URL ≠ TradeLyser callbackCopy exact URL from connect screen into broker app
Access denied / consent declinedOAuth cancelledRun Reconnect; click Allow on broker
Invalid API keyWrong or revoked keyRegenerate in broker portal; paste without spaces
Timeout / network errorLocal network or broker latencyHotspot test; retry after 15 minutes
Account already linkedSame Client ID on another TradeLyser loginUse correct login or disconnect old link
2FA failedIncomplete loginFinish OTP on broker page before closing tab

Capturing the exact string (screenshot) in your support email saves one full round trip.

Multi-device and shared computer tips​

If you connect from office PC and later from laptop, each browser profile maintains its own session. OAuth failures after switching devices usually mean you need Reconnect on the device you use for journaling—not that the other device “broke” the link.

On shared computers, always log out of TradeLyser and the broker site, and avoid saving broker passwords in the browser if others use the machine.

Table of Content