Immutable solution version
Sign-in loop on the satellite domain: the session never syncs from the primary domain
Complete solution
The user signs in, lands back on the satellite domain, and is still signed out. The loop repeats forever. Not the full reference manual.
TL;DR: The user signs in, lands back on the satellite domain, and is still signed out. The loop repeats forever. Symptom On a satellite domain, signing in redirects to the primary domain and back, but the satellite never picks up the session. Confirm the cause 1.
The fix
- Sign-in and sign-up MUST be hosted on the primary domain. If the satellite has its own sign-in pages, the flow is misconfigured.
- After returning from the primary domain, the satellite needs the sync trigger. With satelliteAutoSync false (the default), your satellite's sign-in links must use the SDK's buildSignInUrl() and buildSignUpUrl() methods, which append the sync parameter automatically. Hardcoded sign-in URLs skip the sync and cause this loop.
- Check the satellite domain is registered in the dashboard under Domains > Satellites.
- Replace hardcoded sign-in/sign-up links on the satellite with buildSignInUrl() and buildSignUpUrl().
- If you prefer automatic sync, setting satelliteAutoSync to true redirects every first visit to the primary domain; it costs one redirect per new visitor.
When to use this
- This covers exactly what the title says: Sign-in loop on the satellite domain.
- You are setting this up for the first time, or auditing an existing setup.
- You want the key gotchas in one place before you start.
When not to use this
- You are doing a different workflow with Sign-in; these steps are specific to the title above.
- You need the full reference docs; this is the short path, not the manual.
Compatibility
- Not pinned to a specific version; follows current Sign-in behavior.
Evidence
Verified against Clerk satellite-domain docs 2026-09-26: sign-in flows run on the primary domain; with satelliteAutoSync false the satellite must use buildSignInUrl()/buildSignUpUrl() so the sync trigger parameter is appended; satelliteAutoSync true auto-redirects first visits to the primary at a performance cost; sign-out syncs across domains.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_qW-IzkQ-sXGLi1UU_JxE1A" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Sign-in loop on the satellite domain: the session never syncs from the primary domain <span>— Vectle</span></a>