No problem, it’s been an anoying problem for as long as i can remember, my Server Version# = 4.116.1, the app i’m not sure, not near my tv now, but it’s updated automatically and my lg playstore is the one on recent tv (6.2 if i remember correctly) so it should be all up to date.
But it might be the same cause, it looks to me as if the player is looking for input from a (subtitle) file and interprets it as a bad request. I didnt test it yet, but is the first problem still there after your latest update?
i’ve moved on to using an apple tv, so i’m not using the lg app anymore, however, i’m running into this problem now and this problem doesnt occur on the lg app, so i might start using it again, fortunately it’s not possible to have subtitles on audiotracks ![]()