#Trakt.tv auth fails every time

1 messages ยท Page 1 of 1 (latest)

strong wasp
#

Using Docker Windows (using WSL2), I have been trying to auth towards trakt.tv for hours now.

What I have tried so far:

  1. Creating new app, as described, adding in the client_id and client_secret.

When running the script, it skips right over the place where I have to input pin and simply says "Input Failed". This is despite having -i -t on the command line.

  1. Using pmm_trakt_auth.py, it authed correctly and gave me a config string to put into config. Having done that, it still does the "Refreshing Access Token", then wants me to go to the URL but still unable to put in Trakt pin as it skips right over the input, like in 1).

  2. Authenticating through trakt.tv, adding the pin to the config file fails with:

| Connecting to Trakt...                                                                             |
| Trakt Error: New Authorization Failed                                                              |
| Trakt Connection Failed
shell lagoonBOT
#

Please complete #938455615741775902 and someone from the community or one of our <@&938443185347244033> members will respond when they're available.

Including the meta.log from the beginning is a huge help use !logs for more information.

steady scaffoldBOT
#
Providing Log Files

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.

strong wasp
#

No meta.log, I am thinking there might be a permission issue. Closing this for now.

shell lagoonBOT
#

This post has been marked as Resolved and will be closed in one hour.

If you require further assistance on this issue, you can send another message in this post to re-open it.

If you require further support that is unrelated to this post, please start a new post and do not re-open this one.

Thanks for using Plex Meta Manager.

strong wasp
#

Note that I ctrl + c'ed it as I saw it failed.

This run was with client_id and client_secret filled out and nothing else.

What it should do is pause at the pin entry, so I can input something. It simply skips this.

Ran through docker run -i -t -v "h:/plex-meta-manager/config:/config:rw" meisnate12/plex-meta-manager --run

iron loom
#

you can put in the pin before PMM runs

strong wasp
#

I have tried that, see 3).

Fails with:

#
| Connecting to Trakt...                                                                             |
| Trakt Error: New Authorization Failed                                                              |
| Trakt Connection Failed
iron loom
#

let me try it

strong wasp
#

I'll try it again to have a proper log for it as well

iron loom
#

worked for me

#

I followed the guide from scratch

#

remember to put a space after the : in pin:

strong wasp
#

I know it should work, nobody else seems to have this specific issue but I am at a loss and had hoped someone might be all "ah yes, that's because x, y and z"

iron loom
#

try it one more time?

#

i.e. get a new client id and secret

strong wasp
#

I'm on my .. 4th app

iron loom
#

the pin will be case-sensitive too, so copy and paste it from trakt

strong wasp
#

I did see an issue regarding that on git and have tried with case sensitive, lower, and upper

iron loom
#

and you put urn:ietf:wg:oauth:2.0:oob in the redirect URI?

strong wasp
#

yeppers

#

no whitespace or nothing

iron loom
#

no spaces before or after it?

#

cool

#

idk then ๐Ÿ˜„

strong wasp
iron loom
strong wasp
#

Everything else works but that

#

Yeah, I tried that. It authed correctly. I put it all in. Gave me:

iron loom
#

odd

strong wasp
#

Config looks OKish? I was thinking some issues in there but I have slimmed it down as much as possible to avoid issues

jagged wharf
#

i just pushed a new version of nightly with updated error tracing for trakt

#

youll need to run it in trace mode

#

using --trace

#

once you grab the new nightly version

strong wasp
#

I saw someone on git that fixed their issues with a new trakt user. Just giving that a quick try, then I'll jump right on it

#

Guess what.

| Connecting to Trakt...                                                                             |
| Saving authorization information to //config/config.yml                                            |
| Trakt Connection Successful
#

the heck is up with that

jagged wharf
#

something was odd with your other user

#

the new build should tell you the response from trakt as to why

strong wasp
#

Yeah, my user profile gave a 404, but it logged in just fine

#

Guess it is just too old

silver vortex
#

If you switch back to the other user and generate the trace, does the problem return? It would probably be useful to have that information since this problem cannot be reproduced at will.

strong wasp
jagged wharf
strong wasp
#

Let me try

#

Tried a new pin a few times to ensure it wasn't timed out

#

Thanks for the assist and hope that helped a bit, certain trakt users are just broken, it seems.

jagged wharf
#

i want you to run it again in a sec

#

im adding some other outputs

strong wasp
#

oop, alright

jagged wharf
#

just pushed another version

strong wasp
#
| Connecting to Trakt...                                                                             |
| Trakt Error: (401) Unauthorized                                                                    |
| Trakt Error: (401) Unauthorized                                                                    |
| Trakt Error: New Authorization Failed                                                              |
| Trakt Connection Failed
jagged wharf
#

just pushed a third version if you could run that instead

iron loom
#

Sohjiro on ๐Ÿ”ฅ

strong wasp
#
| Connecting to Trakt...                                                                             |
| Trakt Error: (401) Unauthorized                                                                    |
| {'access_token': '1062b6d0c875e0bleep
cbc286f99deb935a906c0464724a2d4e518c98d6450074', 'token_type': 'Bearer', 'expires_in': 7889238, 'refresh_token': '7eaf7a37b291eeb60a1dfbloob12893394f59afe541c40ee95abf622bc322405', 'scope': 'public', 'created_at': 1661270529} |
| Trakt Error: (401) Unauthorized                                                                    |
| Trakt Error: New Authorization Failed                                                              |
| Trakt Connection Failed                                                                            |
iron loom
#

maybe redact a couple characters out of those keys

#

might be ok I guess it isn't a client or secret

strong wasp
#

wasn't sure if it could be relevant, probably not

#

Account dead anyway, but obfuscated it a bit

iron loom
#

๐Ÿ˜„

strong wasp
#

Let me know if I can help more, just highlight me. For now, it's spaghetti time