Noticed TrackTV not been working since 5th!

[vaise 340]

I have re-entered the pin stuff, getting unauthorised ini the logs.  Anyone else ?  Im running the beta server (latest).

 

Logs attached.

 

server-63654673013.txt

[Luke 42077]

What is tracktv?

[WilhelmStroker 102]

I assume Trakt. I'm not on the beta server but it's still working for me.

[Luke 42077]

Try re-doing your trakt authentication.

[vaise 340]

OK - will try that again.  Did it once tho.  I assume others on the beta track (no pun intended) would have reported this  by now if it was a beta issue.

[hstamas 179]

Posted logs in my post about broken Trakt. Had to bail on the plug-in completely as nothing I tried would fix the errors.

[Luke 42077]

I think the authentication saved in the plugin just expired. No new issue created.

[vaise 340]

Cheers.

I stopped the server, deleted the trakt.xml file, then re-started, then reset traked up - seems a reset over the top without the delete of xml was not working for me.

All good now.

[IcyBergals 8]

Cheers.

I stopped the server, deleted the trakt.xml file, then re-started, then reset traked up - seems a reset over the top without the delete of xml was not working for me.

All good now.

 

Thank you!  I've been having this problem since around the 5th as well and it's been so annoying.  Tried getting a new trakt PIN (didn't work), then reinstalling the plugin and redoing the PIN but it just didn't want to work.  Stopping the server and deleting the XML file then getting a new PIN finally did the trick.  No more manually marking things watched on trakt, wooo!

[jmedemar 8]

I was fighting with this same issue. Thanks to the help above, I checked my .xml file and found the expiration date of my token was 2-6-18. Even though I had gotten a new token and it saved to the .xml properly, the expiration time field was not updated properly in the .xml.  All I had to do was stop the server, delete the .xml file, restart the server, and save the new PINs for all my users.

 

If any of the plugin developers are listening in, please check this out in your implementation, as the .xml file is not updating properly when a new token is saved. Thanks everyone for the help!

[paulsalter 84]

Just checked my xml and it expires in April

 

Does this mean every few months we need to remember to get another pin?

[vaise 340]

Just an FYI, I had to do this process again today.  Not sure exactly when it failed to update, as I did not check the traked info - I just deleted and re-setup.  I did update to the latest beta this morning however.

[Luke 42077]

Why do you feel that you needed to do it again?

[vaise 340]

It kept failing to sync.  Tried to reset users, no go, so deleted the xml, then reset, and all working again.

[Luke 42077]

failing to sync in what way?

[vaise 340]

just says error - I did not bother to post it, as the fix was the same thing as i did last time.  If it happens again, I will attach a log.

[hstamas 179]

I’m getting “Bad Gateway" errors pretty much every night but then after some time it successfully syncs.

[Luke 42077]

I’m getting “Bad Gateway" errors pretty much every night but then after some time it successfully syncs.

 

That's some kind of network error and not related to this thread.