Develop OAuth callbacks

Keep a stable HTTPS callback hostname while developing auth flows.

OAuth providers and many third-party integrations require a fixed HTTPS redirect URL. Turbotunnel can hold that hostname while your local app restarts.

Configure a stable callback host

Save a project tunnel in turbotunnel.json:

{
  "port": 3000,
  "slug": "auth-dev",
  "access": { "type": "public" }
}

Start the tunnel and app:

tt dev -- pnpm dev

https://auth-dev-turbotunnel.vercel.app/api/auth/callback

Use an exact custom domain when the provider already allows one hostname:

{
  "port": 3000,
  "domain": "auth-dev.example.com",
  "access": { "type": "public" }
}

Keep the redirect path public

Providers usually need a public callback path. Password or IP access can block the provider redirect.

Keep the tunnel running while you restart the app. Forwarding resumes when the app returns.

Prefer a saved slug or domain so callback configuration does not change every session. If a managed vercel.app hostname is unavailable, Turbotunnel assigns a generated fallback. Confirm the printed public URL after the first connect.

Develop OAuth callbacks

Configure a stable callback host

Keep the redirect path public

Related docs