Unable to Disable Read-Only Mode

[jp409]

Hi!

I believe I have everything configured to disable the Read Only API mode on my live connection however, it is still not working. I always receive this error:

Error -1 321 Error validating request.-'b_' : cause - The API interface is currently in Read-Only mode.

Here is my log from the IB-gateway:

2025-05-11T20:28:20.519-04:00 | remove Client 1928
  | 2025-05-11T20:28:24.718-04:00 | 2025-05-11 19:28:24:718 IBC: detected dialog entitled: Login Messages; event=Lost focus
  | 2025-05-11T20:28:24.719-04:00 | 2025-05-11 19:28:24:719 IBC: detected dialog entitled: Login Messages; event=Deactivated
  | 2025-05-11T20:28:24.719-04:00 | 2025-05-11 19:28:24:719 IBC: detected dialog entitled: API client needs write access action confirmation; event=Activated
  | 2025-05-11T20:28:24.724-04:00 | 2025-05-11 19:28:24:723 IBC: detected dialog entitled: API client needs write access action confirmation; event=Focused
  | 2025-05-11T20:28:24.728-04:00 | 2025-05-11 19:28:24:728 IBC: detected dialog entitled: API client needs write access action confirmation; event=Opened
  | 2025-05-11T20:28:24.729-04:00 | 2025-05-11 19:28:24:728 IBC: detected dialog entitled: API client needs write access action confirmation; event=Lost focus
  | 2025-05-11T20:28:24.729-04:00 | 2025-05-11 19:28:24:729 IBC: detected dialog entitled: API client needs write access action confirmation; event=Deactivated

I have the ReadOnlyAPI set to no, and the AcceptIncomingConnectionAction set to accept:

2025-05-11T20:23:46.516-04:00 | AcceptIncomingConnectionAction=accept
  | 2025-05-11T20:24:55.020-04:00 | AcceptIncomingConnectionAction=accept
2025-05-11T20:25:25.587-04:00 | 2025-05-11 19:25:25:587 IBC: Setting ReadOnlyApi
  | 2025-05-11T20:25:25.792-04:00 | 2025-05-11 19:25:25:791 IBC: Read-Only API checkbox is now set to: false

I am using the latest image: 10.36.1c. I'm not sure if I'm missing anything here, but I would really appreciate any help!! Thank you!

[jp409]

FYI, I switched to the stable version (10.30.1v) and I am able to connect to live now!

Closing this issue, thanks!

[jp409]

Hi! Unfortunately, I was incorrect here. I am still having issues, but here is a little more information. The issue seems to be using both as trading_mode.

TRADING_MODE is set to 'live': connecting to the live port (4003) works and does not result in a Read Only connection.

TRADING_MODE is set to 'both': connecting to the live port (4003) does NOT work and results in a Read Only connection. My goal is to connect with a paper account on port 4004 and a live account on port 4003. It does not matter which connection is made first.

I am still using the stable version: 10.30.1v

Again, I have the following settings in my environment vars:
TWS_ACCEPT_INCOMING: accept
READ_ONLY_API: no

The ib-gateway log looks like this as soon as I connect with the live account on port 4003. I am ensuring to change the ClientID on each connection, based on connection time.

2025-05-11T20:28:20.519-04:00 | remove Client 1928
  | 2025-05-11T20:28:24.718-04:00 | 2025-05-11 19:28:24:718 IBC: detected dialog entitled: Login Messages; event=Lost focus
  | 2025-05-11T20:28:24.719-04:00 | 2025-05-11 19:28:24:719 IBC: detected dialog entitled: Login Messages; event=Deactivated
  | 2025-05-11T20:28:24.719-04:00 | 2025-05-11 19:28:24:719 IBC: detected dialog entitled: API client needs write access action confirmation; event=Activated
  | 2025-05-11T20:28:24.724-04:00 | 2025-05-11 19:28:24:723 IBC: detected dialog entitled: API client needs write access action confirmation; event=Focused
  | 2025-05-11T20:28:24.728-04:00 | 2025-05-11 19:28:24:728 IBC: detected dialog entitled: API client needs write access action confirmation; event=Opened
  | 2025-05-11T20:28:24.729-04:00 | 2025-05-11 19:28:24:728 IBC: detected dialog entitled: API client needs write access action confirmation; event=Lost focus
  | 2025-05-11T20:28:24.729-04:00 | 2025-05-11 19:28:24:729 IBC: detected dialog entitled: API client needs write access action confirmation; event=Deactivated

I would really appreciate any help, and please let me know if I should include any more information I haven't already.

[gnzsnz]

please follow the steps on #245 , make sure you are using the sample docker-compose.yml as it's tested and works.

I can't help much with the information provided. please send the information required in #245

[jp409]

Thanks for the response @gnzsnz !

I was able to replicate this locally by leaving the Read-Only API checkbox checked and running my program normally. This box popped up, and I am seeing an identical error I am seeing on AWS (I am running the image in an AWS ECS task container and I'm connecting to it with my program, which is running in a separate container in the same task. I'm connecting with localhost:4003).

Is the correct setting to have the Docker image close this box READ_ONLY_API = no ? I definitely have that set and I can see in the logs:

2025-05-20T01:15:37.067Z | ReadOnlyApi=no | ecs/ib_gateway/bbe4fa7ed6014bacb05d1d475d4998d3
  | 2025-05-20T01:15:37.067Z | ReadOnlyLogin=no | ecs/ib_gateway/bbe4fa7ed6014bacb05d1d475d4998d3
  | 2025-05-20T01:15:56.867Z | 2025-05-19 20:15:56:867 IBC: Setting ReadOnlyApi | ecs/ib_gateway/bbe4fa7ed6014bacb05d1d475d4998d3
  | 2025-05-20T01:15:57.238Z | 2025-05-19 20:15:57:238 IBC: Read-Only API checkbox is now set to: false

Sorry if I'm missing something here, but it seems the setting ReadOnlyAPI somehow reverts back to yes, even though I mark it as no. Please let me know if there's anything I can do!