TradingView Webhook Not Working? 10 Fixes That Actually Work

TradingView Webhook Not Working is a game-changer for traders. You've set up your TradingView alert with a webhook URL, but nothing happens when it fires. Or worse — it works sometimes and fails randomly. Here are the 10 most common causes and proven fixes.

TradingView Webhook Not Working: 1Wrong TradingView Plan

Problem: Webhook alerts are only available on TradingView's paid plans (Essential and above). The free plan doesn't support webhooks.

Fix: Upgrade to at least TradingView Essential. Check your alert creation dialog — if you don't see the "Webhook URL" field, your plan doesn't support it.

2URL Not Publicly Accessible

Problem: You're using http://localhost:3000 or http://192.168.1.x:3000 as your webhook URL. TradingView's servers can't reach your local network.

Fix: You need a public URL. Options:

• TradingView Copier Pro: Automatically creates a Cloudflare Tunnel with a public URL — zero configuration
• VPS with public IP: Set up a server with a static public IP and SSL
• Port forwarding: Forward port 3000 on your router (not recommended — security risk)

3Missing HTTPS

Problem: TradingView requires webhook URLs to use HTTPS, not HTTP. If your URL starts with http://, the webhook will be rejected.

Fix: Ensure your webhook URL uses https://. TradingView Copier Pro's Cloudflare Tunnel provides HTTPS automatically.

4Invalid JSON in Alert Message

Problem: Your alert message contains malformed JSON. Common errors:

• Using single quotes instead of double quotes: {'action': 'BUY'} ← wrong
• Trailing commas: {"action": "BUY",} ← wrong
• Unquoted values: {"qty": .5} ← wrong
• Smart/curly quotes from copy-pasting: {“action”} ← wrong

Fix: Use valid JSON with double quotes. Test your message at jsonlint.com:

{"action": "BUY", "ticker": "EURUSD", "qty": 0.1}

5Webhook URL Changed (Tunnel Restart)

Problem: If you restart your copier or tunnel, the public URL may change. The old URL in your TradingView alert is now dead.

Fix: After restarting, check your new webhook URL in the TradingView Copier Pro dashboard and update the alert. For a permanent URL, run the copier on a VPS where it rarely restarts.

6Alert Condition Never Triggers

Problem: The webhook is fine — the alert condition itself never fires. This happens when:

• The strategy condition depends on the bar closing, but you set "Once per bar close" and the bar hasn't closed yet
• The symbol or timeframe on the chart doesn't match what your strategy expects
• The alert expired (TradingView alerts have expiration dates)

Fix: Check the alert in TradingView's Alerts panel. If it shows "Stopped" or "Expired", recreate it. Set expiration to "Open-ended" if your plan supports it.

7Server Returns an Error

Problem: TradingView sends the webhook, but your server returns a 4xx or 5xx error. TradingView shows a "Webhook notification failed" message in the alert log.

Fix: Check your copier's Trade Log for error messages. Common causes:

• 400: Invalid JSON or missing required fields in the alert message
• 500: Server crash — check the copier app logs
• 502/503: Tunnel or proxy error — restart the copier

8Firewall Blocking Incoming Connections

Problem: Your Windows Firewall or antivirus is blocking the incoming webhook connection.

Fix: If using a Cloudflare Tunnel (like TradingView Copier Pro), this isn't an issue — the tunnel establishes an outbound connection from your machine. No inbound ports need to be open. If you're running a bare server, add a firewall rule for your port.

9Computer Went to Sleep

Problem: Your computer went to sleep or hibernated. The copier process paused, the tunnel disconnected, and TradingView got a timeout.

Fix:

• Disable sleep mode: Windows Settings → System → Power → set "Sleep" to "Never"
• Better: Run on a Windows VPS that never sleeps ($5–$15/month)

10TradingView's Own Delays

Problem: TradingView occasionally delays webhook delivery during high-traffic periods (market open, major news events). This isn't your fault.

Fix: You can't fix TradingView's infrastructure, but you can minimize downstream delay. A local copier processes the webhook the instant it arrives — there's no additional queue or cloud server adding latency.

Quick Diagnostic Checklist

1. Is your TradingView plan Essential or higher? ✅
2. Does your webhook URL start with https://? ✅
3. Is the URL publicly accessible (not localhost/LAN)? ✅
4. Is your alert message valid JSON? ✅
5. Is the copier app running? ✅
6. Is AutoTrading enabled in MT5? ✅
7. Is the EA attached to a chart? ✅
8. Is your computer awake and connected to the internet? ✅
9. Has the alert expired? ✅
10. Check the Trade Log for received webhooks ✅