PineConnector not working? 12 fixes, ranked.
Alert fired on TradingView, nothing happened on MT5. Every webhook bridge fails the same twelve ways — we run one ourselves, so we debug these daily and know exactly where to look first. Work through this list top to bottom — it is ranked by how often each cause is the real one — and your setup will be executing again in minutes. And if it keeps breaking, the last section shows how to switch bridges in 5 minutes without rewriting a single alert.
The 60-second checklist
| # | Symptom | Most likely cause |
|---|---|---|
| 1 | Nothing executes, ever | AutoTrading off in MT5 |
| 2 | EA loaded but silent | EA not allowed to trade / not attached |
| 3 | EA logs connection errors | WebRequest URL not whitelisted |
| 4 | Alerts fire, EA ignores them | Wrong or inactive license ID |
| 5 | Some alerts work, others don't | Alert message syntax |
| 6 | No alert ever arrives | Webhook URL missing or wrong |
| 7 | Webhook option greyed out | TradingView plan without webhooks |
| 8 | “Symbol not found” errors | Broker symbol suffix |
| 9 | Works at your desk, fails at night | PC or VPS asleep, MT5 closed |
| 10 | Worked for years, died in 2025 | MT4 support deprecated |
| 11 | Order sent, broker rejects it | Margin, lot size or market closed |
| 12 | Everything correct, still dead | Subscription or license lapsed |
The 12 fixes in detail
01AutoTrading is switched off in MT5
The single most common cause. If the Algo Trading button in the MT5 toolbar is red, no EA on that terminal can place orders — PineConnector included. Click it green, then check the EA shows a smiling status in the chart corner. It resets to off more often than you think: after terminal updates, crashes or restoring from sleep.
02The EA is not attached (or not allowed to trade)
The bridge EA must be attached to one open chart and its own settings must have Allow Algo Trading checked (right-click the EA on the chart → Properties → Common). If you recently changed profiles or closed the chart, the EA silently went with it.
03WebRequest URL not whitelisted
MT5 blocks outbound connections by default. Go to Tools → Options → Expert Advisors, tick Allow WebRequest for listed URL and add the exact URL your bridge's manual specifies. A trailing slash or http/https mismatch is enough to fail. If the EA log shows 4014 or “WebRequest not allowed”, this is it.
04Wrong or inactive license ID
PineConnector routes your alert to your terminal by the license ID at the start of the alert message. If it is mistyped, from another (expired) subscription, or you pasted the demo ID into a live setup, alerts arrive and get dropped. Copy the ID fresh from your PineConnector account page and compare character by character.
05Alert message syntax errors
PineConnector's comma syntax is strict: LICENSEID,buy,EURUSD,risk=1. Common breakers: spaces after commas, smart quotes pasted from a doc, uppercase/lowercase command typos (Buy vs buy), or a Pine Script alert() call that interpolates an empty variable. Test the exact string your alert actually sends — our free TradingView webhook tester parses PineConnector-format messages and shows you what a bridge would execute, in your browser.
06Webhook URL missing or wrong in the alert
In the TradingView alert dialog, the Notifications tab must have Webhook URL ticked and pointing at the exact URL from your bridge's docs. Alerts created before you enabled webhooks do not inherit it — edit each alert or recreate it. Remember every edit of an alert requires re-saving the webhook box.
07Your TradingView plan does not send webhooks
Webhook notifications require a paid TradingView plan (Essential and up). On the free tier the alert fires on screen but nothing is sent, so the bridge never hears about it. If the Webhook URL checkbox is greyed out, this is your answer.
08Broker symbol suffix mismatch
Your alert says EURUSD but your broker lists EURUSD.m, EURUSD.pro or EURUSDc. The EA cannot map one to the other unless told. Check the exact symbol name in MT5's Market Watch and either use it in the alert or configure the suffix in the EA settings.
09Your PC or VPS went to sleep
A local bridge setup only works while MT5 is running. Windows sleep, a VPS reboot, or your broker's terminal auto-logout at the weekend all kill execution silently. Disable sleep, keep the terminal logged in, or move the terminal to an always-on environment — that is exactly what SFCloud exists for ($6.99/mo, MT5 running 24/7 with the EA pre-installed).
10You are still on MT4
PineConnector deprecated MT4 support in October 2025. If your long-running MT4 setup died and nothing else changed, that is the reason. The move forward is an MT5 account (all major brokers and prop firms offer one) and a bridge built for MT5.
11The broker rejected the order
The bridge did its job; the broker said no. Check the MT5 Journal and Experts tabs for the real error: not enough margin, volume below the symbol's minimum lot, market closed (crypto weekends aside, forex closes Friday night), or order type not allowed on your account (hedging vs netting). The fix lives on the broker side: lot size, account type or timing.
12Your subscription or license lapsed
If a payment failed or the plan expired, the license goes inactive and alerts are dropped upstream — everything on your side looks fine. Log into your PineConnector account and verify the subscription status and renewal date before debugging anything else locally.
Still broken — or just tired of debugging at $39/mo?
Every bridge has bad days. The honest question is how much you pay per debugging session. PineConnector starts at $39/mo; its full pricing runs to $159/mo, VPS not included. SignalForge does the same TradingView → MT5 execution from $4.99/mo, adds Prop Firm Shield (drawdown protection for FTMO-style accounts), a news filter and Telegram alerts, and support is answered by the founder — usually the same day. The full side-by-side test with latency numbers is in our PineConnector vs SignalForge comparison.
Migrate in 5 minutes, keep your alerts: SignalForge parses PineConnector-format alert messages natively. Point your TradingView alerts at your SignalForge webhook URL, attach our EA to MT5, and your existing LICENSEID,buy,EURUSD,risk=1 alerts keep working — no rewriting. Verify any message first with the free webhook tester, then start the 14-day free trial (no card).
Prefer a clean start? The 5-minute webhook setup guide walks through the whole connection from zero, and the docs cover every payload format.
Author: Benjamin SF is the founder of SignalForge and an expert in trading algorithm automation. He builds and operates the SignalForge bridge for prop-firm traders and maintains its public latency benchmark (187 ms median).