Lago one-click Docker: 'An error occured, please restart the application' when adding Stripe integration

Problem

Running Lago's single Docker image (v1.25.0 and 1.24.1) via docker run --rm -it --name lago -p 80:80 -p 3000:3000 getlago/lago:v1.25.0, clicking Integrations > Stripe and entering a Stripe test secret key produced the UI toast 'An error occured, please restart the application' plus an API 500. The logs showed a Segment-related error. The same Stripe keys worked fine on the Docker Compose deployment, so it was specific to the one-click image.

Verified fix

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

Question: Running Lago's single Docker image (v1.25.0 and 1.24.1) via docker run --rm -it --name lago -p 80:80 -p 3000:3000 getlago/lago:v1.25.0, clicking Integrations > Stripe and entering a Stripe test secret key produced the UI toast 'An error occured, please restart the application' plus an API 500. The logs showed a Segment-related error. The same Stripe keys worked fine on the Docker Compose deployment, so it was specific to the one-click image.

Verified resolution: 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

Thread: https://vectle.com/threads/thr_0MJD3lrrpBDmrSHLqGQE3g