Reproduction steps
- Set up a self-hosted instance with SSO (OIDC) enabled.
- Keep "Single community" mode disabled (multi-guild setup).
- Create an invite link for a guild (e.g. /invite/XYZ).
- As an unauthenticated visitor, navigate to https://fluxer.example.com/invite/XYZ.
- Click to log in / sign up via SSO (OIDC redirect flow).
- Complete authorization at the IdP and return to Fluxer.
Expected behaviour
Upon completing SSO, the user should automatically join the specific guild from the invite link they opened (/invite/XYZ).
Actual behaviour
The invite code from the URL is dropped during the SSO redirect flow. The backend only attempts to join the static FLUXER_AUTO_JOIN_INVITE_CODE from the .env.
If that env code is missing/stale, the user joins nothing (404 UNKNOWN_INVITE in logs) and lands on an empty dashboard, requiring a second click on the invite link. If multiple guilds exist, the user joins the wrong static guild instead of the one they were invited to.
Build information
Self-hosted Docker (Linux arm64)
API image: ghcr.io/fluxerapp/fluxer-api (digest: 57ab0af50711)
Frontend: ghcr.io/fluxerapp/fluxer-app-proxy-self-hosted (digest: 775dcc3bdc94)
Version: v1 / 2026.1026
Platform
Web, API, Self-hosting
Evidence
fluxer-api log showing maybeAutoJoinInvite strictly bound to the static env code during SSO callback:
{"level":"warn","service":"fluxer-api","inviteCode":"<STATIC_ENV_CODE>","msg":"Failed to auto-join invite","error":{"type":"UnknownInviteError","message":"UNKNOWN_INVITE","stack":"FluxerError: UNKNOWN_INVITE\n at InviteService.acceptInvite\n at async maybeAutoJoinInvite (chunk-SJ7ZDF6P.js:23255:7)\n at async _SsoService.resolveUserFromClaims (chunk-SJ7ZDF6P.js:28120:5)"}}