Plex Error when utilizing Config Secrets for the plex token #2197
Assignees
Labels
Comments
educatedCaveman
added
bug
|
appears to be more than just plex related |
suspected RCA ff80a8d |
|
@educatedCaveman can you confirm if you are seeing this on 2.0.2 or if you are running on develop/nightly? These may be unrelated issues compared to what has been found on the Discord |
|
@YozoraXCII, yes, I think I can. the logs I've generated reference v2.0.2, and in my |
|
@educatedCaveman can you confirm this is fixed on 2.1.0 |
|
I think I'm still having an issue, but I'll have to dig into it this weekend (been super busy). |
|
Couple things: 1: The docs show secrets in lowercase. They need to be uppercase in the config.yml Here is the relevant section from my config.yml: plex:
url: <<PLEX_URL>>
token: <<PLEX_TOKEN>>
timeout: 60
db_cache:
clean_bundles: false
empty_trash: false
optimize: false
verify_ssl:
tmdb:
apikey: <<TMDB_APIKEY>>
language: en
cache_expiration: 60
region:And here is the relevant output from the command line run: You can see that only the |
|
This just worked for me in 2.1.0 nightly and 2.1.0 master: config.yml: command line: log: run went on to connect to Plex and tmdb and completed without error. |
|
@chazlarson Looks like you're using the CLI directly. I'm using |
|
Env vars also working fine for me: then ran: #!/bin/zsh
echo kometa_plexurl in ENV: $kometa_plexurl
echo kometa_plextoken in ENV: $kometa_plextoken
echo kometa_tmdbkey in ENV: $kometa_tmdbkey
python kometa.py --run --config config/test-config.yml -dcWhich produced: |
|
I unset the Here's my compose: Full config: And I still get: As you can see it's still only picking up one of the variables. |
|
I stepped into the container and confirmed that my variables are set and correct. Didn't want to include that for obvious reasons. |
|
I'll see if I can repro it with docker, but so far I'm not seeing either the "must be lower case" or the "only one is read" |
|
The lowercase one is weird, but if I leave my |
|
I also cannot repro any issues in docker. |
plex:
url: <<plexurl>>
token: <<plextoken>>
tmdb:
apikey: <<tmdbkey>>services:
kometa-test:
image: kometateam/kometa:latest
container_name: kometa
restart: no
volumes:
- /home/chaz/kometa/config:/config
environment:
PUID: "1000"
PGID: "1000"
UMASK: "022"
TZ: "America/Chicago"
KOMETA_RUN: "true"
KOMETA_CONFIG: "/config/test-config.yml"
KOMETA_PLEXURL: "${kometa_plexurl}"
KOMETA_PLEXTOKEN: "${kometa_plextoken}"
KOMETA_TMDBKEY: "${kometa_tmdbkey}" |
|
Okay. I think I solved. The secret part of the env can't have an underscore like I had. The below works. Thanks for your help. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version Number
2.0.2
What branch are you on?
master
Describe the Bug
I'm running Kometa on Kubernetes. I have used the example cronJob manifest as a starting point, and made relatively minor changes to suit my setup (configs linked below). A goal of mine is to keep all my configs under source control (GitHub), and also to not store tokens or API keys in plaintext. To accomplish that, I found the section of the documentation for Config Secrets. I've added a secret containing my various keys for Kometa, and the usage of
<<env_var>>seems to work fine. Except for the Plex token. When I run with the plex token obfuscated, it reports:Plex Error: Plex Token is read only. Please get a new tokenI don't think there is an issue with the Plex token because if I hardcode the token, it works perfectly; no error is reported and it does its thing.
I've also verified the environment variable
$KOMETA_PLEX_TOKENreturns the token as I entered it when creating the secret.If it would help to look at my files, they are here. The
cronJobmanifest is here, and the config creating the error is here.Relevant Collection/Overlay/Playlist Definition
No response
Logs
https://gist.github.com/educatedCaveman/a0054a551b12df075fc467a401a7cd28
The text was updated successfully, but these errors were encountered: