Custom domain?
Is it possible to use a custom domain with Convex (rather than XXXXX.convex.cloud)? ChatGPT is insisting that GPT Action Sets use the same domain as auth (and I'm able to use Clerk on a custom domain)
7 Replies
@Mike Lyons yeah, we really really want this too for headless stuff. it's on the backlog, but we don't have a plan to implement it in the next six weeks, unfortunately.
Likely have thought of this, but if it's a Next.js project you could proxy the request with an api endpoint
Ah, that's a reasonable stopgap.
Out of curiosity what would "adding custom domains" entail adding? I'm guessing some sort of SSL cert thing to get CNAMES working?
@gautamg might have some ideas. it'd be very similar to the vercel flow. point an
A record or whatever at our traffic IP or something and then we virtual host it and provision a cert for it?yeah, we need to provision certs for the custom domain (after proving ownership, usually via a TXT record or something) but more importantly our traffic layer has to be aware of the mapping from custom domain to customer backend, i.e. when we get a request directed to our load balancer for mikes-website.com, we need to know that this request is actually intended for some-backend.convex.cloud
any updates on custom domains?
yeah, we're actively working on it