Loading...
Loading...
Solutions to the most common problems you might encounter when developing with Stackseed.
You see EADDRINUSE when starting the dev server. Another process is already using port 3000, 3002, or 3003.
Kill the process occupying the port or start the dev server on a different port.
lsof -ti :3000 | xargs kill -9
# Or use a different port
PORT=3001 bun devThe app fails to connect to Supabase. You see connection refused or timeout errors.
Verify DATABASE_URL in .env.local is correct. Check that your Supabase project is running and the connection string matches. If using a pooler, ensure the port and mode are right.
# Verify your connection string
echo $DATABASE_URL
# Test connection
bunx supabase status
# Check if .env.local exists
ls -la .env.localAfter signing in with Google or another provider, you get redirected to the wrong URL or see a redirect_uri_mismatch error.
Make sure BETTER_AUTH_URL matches your app URL exactly (including http/https). Update the redirect URIs in your OAuth provider's dashboard to match. In development, use http://localhost:3000.
Welcome emails, password resets, or invite emails are not being delivered.
Set RESEND_API_KEY in .env.local. Without it, emails are silently skipped. Verify your sending domain is verified in the Resend dashboard. Check the Resend logs for delivery failures.
Background jobs are queued but never execute. The Trigger.dev dashboard shows no activity.
Make sure the Trigger.dev dev server is running with npx trigger.dev@latest dev. Verify TRIGGER_SECRET_KEY is set in .env.local. Check the Trigger.dev dashboard for error logs.
# Check Trigger.dev is running
npx trigger.dev@latest dev
# Verify your secret key
echo $TRIGGER_SECRET_KEYTypeScript errors or module not found after adding a new workspace package dependency.
Run bun install to update the workspace links. Clear the Turborepo cache with rm -rf .turbo and rebuild. Make sure the package is listed in the app's package.json dependencies.
# Clean install
rm -rf node_modules .turbo
bun install
# Rebuild
bun run buildYou see 'Missing message' warnings in the console or untranslated keys showing up in the UI.
Add the missing key to both messages/en/app.json and messages/de/app.json. Translation keys must exist in all locale files. Restart the dev server after adding new keys.
If none of the above solved your issue, check the help center for detailed FAQ answers or open a GitHub issue.