Configure trusted domains

Add your application domains to Managed Better Auth's allowlist to enable OAuth and email verification redirects in production.

Why domains are required

Managed Better Auth only redirects to domains in your allowlist. This prevents phishing attacks and unauthorized redirects by ensuring users are only sent to your legitimate application URLs.

Without adding your production domain, OAuth sign-in and verification links will fail when users try to access your application.

Add a domain

1. Go to Console → Auth → Configuration → Domains
2. Enter your domain with protocol: https://myapp.com
3. Click Add domain

Repeat for each domain where your app runs.

Localhost is pre-configured

Development domains are automatically allowed, so you don't need to add them:

• http://localhost:3000
• http://localhost:5173
• Any localhost port

Production domains

Add all domains where users access your application:

• https://myapp.com
• https://www.myapp.com (if you support www subdomain)
• https://app.myapp.com (if using a subdomain)

Wildcard domains for previews

For preview environments with dynamic hostnames (for example Vercel preview deployments), you can add a wildcard trusted domain such as https://*.my-app-preview.vercel.app. One entry can match every preview under that pattern instead of adding hosts one by one.

Use the same rules as fixed domains: include https:// (or http:// where appropriate) and omit trailing slashes after the pattern.

Common issues

Redirect blocked after OAuth sign-in:

• Verify the domain is in your allowlist
• Ensure you included https:// (not http:// for production)
• Check spelling matches exactly (including www vs non-www)

Verification link doesn't redirect:

• Verification links use the same domain allowlist
• Add the domain where users should land after clicking the verification link

Next steps

• Production checklist - Complete setup for launch