-
Hi, Firstly I will say that I am not overly confident with networking, this is most likely to be something I'm doing wrong rather than an actual bug. However I would really appreciate some guidance please. So I am interested in running just the ib-gateway in Azure for my services to communicate with. I tried creating an Azure ACI using the image I have previously had the IBKR gateway running on my local machine by manually downloading a java runtime and running the I run the following on my machine to create the container. These are the full logs of the container once it has finished booting after a couple seconds
I have tried endless combinations of ports when calling localhost and/or 0.0.0.0 from my machine to connect to the API, and I have done the same when exec-ing into the container. An example of an attempt to curl the API from the container is below, which seems to just hang?
I can see that port 4004 on the container is listed as a listener.
I can also see that socat is redirecting 4002 to 4004 as per your docs.
Please let me know what I am doing wrong! As I say I'm 99% sure its something that I'm doing that is the issue! Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Moving this to the discussion section, as this is not an issue/bug. i'm not sure what's your problem, you are showing with you are in good shape to use TWS API or ib_async. this is not a REST API so curl won't work, and based on your comment it doesn't. Please don't put this on Azure with an open API port. the API does not provide ANY security, so everybody and their mother in internet would be able to connect and start trading with your account. There are many options to connect on Azure, the README explore a few. I would suggest that you pass an ssh key so ib-gateway can connect to your SSH server. This is a "safe" way, but with a steep learning curve. |
Beta Was this translation helpful? Give feedback.
Thanks for the information.
My apologies for thinking this was a REST API, I have been using the IB Gateway (Client Portal API) on my localhost using REST type requests and this worked. I'm confused, I thought this was a containerised version of that.