Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Running multiple companion instances

See original GitHub issue

Hi Team,

Is it possible to run multiple instances of companion app that are related? We have companion deployed with our server which is highly available. When instance count > 1 provider oauth flow fails with companion: 2019-09-23T08:49:42.840Z [error] grant.oauth.error grant.js responded with error: error=Grant%3A%20missing%20session%20or%20misconfigured%20provider

Earlier I was getting a different error that was resolved after I added transport: 'session' to my custom providers.

From looking at the code extensively, I believe the redis integration only provides for storing update progress and not the session storage itself. Is it possible today to have companion running in high availability with shared session storage?

Issue Analytics

State:
Created 4 years ago
Comments:7 (1 by maintainers)

Top GitHub Comments

2reactions

ifedapoolarewajucommented, Oct 12, 2019

@serverdevil when a companion instance receives the first request, it will redirect to the master domain for the oauth dance to be handled. After the Oauth dance is done, further requests are passed back to the instance that received the first request.

so long as you are setting the sendSelfEndpoint option per companion instance to it’s actual URL i.e https://instance1.server.com, and it is directly accessible via this URL, then companion will try to achieve this sticky session behaviour by itself.

1reaction

arturicommented, Sep 23, 2019

@ifedapoolarewaju could you help here please?