Quantower bridge not connecting: “Bridge: connecting to Quantower on 127.0.0.1:7273…”

The Quantower bridge feeds Senzoukria from a running Quantower chart over 127.0.0.1:7273. A banner stuck on connecting means Quantower or its bridge add-on is not running; an orange “QT misconfigured” banner means ticks arrive without a sequence counter.

Senzoukria · Troubleshooting · Updated September 2026


At a glance

Message
“Bridge: connecting to Quantower on 127.0.0.1:7273…”
Port
7273 (the NinjaTrader bridge uses 7272)
Misconfiguration
Orange “QT misconfigured” banner, reason no-seq
Platform
Windows only

What you see

With “Quantower” as the chart data source (hint: “Local bridge — Quantower must be running”), the banner stays on “Bridge: connecting to Quantower on 127.0.0.1:7273…”, or shows “Bridge dropped. Reconnecting in {n}s…” after a drop.

If data arrives but without a sequence counter, a persistent banner starts with “QT misconfigured” and reads “QuantowerOrderflowBridge.cs is older than v2 (no seq counter on the wire) or Quantower Tick Replay is OFF — 100T bars won’t align with NT’s chart. Update the indicator and toggle Tick Replay ON in NT, then reconnect.” In 0.46.0 the end of that sentence still names NT; on this source the setting to check is Quantower’s tick-by-tick replay.

Why it happens

The Quantower bridge mirrors the NinjaTrader one: a plug-in inside Quantower listens on the loopback port and Senzoukria connects to it when the chart opens. Nothing listens when Quantower is closed, the add-on is not installed or failed to load, or it is not attached to a chart. Without tick-by-tick replay on that chart, the platform sends aggregated bars and the order flow is lost before it reaches the app.

How to fix it

  • Install the bridge add-on in Quantower’s own plug-in folder and restart Quantower; it must appear in the platform’s indicator or plug-in list under its own name.
  • Open a tick chart of the instrument and turn on tick-by-tick replay in that chart’s data settings.
  • Attach the bridge to that chart and keep Quantower open.
  • In Senzoukria, add a Quantower Bridge connection if you have not, and pick Quantower in the Chart data source selector. Bars appear, the last one moves and the badge stays on.

What it is not

  • Not a broker login problem: the bridge needs no credentials in Senzoukria.
  • Not a trading link: the ticket and account panels follow the broker connection, not the tick stream.
  • Not blocked by the NinjaTrader bridge: they use different ports, but a chart reads one data source at a time.

When to contact support

If the message comes back after these steps, report it from Menu → Report a problem or on the Senzoukria Discord. Say whether the add-on appears in Quantower’s list, and whether Quantower’s own log reports an error for it; a single broken add-on can hide the whole batch.

In the same section

This page in other languages

Frequently asked questions

Can I run the Quantower and NinjaTrader bridges together?
They listen on different ports (7273 and 7272), but each chart reads one data source at a time, chosen in the Chart data source selector.
Bars appear but carry no order flow. Why?
The platform is sending bars without ticks. Check that the Quantower chart is on ticks and that its tick-by-tick replay is on.

Keep reading