Solving the Rithmic "No Handle" Error: Connecting Multiple Accounts in NinjaTrader

You've set up your second Apex or MyFundedFutures account in NinjaTrader, clicked Connect, and instead of a green light you get: "No Handle." The session just refuses to open.

This is one of the most common technical headaches for prop traders trying to scale beyond a single account on Rithmic-based firms. The cause is simple, and the fix is straightforward once you know what's actually happening.

What Causes the "No Handle" Error

Rithmic's architecture assigns a session "handle" to each active login. When NinjaTrader connects using a standard Rithmic adapter, it opens a direct session tied to your credentials. The problem: if those credentials are already active somewhere else — another NinjaTrader window, an RTrader Pro instance, or a session that didn't close cleanly — Rithmic won't issue a second handle for the same login.

Result: "No Handle." Connection refused.

This is a fundamentally different behavior from Tradovate, which uses API-based connections that don't have this single-session restriction. It's one of the primary reasons traders migrating to high-account-count setups prefer Tradovate-based prop firms when possible.

The Fix: RTrader Pro Plugin Mode

Rithmic's solution for multiple simultaneous connections is Plugin Mode, which runs RTrader Pro as a local server that NinjaTrader connects through — rather than each NinjaTrader instance connecting directly to Rithmic.

Step-by-step:

1. Download and install RTrader Pro from Rithmic's website if you don't have it already
2. Open RTrader Pro and log in with your Rithmic credentials
3. Enable Plugin Mode: Go to Tools → Settings → General → check "Enable Plugin Server"
4. Note the plugin port (default is usually 4001)
5. In NinjaTrader, go to Tools → Accounts → Add and select Rithmic as the connection type
6. Check "Use plugin connection" and enter the localhost port from RTrader Pro
7. Repeat this for each additional account — each account connects through the same RTrader Pro plugin instance

Once in Plugin Mode, NinjaTrader is no longer establishing independent Rithmic sessions. It's connecting through RTrader Pro, which manages the single session handle. Multiple accounts on the same credentials — or different credentials — can connect simultaneously without conflict.

Still Getting the Error After Plugin Mode?

A few things to check if the error persists:

• Old sessions not closed cleanly. Log into Rithmic's web portal and terminate any active sessions tied to your credentials. Stale sessions that didn't close properly can hold the handle even after you've restarted everything locally.
• Multiple RTrader Pro instances running. If you have more than one RTrader Pro window open — from a previous session that's still running in the background — they'll conflict. Check Task Manager and kill any residual processes.
• Firewall blocking the plugin port. Windows Firewall occasionally blocks the RTrader Pro plugin port. Add an exception for RTrader Pro in your firewall settings.
• VPS-specific issue. If you're running on a VPS and reconnecting after a disconnect, the previous session may not have timed out yet. Wait 2-3 minutes and retry, or log into Rithmic's portal to force-terminate the session.

Long-Term: Considering the Tradovate Alternative

Plugin Mode solves the No Handle error, but it adds a dependency — RTrader Pro needs to be running stably for all your NinjaTrader connections to work. If RTrader Pro crashes during a session, all connected accounts lose their feed simultaneously.

Tradovate's API connection in NinjaTrader doesn't have this dependency. Each account connects independently through the API, and a single account disconnect doesn't cascade to others. For traders running 10+ accounts, this architectural difference becomes more meaningful the more accounts you add.

If you're evaluating whether to migrate to a Tradovate-based firm setup, Copilink supports both Rithmic (via Plugin Mode) and Tradovate connections, so your copier configuration doesn't need to change as your infrastructure evolves.