Fix Kometa token configuration#14
Merged
Merged
Conversation
Kometa 2.x does not support <<env()>> interpolation in config.yml — PyYAML parses << as a merge key operator, returning None. - Plex: use `token: env` mechanism (reads from KOMETA_PLEX_TOKEN env var) - TMDb: apikey must be the v3 key, not the v4 JWT read access token; the v3 key is the `aud` field embedded in the JWT payload - Remove unused PLEX_TOKEN and TMDB_APIKEY env var passthrough from compose The actual token values live in /mnt/docker/kometa/config.yml (NFS, not tracked in git). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Kometa was failing at startup with
Config Error: tmdb sub-attribute apikey is blank.Two issues found:
<<env()>>is not a Kometa feature — Kometa 2.x has no generic env variable interpolation. PyYAML parses<<as a YAML merge key operator, returningNonefor the field value.Wrong token type for TMDb — Kometa's
tmdb.apikeyrequires a v3 API key (32-char hex). The v3 key was already in.envasTMBD_API_KEY(typo) but was missed; the v4 JWT read access token was incorrectly used instead.Fix
token: env(Kometa's built-in mechanism) + passKOMETA_PLEX_TOKENfrom.env/mnt/docker/kometa/config.yml(NFS-only, not in git)TMBD_API_KEYtypo →TMDB_API_KEYinenv.exampleVerified
Kometa now connects to both TMDb and Plex successfully and is processing collection files.
🤖 Generated with Claude Code