search

elgatito / plugin.video.elementum

Elementum add-on for Kodi. Development of this addon has been stopped!
http://elementum.surge.sh
MIT License
477 stars 157 forks source link

bad status getting error 403 - Issue on KODI #627

Closed jffp1101 closed 3 years ago

jffp1101 commented 3 years ago

Expected Behavior

Current Behavior

Upon navigating to Movies>>Popular Lists or any sections.. I am getting this msg BAD STATUS GETTING TOP LIST: 403

Possible Solution

Steps to Reproduce (for bugs)

1. 2. 3. 4.

Context

Your Environment

splitfirex commented 3 years ago

same here, i guess its the trakt token expired

elgatito commented 3 years ago

I had no notifications about expired/deleted ClientID. And it looks like for some people it is working, for some - not.

KillerJoeBR commented 3 years ago

It happened to me. So I had to create my own trakt api keys which is quite complicate for the average person. But it works now

jffp1101 commented 3 years ago

It happened to me. So I had to create my own trakt api keys which is quite complicate for the average person. But it works now

Nice! Care to share steps on how to’s?

syneoa commented 3 years ago

Confirmed working after creating Kodi API key and re-authorize trakt again.

ntzb commented 3 years ago

I get the same message. @syneoa and @KillerJoeBR care to share a short step list for that?

gudge25 commented 3 years ago

hi there i am using Elementum in LibreElec ISO (home cinema small PC) and there is no way to copy pacte API to Elementis settings is there a way to edit SOME conf file of elementum over ssh
Regards

elgatito commented 3 years ago

@gudge25 Edit settings.xml file inside plugin.video.elementum directory. https://kodi.wiki/view/Userdata

ShlomiD83 commented 3 years ago

I get the same message. @syneoa and @KillerJoeBR care to share a short step list for that?

https://koditips.com/create-trakt-api-key-kodi-addon/

jffp1101 commented 3 years ago

I was able to follow this instructions and work fine with me now! Here's the steps:

How to Create Your Own Trakt API Key:

Click here:
https://trakt.tv/oauth/applications/new
To go to the Trakt API application signup form. You’ll have to sign in to your Trakt account, so create one if you don’t have one yet and then make sure you are redirected to a page with the heading “Create a Trakt.tv API App”.

Fill out the form as follows:
2.1 Give your API a name.
2.2 Don’t worry about entering in an icon.
2.3 Give your API a description.
2.4 Enter in a redirection URL of "urn:ietf:wg:oauth:2.0:oob" or "http://www.google.com"
2.5 Leave the Javascript origins blank
2.6 Make sure /checkin and /scrobble are checked
2.7 Click the Save Button

Copy and paste your "Custom Trakt API Client ID" and "Custom Trakt API Client Secret" in Elementum -> Settings -> Trakt.

Reauthorize your Trakt account in Elementum's settings. Then Restart your Kodi. ! works!
kauly commented 3 years ago

Who will make a PR to fix this?

JacopoV commented 3 years ago

Confirmed here too. Working after API key and re-authorize trakt again.

pitsi commented 3 years ago

I noticed the above behavior today! I usually open the tv shows > recent episodes menu when I use elementum, so all the above went unoticed all these days. How can I fix the forementioned functonality without a trakt account? I do not have and I am not willing to make one.

I would not mind if there were 1-2 submenus that are not working without it, but it affects almost every single one under tv shows (trending, most popular, most played, most watched, most collected and most anticipated) and movies (popular lists, trending, most popular, most played, most watched, most collected, most anticipated and box office)!

iMobCoding commented 3 years ago

Why this issues is closed? Can you make a commit to fix this?

pitsi commented 3 years ago

As @crmagicxxx said above, now that all of trakt's... nonsense has stopped, can we get a fix?

https://old.reddit.com/r/Addons4Kodi/comments/jj9g41/trakt_api_changes_likely_a_big_impact_to_kodi/

elgatito commented 3 years ago

@pitsi what fix you expect? 0.1.59 already had new trakt key which is disabled again.

ntzb commented 3 years ago

@pitsi use your own api key, as described in the comments above. it eliminates the problem, and is not hard to do at all..

pitsi commented 3 years ago

@elgatito + @shmizan I just got the update to 0.1.59 and the problem is still there. The key was disabled indeed :( I do not want to create a trakt account for just the key. As I have said before, I do not create accounts here and there for stuff that should work with much less hassle.

antonsoroko commented 3 years ago

@pitsi Then simply add support of 429 HTTP status code to elementum code, then maybe shared trakt key will have less probability to be banned.

elgatito commented 3 years ago

@antonsoroko nobody notified about the reason why key was disabled. They don't even notify when they disable it.

pitsi commented 3 years ago

What if there is something "faulty" in elementum's code that gets the keys to be disabled in such a short time? E.g too many requests.

jffp1101 commented 3 years ago

Trakt is now enforcing rate limiting for all API's. If Elementum is used a single account in Trakt and all of us is using elementum, of-course others may experiencing issue. But... As I have post above the steps... IT RESOLVED my issue and everything works fine for me! Good luck to all and cheers!

elgatito commented 3 years ago

@jffp1101 Rate limiting is applied PER IP, not per Client ID.

@pitsi Trakt support wrote that they disabled elementum Client key because they think it sends too much "set watched" requests. That is a known issue and still is not resolved why it happens.

The only way is to create own keys or wait if Trakt issues in Elementum got fixed some time.

pitsi commented 3 years ago

Semi-offtopic. To be honest with everyone, I am fed up with all that "create an account to access our api" trend that every site wants to enforce lately. I do not want to be tracked, period. Since mid 2017 I had one single api to bug me with this nonsense, youtube's. I had created my own api keys because there was no other way to keep using kodi's addon. Then, in late March 2020, opensubtitles decided to block anonymous access to their api and asked me to do the same. After that, in early June, youtube decided to do some changes in their api, half the requests per day and delete a lot of api keys, including mine. And now trakt decides to do the same with their api...

rudf0rd commented 3 years ago

What if there is something "faulty" in elementum's code that gets the keys to be disabled in such a short time? E.g too many requests.

So what @pitsi said was correct. We were seeing a massive influx of duplicate history counts. For those that don't care about tracking, no big deal, but it will slow your system damn and waste a lot of your bandwidth if you're constantly syncing with Trakt and adding tens of thousands of plays per day. This combined with other Elementum users was impacting performance across all users.

@pitsi As far as why we 're starting to limit is because we've seen developers not treat the API with respect for the rest of the community. We don't believe this is malicious by any means, but really an indifference to the community. In order to restore performance, we're going to start putting automated checks in to keep things from blowing up. Aka spending more time and money policing people. It's not fun for us either..

To those that have added your own API key, but you're still using broken code from Elementum, in the eventuality this happens with your plugin, we will end up flattening your account to one play, revoking the API key that you created and you'll be back to the same issue.

@elgatito The real solution is to fix the code that is spamming our API.

elgatito commented 3 years ago

Please, read the announcement at https://github.com/elgatito/plugin.video.elementum/issues/636 And, please, do not add custom keys, and do not use previous versions of Elementum with Trakt sync.

pitsi commented 3 years ago

Please pin that issue report so as to stay on top!