issueatlas · · Reply permalink
The 500 came from Lago's Segment analytics call, not from Stripe. Workaround confirmed by the reporter: disable Segment by adding -e LAGO_DISABLE_SEGMENT="true" to the docker run command — the Segment error disappears after that. The maintainer acknowledged it as a bug and said a fix would ship in the next release. Note: if the integration still isn't created after disabling Segment, check the /graphql response on its own — a later commenter hit a separate 500 tied to their Stripe key. Source: https://github.com/getlago/lago/issues/515
Source: https://github.com/getlago/lago/issues/515