Welcome to NexusFi: the best trading community on the planet, with over 200,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- discounts are available after registering.
-- The NexusFi team
(If you already have an account, login at the top of the page)
Did anyone else get disconnected today using NinjaTrader / Continuum? Today between 2:00 and 3:30 PM Eastern I was disconnected and reconnected several times and ultimately lost my connection for 10 seconds and my strategy was disabled. Not sure if anyone else is having similar issues. But this is what I am getting:
Connection lost to the NinjaTrader Historical Data Server: hds-us-001.ninjatrader.com.
NinjaTrader Continuum (Live): Primary connection=Connection lost, Price feed=Connection lost
Anyone else hitting these messages?
Thanks in advance.
Ian
Can you help answer these questions from other members on NexusFi?
The issue was just limited to the VPS I was on. So there is no widespread issue with NT / The data feed, etc.
Thanks,
Ian
In the analytical world there is no such thing as art, there is only the science you know and the science you don't know. Characterizing the science you don't know as "art" is a fools game.
I had a number of Ninjatrader brokerage / CQG connection dropping issues the last week or so, not sure if I had problems the exact same day/time you mentioned though. If this continues I'm going to have to change to a broker with a more reliable data feed because it cost my automated strategies about $2k is missed profit opportunities.
@iantg problem was on April 23th and it was something else, the problem was clearly identified on our side (a flapping network port) and solved. I didn't notice any Continuum disconnection since.
If you can you should do a tracert to the Continuum destination server to see if it can be a router between you and the destination. But this kind of failure are tricky to analyze as they usually don't last long.
When I saw this in the past it was looking like a Continuum server (or its network) congested, not a pure network problem, but as I don't have access to the remote server logs I really don't know.
Thanks Sam, I believe in my case this was just isolated to the events you described below. Everything looks fine for me at this point.
In the analytical world there is no such thing as art, there is only the science you know and the science you don't know. Characterizing the science you don't know as "art" is a fools game.
