[BUG]: CORS /graphql letsencrypt about lago HOT 4 OPEN

Hello @unusualevent

Sorry for the delay here.
Well, our documentation about serving SSL with the basic configuration is a bit old and we do not maintain it... That's a shame.
We'll work on a new one, serving everything with Traefik.

Do you use a single domain to run Lago?

from lago.

@jdenquin I was trying to serve all of Lago from the same domain, yes. I think I was thinking about proxying through Caddy, if possible I'd like it if they all went through the same port so that CORS worked.

from lago.

I know that some other apps have like their own internal nginx router container, as another example. that way you can pick and choose your outside ssl termination.

443:443 (caddy/traefik/nginx/whatever) -> router_container:80 (not occupying that port on the host) -> route to the two containers

or at least the demo itself should route everything through the same domain and port, or should have the correct CORS headers.

the lack of a good way to run it securely made me not want to use Lago because the self hosting would be far too much trouble (and that's saying something, I'm willing to put up with a lot of trouble self hosting things). the pricing was also astronomical if I wanted you to handle it for me.

from lago.

I understand your bad experience @unusualevent , feel free to join the Slack Community and ask for any help around it.
Using the same domain actually is not something we recommend, it's better to use subdomains for both services (front and api)

from lago.