Gateway Un-Authenticates and Throws this Failure Message: 'Force compete capability must be used together with compete flag'

Hi voyz, I just want to let you know that I REALLY appreciate the work you’ve done here. This has been such a time saver for me.

Everything was working perfectly until recently, when I started getting the bug below.

Describe the bug The gateway loses authentication with the failure message: ‘Force compete capability must be used together with compete flag’

To Reproduce The gateway has been working completely fine for me for the past few hours, and then it lost authentication.

Upon posting the /iserver/auth/status request, I receive this: {'authenticated': False, 'competing': False, 'connected': True, 'message': '', 'serverInfo': {'serverName': None, 'serverVersion': None}, 'fail': 'Force compete capability must be used together with compete flag'}

I’ve tried all of the recommended fixes such as changing the proxy, using the logout endpoint, using a combination of the logout endpoint and the reauthenticate endpoint, all of these to no avail.

No matter how many times I restart ibeam, this issue still persists and prevents successful authentication.

Is there some way to specify a ‘compete flag’ when sending a request to the API, or is there another workaround to this issue?

Environment IBeam version: latest (pulled today)

[JackD111]

Seems that they resolved this issue. IB gateway running again as normal.

[hschickdevs]

Hi @adamkornafeld, re-opening this because it seems that there are some modifications to be made here.

Is there something that we need to modify in iBeam to comply with this new compete flag rule?