-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR:root:Error getting streams from Plex: 'device' #14
Comments
Can you please post the full traceback of the error? |
This is very strange. As you can see here, the Please try the following:
This should cause a full traceback to be printed, along with the error. Please post that to this issue. |
Thank you for the response, this is what i get:
|
What is weirder, is that it seems i can get it to work only if i use plex via app.plex.tv . If i view media using its apps (i tried windows client and android client) i get the above error. To prove that, i sucessfully banned myself by using app.plex.tv from my pc and from my mobile phone (using mobile data) |
Interesting. You have someone streaming, but Plex isn't returning what kind of device they're using. It's completely omitted from the JSON response. I haven't seen this until now. Please do the following and see if it fixes the issue:
|
That worked! Trying to ban myself got this:
Thank you |
Great! I'm glad that worked. The fix is not permanent at this point, and will be reverted if you re-create the container. I will go ahead and make the changes and cut a new release so they will be permanent. |
That's great! Thanks! |
Hello, i'm getting the following error when someone streams on my plex server"
ERROR:root:Error getting streams from Plex: 'device'
If i access the status url directly on my web browser eg http://url:32400/status/sessions?X-Plex-Token=PLEXTOKEN i can correctly see the xml file getting populated with session data.
My plex token is correct and the container connects to my plex instance. What could be wrong here ?
The text was updated successfully, but these errors were encountered: