Improve DX: warn or block invite emails when Site URL is not configured #41907
Unanswered
iddi5504
asked this question in
Feature Requests
Replies: 2 comments
📝 CodeRabbit Plan ModeGenerate an implementation plan and prompts that you can use with your favorite coding agent.
🔗 Similar IssuesPossible Duplicates
Related Issues
👤 Suggested Assignees🧪 Issue enrichment is currently in open beta.You can configure auto-planning by selecting labels in the issue_enrichment configuration. To disable automatic issue enrichment, add the following to your issue_enrichment:
auto_enrich:
enabled: false💬 Have feedback or questions? Drop into our discord! |
0 replies
|
When i try the same thing with my Supabase account and when i tried to invite other member to my project as a developer role and it worked it just send the email to other person and he also joined my project without any kind of issue.. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Describe the issue
Invite confirmation emails fall back to localhost when Site URL is not configured .
Invite confirmation emails sent from Supabase Studio can contain broken magic links that use http://localhost:3000 as the base URL.
This happens when the project Site URL is not configured in Authentication settings. Supabase Auth silently falls back to localhost, resulting in unusable invite links for end users.
Related to #41321.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
Actual behavior
The confirmation email contains a link similar to:
http://localhost:3000/#access_token=...&type=signup
This link is not reachable for the invited user and results in a failed connection.
Expected behavior
One of the following would improve the experience:
Screenshots
If applicable, add screenshots to help explain your problem.
System information
Additional context
Related to #41321
Invite confirmation emails use the magic link flow and rely on Auth configuration.
From the email template:
All reactions