I trade through TradingView every day, running a USDJPY momentum strategy with live broker connections. Over the past year, I've hit virtually every broker connection error the platform can throw. Disconnections during volatile moves, phantom login loops, order panels that show stale data, session conflicts between devices — all of it.
This guide covers every broker connection issue I've encountered and fixed, organized from the most common problems to the edge cases that will drive you crazy if you don't know what to look for.
Quick Diagnosis: Which Error Are You Seeing?
Before diving into fixes, identify your specific problem. TradingView broker connection issues fall into five categories:
| Symptom | Likely Cause | Jump To |
|---|---|---|
| "Not Connected" in Trading Panel | Session expired or login needed | Initial Connection Issues |
| Login fails with password error | Broker-side 2FA or session limit | Authentication Failures |
| Connected but orders rejected | Permission, symbol, or account mismatch | Orders Failing After Connection |
| Random disconnections mid-session | Session limits or network issues | Random Disconnections |
| Order panel shows but no data | Delayed data or subscription issue | Order Panel Shows No Data |
Initial Connection Issues
The Trading Panel Shows "Not Connected"
This is the most common starting point. You open your chart, click the Trading Panel at the bottom, and your broker shows as disconnected.
Fix checklist (in order):1. Click the broker name in the Trading Panel → Select "Connect." Many people miss this — TradingView doesn't auto-reconnect after sessions expire.
2. Check if you're logged into TradingView itself. If your TV session expired (common after browser updates or clearing cookies), the broker connection dies silently. Log back into TradingView first, then reconnect the broker.
3. Try a hard refresh. Press Ctrl+Shift+R (Windows/Linux) or Cmd+Shift+R (Mac) to force-reload without cache. A standard F5 refresh sometimes loads cached connection states.
4. Switch to a different browser or try incognito mode. Browser extensions (especially ad blockers, VPNs, and privacy tools) can block the WebSocket connections TradingView uses to talk to brokers. If it works in incognito, you've found your culprit.
5. Check TradingView's status page. Go to status.tradingview.com — if there's a platform-wide outage, no amount of troubleshooting will help. Wait it out.
First-Time Connection Setup
If you've never connected a broker before, here's what trips people up:
Step 1: Open any chart on TradingView. At the bottom of the screen, click the Trading Panel tab. If you don't see it, click the three-dot menu at the bottom bar and enable it. Step 2: Click "Connect Broker" or the broker selection dropdown. You'll see a list of supported brokers. As of 2026, major integrations include:- Crypto: OKX, Bybit, Bitget, Coinbase, Gemini
- Forex/CFDs: OANDA, FOREX.com, Pepperstone, FXCM, IG
- Stocks/Multi-asset: Interactive Brokers, Alpaca, TradeStation, tastytrade
> Common mistake: Trying to connect a broker that isn't on TradingView's supported list. Just because your broker offers good charts doesn't mean they have TradingView integration. Check TradingView's broker page for the current list.
Authentication Failures
"Invalid Credentials" When You Know the Password Is Right
This is maddening. You can log into your broker's own website, but TradingView rejects the same credentials.
Causes and fixes:1. Two-Factor Authentication (2FA) popup blocked. Many brokers require 2FA during the TradingView handshake. If your browser blocks the popup, the login silently fails with a generic "invalid credentials" message. Fix: Allow popups from tradingview.com in your browser settings, then try again.
2. Concurrent session limit reached. Most brokers allow only 1-2 active API/integration sessions. If you're already logged into your broker on their native app, TWS (for Interactive Brokers), or another third-party tool, the TradingView connection gets rejected. Fix: Log out of your broker's native platform, wait 30 seconds, then reconnect from TradingView.
This is especially common with Interactive Brokers — IB only allows one active session per user. If TWS is running on your desktop, TradingView can't connect simultaneously. You need to choose one or the other, unless you configure IB's Read-Only API mode.
3. Password changed recently. Some brokers cache OAuth tokens on TradingView's side. After a password change, the old token fails but the error message says "invalid credentials" instead of "token expired." Fix: In the Trading Panel, click the gear icon next to your broker → "Disconnect" → then reconnect fresh with new credentials.
4. Sub-account vs. main account. If your broker supports sub-accounts (like OKX), make sure you're logging in with the correct account level. Some integrations only work with the main account, not sub-accounts.
"Connection Limit Exceeded" Error
This means your broker limits how many simultaneous connections you can have, and you've maxed out.
For Interactive Brokers users:IB is the strictest about this. One account gets ONE connection. If you're running:
- TWS (Trader Workstation) on your desktop
- IB Gateway for your algo trading bot
- TradingView trying to connect
1. Close TWS or IB Gateway
2. Wait 60 seconds (IB takes time to release sessions) 3. Reconnect from TradingView 4. If you need both TWS and TradingView, use IB's Read-Only API setting in TWS → Global Configuration → API → Settings → check "Read-Only API" — this allows TradingView to connect for viewing, but orders must go through TWS For OKX users:OKX is more generous — multiple sessions are allowed. If you're hitting a limit, it's likely a rate-limit issue from too many rapid reconnection attempts. Wait 5 minutes and try again.
Broker Login Page Loops Endlessly
You click "Connect," the broker login page opens, you enter credentials, it redirects... and then asks you to log in again. And again.
This is almost always a cookie/browser issue:1. Clear cookies specifically for your broker's domain (not all cookies — just the broker's)
2. Disable browser extensions one at a time to find the culprit. Common offenders: Privacy Badger, uBlock Origin (in strict mode), DuckDuckGo Privacy Essentials 3. Try the TradingView desktop app instead of the browser version. The desktop app handles broker auth differently and avoids most extension conflicts 4. Check if your broker requires you to enable third-party login/API access in their settings. Some brokers (especially newer ones) require you to explicitly opt into TradingView integration from their own platform firstOrders Failing After Connection
You're connected — green status, live data flowing — but orders get rejected. This is a different category of problem.
"Insufficient Permissions" or "Trading Not Enabled"
Causes:1. Paper trading account connected instead of live. TradingView sometimes defaults to paper trading mode. Click the account selector in the Trading Panel and switch to your live account. For Interactive Brokers, this is a very common trap — IB has separate paper trading credentials (username usually starts with a "D" prefix for demo).
2. Trading permissions not set on your broker account. Even if you have a funded account, many brokers require you to explicitly enable trading for specific asset classes. For example:
- IB: You need trading permissions for each asset class (stocks, options, futures, forex) set up in Client Portal → Settings → Trading Permissions - OKX: Futures/perps trading requires switching to Trading Account mode and enabling derivatives3. API trading not enabled. Some brokers treat TradingView integration as API access. Check your broker's API settings — there may be a toggle you need to flip.
"Symbol Not Found" or "Invalid Instrument"
You see the chart fine, but when you try to place an order, the Trading Panel says it can't find the symbol.
Why this happens: TradingView uses its own symbol naming convention, which doesn't always map 1:1 to broker symbols. The chart data comes from TradingView's data feed, but orders go to your broker — and the broker might use different ticker formats. Fixes:1. Switch to the broker's data feed. In the chart header, click the exchange name next to the symbol. If you see options like "OANDA" or "IBKR" alongside "CBOE" or "NASDAQ," select your broker's feed. This ensures the symbol mapping is correct for orders.
2. Check if the instrument is available through your broker. Not every symbol on TradingView is tradeable through every broker. For example, you can chart Japanese yen futures on TradingView, but your forex broker might only offer USDJPY spot — and the TradingView panel tries to send a futures order.
3. Use the correct symbol format for crypto. On OKX's integration, you might need to select "BTCUSDT.P" for perpetual swaps vs. "BTCUSDT" for spot. The wrong suffix means order rejection.
Order Size Rejected
Your connection works, the symbol is right, but the order gets rejected for size.
Common reasons:
- Below minimum order size. Each broker has minimums. OKX: 0.001 BTC for spot. OANDA: 1 unit for forex. IB: varies by instrument.
- Position size exceeds account margin. The Trading Panel doesn't always show real-time margin calculations. Your order might be too large for your available margin.
- Decimal precision mismatch. Some brokers reject orders with too many decimal places. If your order for 0.12345678 BTC fails, try rounding to 0.1234.
Random Disconnections During Trading
Disconnects Every Few Hours
If your broker stays connected for a while but drops every 2-6 hours:
1. Session timeout. Many brokers expire inactive sessions. If you're charting but not actively trading, the broker connection can drop. Fix: Place a small "heartbeat" action occasionally, or simply reconnect when you're ready to trade.
2. TradingView connection limits by plan. Free and Basic plans have restrictions on simultaneous connections. If you're hitting plan limits, you'll get disconnected when TradingView needs to free resources. This is one reason to consider upgrading — TradingView Essential and above support more stable broker connections.
3. Network instability. WebSocket connections (which TradingView uses for live data and broker links) are more sensitive to network drops than regular HTTPS requests. If you're on WiFi, try a wired connection. If you're on a VPN, try without it.
Disconnects During High Volatility
This is the worst — you lose connection exactly when you need it most. During market-moving events, broker servers get slammed with requests and TradingView's broker bridge can fail.
Mitigation strategies:1. Keep your broker's native platform open as backup. I always have TWS or the broker's web interface ready in a separate tab during high-impact events. If TradingView drops, I can execute directly.
2. Set up TradingView alerts as a backup trigger. Even if the broker connection drops, TradingView alerts (webhook, email, app notification) still fire. You can react to the alert and place the order through your broker's own platform.
3. Don't rely on TradingView for stop-loss execution. Place your stop-loss orders directly with your broker, not through TradingView's Trading Panel. Broker-side stops survive disconnections. TradingView-side stops die when the connection drops.
> This is non-negotiable advice. If you're using TradingView's Trading Panel to manage risk with stop-losses, those stops only exist while TradingView is connected to your broker. A disconnection erases them. Always place critical risk management orders directly through your broker's platform.
Order Panel Shows Stale or No Data
Connected But Prices Are Frozen
The Trading Panel says "Connected" but bid/ask prices aren't updating, or they're significantly different from the chart.
1. You might be connected to a delayed data feed. Some broker integrations default to delayed quotes unless you have a specific market data subscription. Check your broker's data subscription settings.
2. Weekend/off-hours connection. If the market is closed, prices freeze at the last traded price. This is normal. The confusion arises when crypto traders expect 24/7 updates for forex symbols — those stop on Friday 5PM ET.
3. Stale session state. Click the disconnect button in the Trading Panel, wait 10 seconds, and reconnect. This forces a fresh data stream.
Trading Panel Shows Paper Account Positions
You're connected to your live account, but the Trading Panel displays positions from your paper account (or vice versa).
Fix for IB users: Interactive Brokers has separate paper and live accounts with different login credentials. Make sure you're using the correct one. Live accounts typically start with "U" followed by numbers. Paper accounts start with "D" followed by numbers. Fix for OKX users: In OKX's integration, make sure you've selected the correct account type (Trading Account vs. Funding Account). Positions only show for the account type you're connected to.Browser-Specific Fixes
Chrome
1. Go to chrome://settings/content/popups → Add tradingview.com to the "Allowed" list
chrome://settings/content/cookies → Make sure "Block third-party cookies" isn't blocking your broker's domain
3. Clear site data: chrome://settings/content/all → Search for "tradingview" → Delete → Reconnect
Firefox
1. Click the shield icon in the address bar → Disable Enhanced Tracking Protection for tradingview.com
2. Go toabout:preferences#privacy → Under Cookies → Add exceptions for your broker's domain
3. In about:config, ensure network.websocket.max-connections is at least 200 (default is 200, but some extensions lower it)
Safari
1. Safari → Settings → Privacy → Uncheck "Prevent cross-site tracking" temporarily while connecting your broker
2. After successful connection, you can re-enable it — the session token is usually persistent 3. If on iPad, force-close and reopen Safari — iPadOS sometimes caches stale WebSocket statesTradingView Desktop App
The desktop app avoids most browser-related issues. If you're having persistent connection problems in the browser:
1. Download the TradingView desktop app (available for Windows, Mac, and Linux)
2. The app uses its own Chromium engine, bypassing extension conflicts and cookie issues 3. Broker connections tend to be more stable in the desktop app because there are no competing browser processesBroker-Specific Connection Guides
OKX + TradingView
OKX and TradingView have a direct integration that includes a promotional offer — free TradingView Plus with qualifying OKX trading volume.
Common OKX issues:- Region restriction: OKX isn't available in certain regions (US, Singapore, etc.). If you're using a VPN to access OKX, the TradingView integration may detect the mismatch and block the connection.
- API vs. integration login: OKX's TradingView connection uses OAuth, not API keys. Don't try to paste API keys into the TradingView broker login.
- Sub-account limitation: The integration connects to your main OKX account. Sub-accounts aren't accessible through TradingView's Trading Panel.
Interactive Brokers + TradingView
IB's TradingView integration is powerful but has the strictest session management.
Key IB gotchas:- One session rule: IB allows only one active trading session. If TWS is open, TradingView can't connect (and vice versa). Decide which platform you'll trade from for the session.
- 2FA (IB Key) required: Every connection attempt requires IB Key authentication on your phone. If IB Key isn't working, you can't connect from TradingView either. See our IB 2FA troubleshooting guide for help.
- Paper vs. live account switching: IB paper and live accounts have completely different credentials. There's no "switch" button — you need to disconnect and reconnect with the other account's login.
- Market data subscriptions matter. If you trade US stocks through IB via TradingView, you need the appropriate market data subscription on your IB account. Without it, you'll see delayed data and some order types may be restricted. Check our IB market data subscription guide for which bundle you actually need.
OANDA + TradingView
OANDA's integration is one of the smoothest:
- Supports both live and demo accounts from the same login flow
- No single-session limitation — you can be on OANDA's own platform and TradingView simultaneously
- Common issue: OANDA's fxTrade vs. fxTrade Practice. Make sure you select the correct server (Live vs. Practice) when connecting
Prevention: How to Avoid Connection Issues
After dealing with hundreds of disconnections, here's my setup for minimizing problems:
1. Use the TradingView desktop app for any session where you plan to trade. Browser connections are less stable.
2. Bookmark your broker's native platform. Always have a backup execution method ready. TradingView is excellent for charting and casual order entry, but it's not a replacement for your broker's dedicated trading platform during critical moments.
3. Place stop-losses through your broker, not TradingView. I cannot stress this enough. Broker-side stops survive any TradingView disconnect. TradingView-side stops don't.
4. Set TradingView alerts for your key price levels. Alerts work independently of broker connections — they'll fire via webhook, email, or app notification even if your broker panel drops.
5. Don't trade from multiple devices simultaneously. One browser, one TradingView session, one broker connection. Multi-device setups cause session conflicts that are hard to diagnose.
6. Upgrade your TradingView plan if you're on Free or Basic. Higher-tier plans (Essential and above) get priority for connection stability and support more simultaneous features.
FAQ
Can I connect multiple brokers to TradingView at the same time?
Yes, but you can only have one broker active per chart tab. You can connect OKX for crypto charts and IB for stock charts in different tabs. You can't route an order from one chart to a broker connected in a different tab.
Does TradingView's broker connection work on mobile?
Yes, both the iOS and Android TradingView apps support broker connections. The setup flow is the same — open Trading Panel, select your broker, log in. Mobile connections tend to drop more frequently when the app goes to background, so don't rely on them for active position management.
What happens to my open positions if TradingView disconnects?
Your positions at the broker are completely unaffected. TradingView is just a window into your broker account — disconnecting TradingView doesn't close positions, cancel orders, or affect anything on the broker's side. The only exception: if you placed a stop-loss *through TradingView's panel* rather than directly with your broker, that stop may not persist.
Is it safe to enter broker credentials into TradingView?
TradingView uses OAuth for most broker connections — meaning your credentials go directly to your broker's authentication server, not through TradingView. However, for brokers that don't support OAuth, TradingView stores encrypted credentials. Check TradingView's security policy and your broker's integration documentation for details.
Why can I see a chart for a symbol but can't trade it?
TradingView aggregates data from many exchanges and data providers — far more than any single broker offers. Your chart might show CME gold futures data, but your forex broker only offers gold CFDs. The symbol you're charting needs to match an instrument available through your connected broker. Switch the chart to your broker's data feed to see only tradeable instruments.
My broker says TradingView integration isn't supported in my country. Any workaround?
No safe workaround. If your broker restricts TradingView integration by region, using a VPN to bypass it violates terms of service and could get your trading account suspended. Use your broker's native platform instead.
Bottom Line
TradingView's broker integration is convenient for everyday trading, but it's not bulletproof. The most important takeaway: never trust TradingView as your only execution layer. Use it for charting, analysis, and casual order entry. But for risk management — stops, position sizing, emergency exits — always go through your broker directly.
If you're spending more time troubleshooting connections than actually trading, consider whether TradingView's broker panel is adding value or adding friction. For most traders, the sweet spot is: chart on TradingView, execute on your broker's platform, and use TradingView alerts as the bridge between the two.
*Happy trading — and may your connections stay green.*