“Bridge: connecting to NinjaTrader on 127.0.0.1:7272…” never goes live
When the Senzoukria footprint stays on “Bridge: connecting to NinjaTrader on 127.0.0.1:7272…”, nothing is listening on that local port: NinjaTrader is closed, the OrderflowBridge indicator is not on a chart, or its port differs from 7272.
Senzoukria · Troubleshooting · Updated September 2026
At a glance
- Message
- “Bridge: connecting to NinjaTrader on 127.0.0.1:7272…”
- After a drop
- “Bridge dropped. Reconnecting in {n}s…”
- Port
- 7272 by default, loopback only
- Platform
- Windows only
What you see
With “NinjaTrader” chosen as the chart data source (hint: “Local bridge — NT8 chart must be running”), the banner stays on “Bridge: connecting to NinjaTrader on 127.0.0.1:7272…”. If the link was up and closed, it reads “Bridge dropped. Reconnecting in {n}s…” and the app retries on its own.
Why it happens
The bridge is an indicator, OrderflowBridge.cs, that runs inside NinjaTrader 8 and opens a listener on 127.0.0.1. Senzoukria connects to it; it never starts NinjaTrader itself. If NinjaTrader is closed, the indicator failed to compile, it is not added to a chart, or its Port property differs from the port Senzoukria uses, there is nothing to connect to. Closing NinjaTrader closes the bridge with it.
How to fix it
- Start NinjaTrader 8 and open a chart of the instrument you want.
- Check that OrderflowBridge.cs sits in Documents\NinjaTrader 8\bin\Custom\Indicators and compiles with 0 errors (NinjaScript Editor, F5).
- Add the indicator “OrderflowBridge” to the chart. NinjaTrader’s Output window should print “OrderflowBridge: listening on 127.0.0.1:7272”.
- Keep the indicator’s Port at 7272, the port Senzoukria connects to for NinjaTrader.
- In Senzoukria, pick NinjaTrader in the Chart data source selector. The banner moves to “Replaying history: …”, then the status bar shows LIVE.
What it is not
- Not a credentials problem: the bridge needs no broker login in Senzoukria.
- Not an internet problem: the connection stays on this machine (loopback).
- Not available on macOS or Linux: the bridge options are marked “Windows only”.
When to contact support
Still stuck after these checks? Use Menu → Report a problem, or post on the Senzoukria Discord. Include the last lines of NinjaTrader’s Output window and say whether the “listening on” line appeared.
Related pages
- NinjaTrader bridge misconfigured (Tick Replay)
- NinjaTrader bridge
- Bridge connection
- Quantower bridge not connecting
In the same section
- Databento book refused
- Anthropic refused this key
- Crypto DOM Profile: no live depth
- Alpaca unauthorized
- Python engine unavailable
- GEX key required
- Accepted but no data
- Subscription required or expired
This page in other languages
Frequently asked questions
- Do I have to keep NinjaTrader open?
- Yes. Both programs have to stay open; closing the platform closes the bridge.
- Can the bridge listen on another port?
- The indicator accepts ports from 1024 to 65535, but Senzoukria’s NinjaTrader source connects to 7272. Keep the default unless you know both sides use the same value.