#Trakt Pin issue
1 messages · Page 1 of 1 (latest)
That shouldn't happen. Does the config file get updated with the rest of the trakt information?
Client ID and Secret are good.
Don't think so. Where would I look? First ti.e setting up here.
Time
Which lines should populate?
All those lines under "authorization"
Then apparently PMM can't write to the config file?
Odd that one thing populates, though.
how are you running PMM and in what environment?
and the log shows it authenticating correctly?
normally I'd say this is permissions, but since the one field updates that doesn't seem like the issue.
Only the first time. And not any other
I think the pin is single-use, so that part isn't surprising.
What's surprising is that is doesn't update all the fields in the config.
would looking at the log helP?
It would be interesting to see if there were any breadcrumbs in the form of an error or the like when the successful auth happens and the config file should get updated.
please provide log
The log is where I found it. I will look and take a screen shot.
The brute force fix would be to run pmm_trakt_auth.py from here:
https://github.com/chazlarson/Media-Scripts/tree/main/Plex-Meta-Manager
Then just paste the entire block it produces into the config file.
Ok
You have been asked to provide your log file, which will allow us to support you further.
You can find your meta.log file within the logs folder of your Plex Meta Manager config folder [right next to config.yml].
You can drag-and-drop your meta.log file directly into Discord, you do not need to upload it to a third-party site unless it exceeds the 50mb size limit.
Please DO NOT manually extract, copy and paste text from your log files directly into Discord as the formatting can be difficult to read and can often redact parts of the log file that are important for full context.
says you client id or client secret is invalid
so next part would be to check out that portion of your config
That sounds familiar. I think this has come up before and the solution was either a new trakt app or a different trakt account.
Config Warning: trakt sub-attribute pin not found using None as default
maybe indentation is off?
Should I pull the log from the first run?
This:
[INFO] | Connecting to Trakt...
[WARNING] | Config Warning: trakt sub-attribute pin not found using None as default | trakt sub-attribute pin added to config
[INFO] | Navigate to: https://trakt.tv/oauth/...
[INFO] | If you get an OAuth error ...
[ERROR] | Input Failed
[INFO] | Trakt Connection Failed
is expected if there is no pin in the config.
Agree. It works the first run, and not any other.
This is one of the later failing runs?
i suggested we see the config file
Yes
This line:
[WARNING] | Config Warning: trakt sub-attribute pin not found using None as default
shows that the pin attribute is not even present in the file, and I don't think it gets removed once used. This is really odd.
Can I see the log from the first, successful run?
trakt:
client_id: #####
client_secret: ########
pin:
# Everything below this line is automatically generated
authorization:
access_token:
token_type:
expires_in:
refresh_token:
scope: public
created_at:
pin:
Note the two "pin" entries; PMM can't see one of those so it's creating the other.
you striped out the part we need to see
which lines? Maybe I am missing them. I put ###s in the stripped
If I start with this:
trakt:
client_id: bingbangboing
client_secret: boingbangbing
authorization:
access_token:
token_type:
expires_in:
refresh_token:
scope:
created_at:
pin: AFED19BC
The log shows:
| Connecting to Trakt... |
| Saving authorization information to /config/sb-config.yml |
| Trakt Connection Successful |
and the config now shows this:
trakt:
client_id: bingbangboing
client_secret: boingbangbing
authorization:
access_token: foobarbaz
token_type: Bearer
expires_in: 7889237
refresh_token: bazbarfoo
scope: public
created_at: 1664646039
pin:
So it apparently does empty the pin.
sorry i missed it the first time
client_id: #####
client_secret: ########
pin: <<<<<< ONE PIN ATTRIBUTE
# Everything below this line is automatically generated
authorization:
access_token:
token_type:
expires_in:
refresh_token:
scope: public
created_at:
pin: <<<<<< ANOTHER PIN ATTRIBUTE
The log shows that PMM added it.
[INFO] | Connecting to Trakt...
[WARNING] | Config Warning: trakt sub-attribute pin not found using None as default
| trakt sub-attribute pin added to config << RIGHT HERE
yep. maybe on the first run, pin was not alligned correctly
The first run shows no problems:
[INFO] | Connecting to Trakt...
[INFO] | Saving authorization information to /config/config.yml
[INFO] | Trakt Connection Successful
BUT, this is interesting.
the first run shows 17 attributes missing from the config and added.
the second failing run shows those same 17 attributes missing from the config and added again.
I have also left the original pin in and it would not validate. Let me see if I can find that log
I think something is overwriting your config file before the run.
Or you're not using the config file above.
is there possibly another config file that isn't mapped correctly?
Log says, for example:
Config Warning: settings sub-attribute asset_depth not found...
settings sub-attribute asset_depth added to config
But that config file above shows that it is in fact not missing:
settings:
...
asset_depth: 0
so either there's a problem reading the config file OR the config file above is not the one being used by the script.
The config file looks fine, so I don't think there's a problem with it.
That’s what it seems like there is another config file involved
I have been editing and editing one to try to fix trakt
What does the unraid container config look like?
So the config file above is not the one that produces those logs?
If that's some other random config, then this exercise has been futile.
The logs you've provided are showing errors that this config file should not have produced.
I’m with you @stiff sluice the errors showing, don’t seem to match the config we’re looking at
What config file produced this log?
If it wasn't the one provided above, there's no point in my looking at it.
Until you provide the config that generated it.
Shows all the same errors.
Agreed
I have been editing and editing the same one. I have not changed the trakt area.
But the errors don’t match the config file
For example:
Connecting to Movies Library... [ERROR] | Config Error: metadata_path attribute is blank
but in the config above that isn't true:
libraries:
Movies:
metadata_path:
- file: config/Holiday.yml
ok, I will run a new log with a new pin with the latest config then then run it again to fail.
The log reports loading one TV metadata file, but the config contains two.
I'm virtually certain that config is not the one being used by the script.
In addition, what I see is there has to be a separate config file save somewhere else, possibly mapped incorrectly, that is being run instead of the above config
I’m just trying to help
It’s helping me in the process
Here are the things that the script is saying are missing and maybe added:
omdb attribute not found
mdblist attribute not found
mal attribute not found
playlist_files attribute not found
Those are in fact not present, so these errors are accurate.
These, however:
settings sub-attribute asset_depth added to config
settings sub-attribute prioritize_assets added to config
settings sub-attribute dimensional_asset_rename added to config
settings sub-attribute download_url_assets added to config
settings sub-attribute show_missing_season_assets added to config
settings sub-attribute show_missing_episode_assets added to config
settings sub-attribute show_asset_not_needed added to config
settings sub-attribute default_collection_order added to config
settings sub-attribute item_refresh_delay added to config
settings sub-attribute delete_not_scheduled added to config
settings sub-attribute only_filter_missing added to config
settings sub-attribute show_options added to config
settings sub-attribute playlist_sync_to_users added to config
settings sub-attribute playlist_report added to config
settings sub-attribute verify_ssl added to config
settings sub-attribute custom_repo added to config
settings sub-attribute check_nightly added to config
tmdb sub-attribute cache_expiration added to config
tmdb sub-attribute region added to config
radarr sub-attribute upgrade_existing added to config
radarr sub-attribute radarr_path added to config
radarr sub-attribute plex_path added to config
sonarr sub-attribute upgrade_existing added to config
sonarr sub-attribute sonarr_path added to config
sonarr sub-attribute plex_path added to config
The config file you've provided has these things in it, however you've also provided multiple logs with these very same things reported as missing. That should only happen once unless someone or something is removing them between the two runs that show them missing.
BTW, there's an automatic config-redactor, in case you're doing that manually:
You have been asked to provide your config file, which will allow us to support you further.
Please DO NOT share your config.yml file as is without redacting it. It contains information that you do not want the public to have, nor do we need it to troubleshoot your scenario in MOST cases.
We will use a regex parser to redact the file for you.
:one: Goto https://regex101.com/r/DMo1DQ/latest
:two: Copy the contents of your config.yml to the TEST STRING box in that page
:three: The results will be immediate and found in the SUBSTITUTION box below
:four: From the SUBSTITUTION box, select all, then copy and paste the redacted text into the channel where you want to share your config. (You will see (redacted) where confidential information was replaced)
Consider using Discord code blocks when sharing small parts of your config file. Check out !code for more info on code blocks
also i notice your config is named config-stripped2.yml. if you dont name it config.yml then you have to specify the config when you run with --config
i think he changed the name to send it to us
after he stripped stuff
thats possible but if he didnt then that would be a cause as to the multiple configs
I did rename it
his first config he sent is called config-stripped.yml so thats why i said something
yep, for sure
if you have multiple config*.yml in the config folder then you have to specify the config in your command
it is called config.yml in the docker container. Nother else called config*.yml
just making sure
@stiff sluice did ask to see how the unraid container was configured
i don't have unraid experience so that issue i could not help with
we also need the meta.log for this config too when the run is done
yes, so far none of the log files have matched up with the config files
PMM run 2 in progress
why a 2nd run?
What happened to run 1?
It fails on run2
then we need the log
show me the log from run 1, please.
we need the log and config from run 1
Pulling log from run1
presumably the config is the one above.
it is
ok, just was making sure
Run1, trakt success
What does the config look like right now?
for run 2 correct?
Yes, the config should now contain the trakt authentication info.
Though that log does not show it writing that info.
Thanks, saw that
[INFO] | Connecting to Trakt... |
[INFO] | Trakt Connection Successful |
you have an issue here too
[2022-10-01 14:20:31,250] [library.py:141] [ERROR] | YAML Error: mapping values are not allowed here |
| in "/config/TVCharts.yml", line 47, column 12
Same as the last upload, config-stripped2.yml
trakt:
client_id: #######
client_secret: #######
pin: #######
# Everything below this line is automatically generated
authorization:
access_token:
token_type:
expires_in:
refresh_token:
scope: public
created_at:
``` this should be filled in now though. is it?
looking
It was filled in and trakt now works. Weird.
[INFO] | Connecting to Trakt... |
[INFO] | Trakt Connection Successful
awesome. just need to change root_folder for radarr and fix the issue in your TVCharts.yml
if you send your tvcharts yml we can look and see whats going on if you want
IMDB Popular:
template: { name: Chart, num: 4 }
tmdb_popular: 40
imdb_list:
url: https://www.imdb.com/search/title/?title_type=tv_series,tv_miniseries
limit: 40
summary: IMDB Popular Shows across the internet
IMDB Top Rated:
template: { name: Chart, num: 5 }
imdb_list:
url: https://www.imdb.com/search/title/?title_type=tv_series,tv_miniseries&num_votes=20000,&sort=user_rating,desc
limit: 100
tmdb_top_rated: 100
summary: Top Rated IMDB TV series across the internet
so this whole part here you are mixing tmdb and imdb stuff
I think I found the issue, I think I was writing over the section below "# Everything below this line is automatically generated" evertime I changed the config
Ok, I will have to look and verify
tmdb_popular: 40
tmdb_top_rated: 100
I see those 2 lines, thanks.
Well, that would do it. Would also explain all the fields that were continually missing.
I appreciate everyone's help. You people are awesome.
I assume you had an open editor and never reloaded?
i've done that before
Ok, case closed. Thanks everyone.