Bolt Clerk Production Domain Not Authorized
Quick Answer
The production domain has not been added correctly in Clerk, or the app is still using development keys or development-only URLs after deployment. Start with "Add the live domain in Clerk" before making broader code changes.
You're in the right place if...
- !Authentication works locally but not on the live domain
- !Clerk shows unauthorized or invalid host errors
- !The login page loads, but sign-in never completes on production
Why this happens
The production domain has not been added correctly in Clerk, or the app is still using development keys or development-only URLs after deployment.
Fix
Add the live domain in Clerk
Open your Clerk dashboard and add the exact production hostname, including www if you use it.
Switch the deployed app to the correct Clerk keys
Confirm the production environment uses the production Clerk publishable and secret keys, not development ones.
Regenerate the environment setup in Bolt
Use this prompt if the app still points to the wrong Clerk instance or URLs.
Copy this prompt
Clerk auth is failing on the production domain. Please audit the environment setup and auth config so the deployed app uses the correct production Clerk keys and authorized production domain.
Prevent this next time
Do the Clerk domain setup before launch day. Authentication domains should be part of your deployment checklist, not an afterthought.
Frequently Asked Questions
No. Development and production Clerk environments are separate, and using the wrong keys creates unreliable auth behavior.
Yes, if users can reach both. Add every production hostname the app may use.
Related fixes
Weekly Newsletter
Get next week's fix before you need it.
Join developers getting weekly vibe coding tips, error fixes, and tool updates.
Subscribe on Substack →