Server Version#: 1.19.1.2645
Player Version#: 7.31.0.16802
On Abdroid TV 9 (xiaomi Mi Box S) always message "An error occurred while attempting to play this video… Restarting server and App
Issue only happens with the new player, not the old one. Issue started since updating PleX (I updated both player and server today). Apparently not the only one with this issue (?). Plex Media Server Logs_2020-04-13_21-54-28.zip (3.8 MB)
Same thing happened to me,
Plex App was working fine on my Mi Box S,
then a day ago no files are playing,
getting the same error message suggesting I restart the Plex app & the server (which I did several times)
I am now casting Plex to the built in Chromcast feature of the Mi Box S, but the app for the Android TV is not working.
Do you have custom server access URLs entered in your plex settings under network? I did because my server is behind a nginx proxy but this was causing an issue because of the certificates with the same error using the new player. I removed them and port forwarded again and all is well.
There is a certificate verification using the new player but not the old. I suspect many of the issues people are having here in the forums may be related to reverse proxies and custom URL entries in their advanced settings and not having the certificates exactly right.
Totally agree. More than that - if I try to rewind 10 seconds back it breaks and can’t resume this video again even after app restart.
I think this should be looked into and addressed asap by Plex Devs.
Thank you for the feedback. Doubt is due to codecs as the issue started right after the update and only on the new player.
Still I did as instructed, deleted the codecs, restarted the PleX server, waited and the issue persists. Attached the fresh log without verbose. Hope something useful is shown there.
No custom access or nothing related. I’m not sure if this is the problem as I have always kept the same default configuration
and used the new player, and this issue started just after the last version update.
By the way, did a temporary roll-back on my client app and the issue persists, so at least now we know the issue probably comes from the server side.
Thanks for the idea though. I’m starting to think this is just a bug that was introduced on the last revision, and not user related.
No. I’m running the lastest PleX server app for Synology. Also this error started just after updating to the lastest PleX version.
It is weird that the transcoder fails to initialise, given it works with all my other clients and even in the mi box if the old player is used. Perhaps is not an issue on my side, but a bug introduced in the last server version?
This is not for the same server and player version, and I think is for the Nvidia shield specifically. Not quite sure if it’s the same issue as that topic is fairly old and mine started with the last relase, but Dave told me to create a new topic when I tried to piggyback on an existing one that seemed more related to my case.
Still thank you for the information. Will make sure to follow that topic.
Yw, It is a bug in the latest version of Plex software released to the public. If you backdate your plex software one version on the mi box it will work fine on the new player. Or just keep the old player for now until the next update comes out.
I’m using Synology as my server, and having MiBoxS as my player. all was fine with the latest Plex versions until MiBoxS was updated to latest version 9.0 Pie.
Solved the issue by switching to old player (yeah it sucks)
I checked the logs and found that it’s problem with the codec not able to run and not supported…
really hope there’s something we can do to solve the issue and get back to the new player.
04-10 21:55:23.262 i: [Player][ExoPlayer] Setting initial track selection…
04-10 21:55:23.262 i: [Player][ExoPlayer] Switching video surface to use MediaCodec surface.
04-10 21:55:23.263 i: [Player] onSurfaceChangeRequested
04-10 21:55:23.411 i: [FF] Video decoder doesn’t support aac (audio/mp4a-latm).
04-10 21:55:23.414 i: [FF] Audio decoder doesn’t support aac (audio/mp4a-latm).
04-10 21:55:23.416 i: [FF] Video decoder doesn’t support h264 (video/avc).
04-10 21:55:23.421 i: [FF] Video decoder doesn’t support aac (audio/mp4a-latm).
04-10 21:55:23.422 i: [FF] Audio decoder doesn’t support aac (audio/mp4a-latm).
04-10 21:55:23.423 i: [FF] Video decoder doesn’t support h264 (video/avc).
04-10 21:55:23.426 i: [FF] Video decoder doesn’t support aac (audio/mp4a-latm).
04-10 21:55:23.426 i: [FF] Audio decoder doesn’t support aac (audio/mp4a-latm).
04-10 21:55:23.428 i: [FF] Video decoder doesn’t support h264 (video/avc).
04-10 21:55:23.441 i: [ExoPlayer][EventLogger] surfaceSizeChanged [3.35, 0.00, window=0, 0, 0]
04-10 21:55:23.451 i: [ExoPlayer][EventLogger] timelineChanged [3.36, 0.00, window=0, periodCount=1, windowCount=1, reason=DYNAMIC
04-10 21:55:23.455 i: [ExoPlayer][EventLogger] period [675.00]
04-10 21:55:23.455 i: [ExoPlayer][EventLogger] window [675.00, true, false]
04-10 21:55:23.455 i: [ExoPlayer][EventLogger] ]
No. I already tried to go back to the previous version as mentioned in this very topic. The issue is not in the PleX client app but the server app (not even sure if there is other reason though). Not sure if you are trying to be condescending, but is a lousy attitude specially if you are wrong.