MatAmoM
Convex Community2w ago
2 replies
MatAmo

Dev deployment CONVEX_SITE_URL locked to custom domain (override disabled) - how to use native .com

Advice
Scope
I can’t change
CONVEX_SITE_URL
on my dev deployment (UI control is disabled), and it appears stuck on my custom domain (
https://my-domain.com
). I want localhost-first dev auth without using that domain.

Stack / versions
- Language: TypeScript
- Frontend: Nuxt
^4.3.1

- Convex:
^1.31.7
(
npx convex --version
=>
1.31.7
)
-
@convex-dev/better-auth
:
^0.10.10

-
better-auth
:
^1.4.18

- Node:
v22.15.0

- pnpm:
10.10.0


What I’m seeing
In Deployment Settings -> Custom Domains / Override Environment Variables:
-
process.env.CONVEX_SITE_URL
shows
https://my-domain.com (default)

- the combobox is disabled, so I can’t switch back to native
.convex.site
for dev

Repro steps
1. Have custom domains configured for production (
api.my-domain.com
/
site.my-domain.com
).
2. Open dev deployment settings.
3. Try to change
CONVEX_SITE_URL
override in dashboard.
4. Control is disabled; value stays
https://my-domain.com
.

Impact
- Local dev on
http://localhost:3000
can hit auth CORS/issuer issues if dev points at the custom domain.
- I can work around routing, but the deployment-level URL still leaks into auth issuer/JWT claims.

Question
Is this expected behavior (dev
CONVEX_SITE_URL
being locked when prod custom domains exist)?
If yes, what’s the recommended way to keep prod custom domains but run dev with native Convex URLs (
*.convex.cloud
/
*.convex.site
)?
Pasted_image_20260217100919.png
Was this page helpful?