Support

Direct help for common BaseBuddy setup, access, mapping, editing, and deployment tasks.

Support/How to fix BaseBuddy sign-in return issues

How to fix BaseBuddy sign-in return issues

Troubleshoot local password sign-in, invite return paths, stale callback links, and production app-data storage.

Use this when sign-in starts, but the browser returns to the wrong place or lands back on login with an error.

Current BaseBuddy installs use local password sessions stored in app data.

Match the symptom

SymptomWhat to check first
Password sign-in failsUser exists in app data and password is correct
Sign-in works locally but fails in productionProduction can read and write the same app data
Invite sign-in opens ProjectsInvite is fresh, recipient used the invited email, and the internal return path was preserved
Browser opens /login?error=auth_callback_errorAn old OAuth callback URL was opened
Browser opens /login?error=email_confirm_errorAn old email confirmation URL was opened

Confirm local auth is ready

Run:

shpnpm basebuddy doctor --skip-db-check

The App data, Owner account, and Environment values sections should be ready.

If the user is missing, create one:

shpnpm basebuddy user:create \
  --email "editor@example.com" \
  --name "Editor" \
  --password "choose-a-strong-password"

Confirm the return path is internal

BaseBuddy accepts internal paths after sign-in:

text/projects
/invite/<token>

External return URLs are rejected and BaseBuddy falls back to Projects.

For invite issues:

  1. Send a fresh invite.
  2. Ask the recipient to open it on the intended BaseBuddy domain.
  3. Ask them to sign in with the same email address used on the invite.
  4. Keep the invite and sign-in flow in the same browser.

Fix production-only failures

If login works locally but not in production, production may be missing live app data or using ephemeral storage. Confirm the deployment can read and write the selected app-data backend.

After moving or restoring app data, restart the app and rerun:

shpnpm basebuddy doctor

Retest

Use a private browser window:

  1. Open /login.
  2. Sign in with email and password.
  3. Confirm the browser opens /projects.
  4. Test one fresh invite if invite return paths were failing.

For setup diagnostics, use How to fix failed setup checks.