-
Notifications
You must be signed in to change notification settings - Fork 5
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
Jellyfin server errors frequently reset the ZBR #308
Comments
I verified the request body is identical when it is part of a browZer or non-browZer session. |
The POST request is initiated by the Jellyfin Service worker when not running in browZer, and by the ZBR instead of serviceworker.js when running in browZer. Here's another example of a request that fails only in browZer. This one doesn't correspond with the ZBR re-bootstrapping itself the same way the other request did above.
{
"VolumeLevel": 100,
"IsMuted": false,
"IsPaused": true,
"RepeatMode": "RepeatNone",
"ShuffleMode": "Sorted",
"MaxStreamingBitrate": 1500000,
"PositionTicks": 0,
"PlaybackStartTimeTicks": 17221955326070000,
"PlaybackRate": 1,
"SecondarySubtitleStreamIndex": -1,
"AudioStreamIndex": 1,
"BufferedRanges": [],
"PlayMethod": "Transcode",
"PlaySessionId": "192a273e0c5a41a4b2d3bfdd2d93e96e",
"PlaylistItemId": "playlistItem0",
"MediaSourceId": "96a707bcf82206e68547b1bd2447a98a",
"CanSeek": true,
"ItemId": "96a707bcf82206e68547b1bd2447a98a",
"EventName": "timeupdate"
} When I visit Jellyfin in browZer and click on a media library the ZBR immediately re-bootstrapps, corresponding with but perhaps not caused by the server error response to If I attempt to play a video without first clicking on a library, such as one of the "recently added" titles, then I encounter the error response to |
Some requests via ZBR like
POST /media/Sessions/Capabilities/Full
get a server error (500), but only through browZer. The server error seems to trigger the ZBR to re-bootstrap, but it doesn't fix whatever the problem is.Here's a normal request body and response when not using browZer.
Response
The text was updated successfully, but these errors were encountered: