NinjaSync Troubleshooting_

NinjaSync is not receiving webhooks

Check the following in order:

• —NinjaTrader 8 is running (the bridge only works while NT8 is open)
• —ngrok is enabled and connected (check the status at http://localhost:4003/settings)
• —The webhook URL in TradingView matches your ngrok domain exactly
• —If API key auth is enabled, the payload includes a valid auth_token

Orders are rejected or not filling

Verify the following:

• —The account field matches exactly what NinjaTrader shows (case-sensitive)
• —The ticker field uses a valid NinjaTrader instrument name (e.g. NQ MAR26)
• —Your broker account is connected and has sufficient margin
• —The market is open (futures trade Sun-Fri with a daily close)

License key shows as invalid

Ensure your Whop subscription is active. Expired or cancelled subscriptions will invalidate the license. If your subscription is active and the key still fails, try copying the key again from your email (avoid extra spaces). If the problem persists, contact support in Discord.

ngrok tunnel is not connecting

Common causes:

• —Auth token is missing or invalid — re-copy it from the ngrok dashboard
• —Static domain contains https:// — paste only the hostname
• —Firewall or antivirus is blocking ngrok — whitelist the ngrok process
• —Free ngrok domain was reclaimed — claim a new one in the ngrok dashboard

What is the latency of NinjaSync?

Typical end-to-end latency (TradingView alert fires → NinjaTrader order submitted) is 200-500ms. This includes TradingView webhook delivery, ngrok tunnel transit, and NinjaSync processing. Latency varies by internet connection and server load.

Which brokers does NinjaSync support?

NinjaSync works with any broker that connects to NinjaTrader 8. This includes NinjaTrader Brokerage, Interactive Brokers, Dorman Trading, Phillip Capital, and others. If your broker connects to NT8, NinjaSync will work with it.