Taxel / PlexTraktSync

A python script that syncs the movies, shows and ratings between trakt and Plex (without needing a PlexPass or Trakt VIP subscription)

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Internal server error with 0.28.5

Njur opened this issue · comments

commented

Confirmation

  • I have read the README.md on the project homepage
  • I have checked if identical issue already exists
  • I have tried downgrading to find version that can be used as a workaround

The problem

Hi after running a new scan I get this error, it normally runs fine and works for movies, but crashes on shows.
Error message: Internal server error. Please open a support issue and
include your full API request and response, including all headers.
ERROR API didn't respond properly, script will abort now. Please try again
later.
ERROR Last call: plextraktsync.trakt.TraktApi.search_by_id(('3042827',),
{'id_type': 'tmdb', 'media_type': 'episode'})

Error trace / logs

No response

Expected behavior

It normally runs fine.

Steps to reproduce the behavior

Tried running several times.

Inspect of problematic items

No response

Workarounds

No response

Install method

docker-compose

Config file contents

No response

Version

0.28.7

Python Version

3.12.1

Plex Server Version

4.15.7

Operating System and Version

Linux

Try downgrade, and give the exact version it got broken.

Same error, same id.
I've tried to downgrade every single tag, I've narrowed it down to the last working version (0.28.4).
There's something that broke it here 0.28.4...0.28.5
Let me know if I can add something useful, if needed.
Thanks in advance!

So, the error says it can't get response from trakt

ERROR API didn't respond properly, script will abort now. Please try again
later.
ERROR Last call: plextraktsync.trakt.TraktApi.search_by_id(('3042827',),
{'id_type': 'tmdb', 'media_type': 'episode'})

this should correspond to:

which shows result for two items, but they both link to:

image

also, the the api call indeed gives 500:

curl -sSf --header 'Content-Type: application/json' --header 'trakt-api-version: 2' --header 'trakt-api-key: xxx' --header 'Authorization: Bearer xxx' 'https://api.trakt.tv/search/tmdb/3042827?id_type=episode' -i
HTTP/2 500 
date: Mon, 15 Jan 2024 20:17:12 GMT
content-type: application/json
x-frame-options: SAMEORIGIN
x-xss-protection: 0
x-content-type-options: nosniff
x-download-options: noopen
x-permitted-cross-domain-policies: none
referrer-policy: strict-origin-when-cross-origin
x-pagination-page: 1
x-pagination-limit: 10
expires: Tue, 16 Jan 2024 04:17:09 GMT
x-pagination-page-count: 1
x-pagination-item-count: 3
cache-control: public, max-age=28800
x-error-message: Internal server error. Please open a support issue and include your full API request and response, including all headers.
vary: Accept-Encoding
x-ratelimit: {"name":"AUTHED_API_GET_LIMIT","period":300,"limit":1000,"remaining":999,"until":"2024-01-15T20:20:00Z"}
x-request-id: e307d0d2-9809-4ae7-a6d4-255a44ce6ec3
x-runtime: 2.662518
cf-cache-status: MISS
server: cloudflare
cf-ray: 8460ccf0ff5e09b7-ARN
alt-svc: h3=":443"; ma=86400

as the error says, it should be reported to trakt support.

don't forget to post back feedback you get from trakt support.

commented

[G4Zz0L1]: 0.28.4 worked, so will just stay with that until the later version gets fixed.
Thanks:)

It will not get magically fixed if the problem is with trakt site. you need to report it there.

Sorry, I didn't have much time this week.
I will try to report the error to Trakt and let you know.

And you can reopen the issue yourself if needed.

the sideeffect of this is that the whole script gets a aborted. Would be nice if it can log a warning/error and continue to the next item

You could remove match for the whole show in plex, then it would not attempt to update with trakt.

In fact, maybe fix match actually improves the situation?

yeah im currently fixing my matches to see if it resolves it

It should be fixed here trakt/api-help#435
It also suggests a fix for the url we call with this

you should had linked this discussion to that bug report, it was already determined here that there are duplicate results for same id. would had saved them some research time!