IB TWS security token asked after disconnection

For IB, one quick thing about the <b>Gateway</b>.

The latest version available seems to have the "Settings" feature broken.The menu would not open when clicking on "Settings" menu item (I have verified this with several users.)

Please, at your convenience repair it, as it is very inconvenient not being able to change the port number (and so on). Thank you.
 
fullautotrading said:
For IB, one quick thing about the <b>Gateway</b>.

The latest version available seems to have the "Settings" feature broken.The menu would not open when clicking on "Settings" menu item (I have verified this with several users.)

Please, at your convenience repair it, as it is very inconvenient not being able to change the port number (and so on). Thank you.
More...

Thank you for the report; this was corrected a while back, but fix did not make it into 943 standalone build, it is there now.
 
Hello fullautotrading,

years after you suggested it to me, I have started using IB Gateway, which has the advantage that it can run unattended for a week (or longer, but I need a week) and doesn't have the auto-logoff feature.

Everything works fine, with the "IB API login" version, but I have a question nonetheless: why am I getting the API Client status as constantly "disconnected"? It is listed as "disconnected" although it works perfectly fine, as the API even receives and executes orders.

See picture below.
 
travis said:
Hello fullautotrading,

years after you suggested it to me, I have started using IB Gateway, which has the advantage that it can run unattended for a week (or longer, but I need a week) and doesn't have the auto-logoff feature.

Everything works fine, with the "IB API login" version, but I have a question nonetheless: why am I getting the API Client status as constantly "disconnected"? It is listed as "disconnected" although it works perfectly fine, as the API even receives and executes orders.

See picture below.
More...

This does not look right; I will PM you.
 
travis said:
Hello fullautotrading,

years after you suggested it to me, I have started using IB Gateway, which has the advantage that it can run unattended for a week (or longer, but I need a week) and doesn't have the auto-logoff feature.

Everything works fine, with the "IB API login" version, but I have a question nonetheless: why am I getting the API Client status as constantly "disconnected"? It is listed as "disconnected" although it works perfectly fine, as the API even receives and executes orders.

See picture below.
More...

Well if it says the client is disconnected, I don't see reasons to doubt that the client is disconnected (I did not notice any problem with the Gateway about that).

>it works perfectly fine, as the API even receives and executes orders.

Probably it just depends on the "client" you are using. The first idea that comes to my mind is that what you are using to place the orders (what is that?), connects to do so, and then perhaps it disconnects when done. Is it ever possible ?
 
To answer your question and dst's private question ("do you see this right away or after some activity?"), here's some more information.

I am using the application with a DDE exchange to excel, and the orders get sent fine, as I said.

I see it all the time, as I've never seen it connected. Yet the orders go through fine. So, everything works fine.

My conclusion is that maybe it is so fast, that I either don't see it connected, or the IB gateway application doesn't even have enough time to record the connection while the order is sent and keeps telling me it's disconnected, whereas for the split second while the order is sent, it is indeed connected.

Another problem, much bigger, that I found this morning, as I woke up, is that I am getting again the infamous screen for which I've started this thread and which I haven't gotten on TWS for years but I am now getting on IB Gateway: the security token is being asked and there were 33 attempts, so in other words it had been logged off for several hours.

I have no idea why this is happening, given that fullautotrading hasn't gotten this message either, for years, since we posted it on this thread.

I am inclined now to go back to TWS and maybe not use the charts in the hope of being able to use it without problems for an entire week.
 
travis said:
To answer your question and dst's private question ("do you see this right away or after some activity?"), here's some more information.

I am using the application with a DDE exchange to excel, and the orders get sent fine, as I said.

I see it all the time, as I've never seen it connected. Yet the orders go through fine. So, everything works fine.

My conclusion is that maybe it is so fast, that I either don't see it connected, or the IB gateway application doesn't even have enough time to record the connection while the order is sent and keeps telling me it's disconnected, whereas for the split second while the order is sent, it is indeed connected.

Another problem, much bigger, that I found this morning, as I woke up, is that I am getting again the infamous screen for which I've started this thread and which I haven't gotten on TWS for years but I am now getting on IB Gateway: the security token is being asked and there were 33 attempts, so in other words it had been logged off for several hours.

I have no idea why this is happening, given that fullautotrading hasn't gotten this message either, for years, since we posted it on this thread.

I am inclined now to go back to TWS and maybe not use the charts in the hope of being able to use it without problems for an entire week.
More...

<b>> My conclusion is that maybe it is so fast, that I either don't see it connected, or the IB gateway application doesn't even have enough time to record the connection</b>

Sure, if you are sending a few orders, it's quite possible that everything is so tight that the interface does not even get (visibly) refreshed [cf. for instance, <a href="http://www.scs.ryerson.ca/mes/courses/cps530/programs/threads/Repaint/index.html" target="_blank"> here</a> (or similar topics)]. If you control the code, you might "separate", for debugging, the connection/disconnection part and the order sending part, so you can take a look if this is the case.

<b>>Another problem...given that fullautotrading hasn't gotten this message either, for years, since we posted it on this thread.</b>

That's right, since the last time I posted about the "infamous" :-) credential prompt, I have not seen it anymore (I am connected all the time). So, all is fine, so far.
[What I suggested is to no allow even the "physical" occurrence of that, preventing it altogether on the client side. But since you got it, it has to be concluded, that this has not been done that way.]
 
Yes, this all makes sense and thanks for the useful information.

So, recapitulating, thanks to both of you for your help, and now I might either use TWS, if it doesn't cause me any problems by running for a week, or I might disable the Security Token feature, like I've done in the past, and use IB Gateway. Before reverting to TWS, for a bit longer, I'll keep testing IB Gateway with the Security Token enabled.
 
Good news regarding my IB Gateway.

After talking to dst, I realized I hadn't been using the latest IB TWS (and IB Gateway) version. I had 936 here and 932 on my server, whereas the latest version was 944.3. How stupid of me to come here and complain without making sure I had the latest version. Sorry.

On the other hand, it wasn't completely my fault, because even today the little application to "check for TWS Updates" told me that I have the latest version. So I went to IB's website and downloaded from there, installed it over the old version (it doesn't delete the settings). From now I won't trust that little application checking for updates and, if I have any problems, I'll go to the website first, and see if I am running the latest version.

As you can see from the picture attached below, this update completely solved that first problem I had mentioned: that API Client showed as "disconnected" (although it worked perfectly):

View attachment 144924

Now we'll see if it also solves the Security token request after the hour they reboot their servers, request that obviously made my automated trading impossible and which was the reason I started this thread a long time ago.

I'll come back on Friday night to let you know if in the next two days I'll have had no extra security token requests, after entering it today.
 
You must log in or register to reply here.
Back
Top