Spioune Comments - Convex Community

Spioune

CCConvex Community

•Created by Spioune on 2/20/2025 in #self-hosted

http actions via traefik

Yes. I changed CONVEX_SITE_ORIGIN and restarted the backend, the authentication page still shows the old CONVEX_SITE_ORIGIN value. I had to run npx convex dev and edit auth.config.ts from process.env.CONVEX_SITE_URL to 'https://example.com' to process.env.CONVEX_SITE_URL again to get the new value

51 replies

CCConvex Community

•Created by Spioune on 2/20/2025 in #self-hosted

http actions via traefik

thanks again for your help

51 replies

CCConvex Community

•Created by Spioune on 2/20/2025 in #self-hosted

http actions via traefik

time to sleep

51 replies

CCConvex Community

•Created by Spioune on 2/20/2025 in #self-hosted

http actions via traefik

amazing

51 replies

CCConvex Community

•Created by Spioune on 2/20/2025 in #self-hosted

http actions via traefik

so the only "bug" is convex backend proxy to 3211

51 replies

CCConvex Community

•Created by Spioune on 2/20/2025 in #self-hosted

http actions via traefik

So now everything is working correctly (without using convex port 3211)

51 replies

CCConvex Community

•Created by Spioune on 2/20/2025 in #self-hosted

http actions via traefik

hmm i deleted auth.config.ts and create it and now its back to https://convexpublic.mydomain.dev

51 replies

CCConvex Community

•Created by Spioune on 2/20/2025 in #self-hosted

http actions via traefik

but still, it is equals to the cloud url (since CONVEX_SELF_HOSTED_URL should point to the cloud url) instead of the site url which is wrong

51 replies

CCConvex Community

•Created by Spioune on 2/20/2025 in #self-hosted

http actions via traefik

nevermind, CONVEX_SITE_URL in the auth.config.ts has nothing to do with the server config. It comes from the CONVEX_SELF_HOSTED_URL in .env.local in the convex application

51 replies

CCConvex Community

•Created by Spioune on 2/20/2025 in #self-hosted

http actions via traefik

so I set them back to https url

51 replies

CCConvex Community

•Created by Spioune on 2/20/2025 in #self-hosted

http actions via traefik

so it should definetely not be the localhost

51 replies

CCConvex Community

•Created by Spioune on 2/20/2025 in #self-hosted

http actions via traefik

and also for the JWT issuer

51 replies

CCConvex Community

•Created by Spioune on 2/20/2025 in #self-hosted

http actions via traefik

but on Convex Cloud it is equal to the .convex.site url

51 replies

CCConvex Community

•Created by Spioune on 2/20/2025 in #self-hosted

http actions via traefik

it is equal to CONVEX_CLOUD_ORIGIN

51 replies

CCConvex Community

•Created by Spioune on 2/20/2025 in #self-hosted

http actions via traefik

it is not

51 replies

CCConvex Community

•Created by Spioune on 2/20/2025 in #self-hosted

http actions via traefik

I manage to setup traefik proxy to prefix with /http which is much cleaner. One thing I don't understand though, where does CONVEX_SITE_URL comes from inside auth.config.ts?

export default {
  providers: [
    {
      domain: process.env.CONVEX_SITE_URL,
      applicationID: "convex",
    },
  ],
};

export default {
  providers: [
    {
      domain: process.env.CONVEX_SITE_URL,
      applicationID: "convex",
    },
  ],
};

It is equal to https://convexbackend.mydomain.dev. Shouldn't it be convexpublic.mydomain.dev (the http actions url) ?

51 replies

CCConvex Community

•Created by Spioune on 2/20/2025 in #self-hosted

http actions via traefik

This means the request goes out of the local network to the public internet and back in ? Despite the fact that this is all on the same server

51 replies

CCConvex Community

•Created by Spioune on 2/20/2025 in #self-hosted

http actions via traefik

What if I set CONVEX_CLOUD_ORIGIN and CONVEX_SITE_ORIGIN to be localhost? Are they used for anything else?

51 replies

CCConvex Community

•Created by Spioune on 2/20/2025 in #self-hosted

http actions via traefik

Thanks for your help !

51 replies