Pain point · Self-hosting & upgrades · Causes churn
Helm install fails with CORS errors, signup cannot complete
10 source threads · first seen 2022-08 · last seen 2026-01
Summary
A basic Helm install on Kubernetes could not be made to work because the frontend hits CORS failures against the GraphQL endpoint, regardless of how apiUrl and frontUrl were set.
- Affects
- team deploying on Kubernetes
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“The API endpoint POST /graphql is not reachable when accessed via the configured external IP, even though the container is running correctly”
“can't even signup because of incorrect api url”
“We are trying to make basic Lago install through Helm working but we're just unable to because of CORS problems”
“The graphql API is served over 3000 instead of proxied via the front/nginx container, various shenanigans ensue”
“For whatever reason the following env vars are not being read anymore:”
“Frontend loads but API doesn't start because Postgres doesn't start”
“It's just this invoice file redirection thing that fails”
“i also tried configure nginx to add Access-Control-Allow-Origin header”
“I expected no CORS error to happen because my URLs are defined in the ENV variables”
“The customer gets added but the error is their and when I view the created customers I get the same error”