Skip to content

fix: fresh Jellyfin 12 admin setup (v1.2.3) - #9

Merged
LavX merged 1 commit into
mainfrom
fix/v1.2.3-jellyfin-first-user
Oct 19, 2026
Merged

LavX merged 1 commit into
mainfrom
fix/v1.2.3-jellyfin-first-user

Conversation

@LavX

@LavX LavX commented Oct 19, 2026

Copy link
Copy Markdown
Owner

What

Fixes the fresh-install failure in v1.2.2: Jellyfin 12 creates the default first user (root) on GET /Startup/User, not on the POST. v1.2.2 skipped the POST when any user existed, leaving root without a password, so AuthenticateByName returned 401.

Now POST /Startup/User always runs. It renames the first user and sets the password, returns 204 on a fresh install, and 403 when a previous attempt already set a password. Both are handled.

How it was tested

  • Reproduced with the released v1.2.2 binary on a fresh stack: Jellyfin user was root with no password, AuthenticateByName 401.
  • Ran the fixed setupJellyfin against that exact broken state: succeeded, renamed the user to admin, set the password, created Movies/TV/Music libraries, and completed the wizard.
  • Unit tests cover the fresh 204 path and the 403 already-configured path.
  • bun test: 342 pass. Typecheck clean.

Checklist

  • bun test passes
  • tsc --noEmit passes
  • No em dashes added
  • No AI attribution
  • Docs updated (no user-facing flag change)
  • New code has tests

Jellyfin 12 creates the default first user (root) on GET /Startup/User
instead of POST. The previous skip-if-a-user-exists check therefore left
root without a password and AuthenticateByName returned 401. Always POST
Startup/User to rename the first user and set the password; tolerate 403
when a previous attempt already set one.

v1.2.3.
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-19T09:22:01.263751Z a5f4bfb PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@LavX
LavX merged commit 270dbea into main Oct 19, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant