@sa2000 Having the same issue. Just started today. Was having issues buffering in original quality, had to dumb down to 720p and error starting showing up at about 75% through the movie. Happens when streaming on an XboxOne. Attached my logs as well.
What time was the error?
Best to also enable xbox one logging - see https://support.plex.tv/articles/206239048-xbox-one-logs/
and next time you get the error note down the time and get the logs zip for Plex Media Server and attach with indication as to when exactly the error arose
Hello, I can recreate this faithfully every time. Logs Attached though I’m not sure of the location of relevant info within them…
Plex Media Server Logs_2018-07-09_16-39-15.zip (3.8 MB)
First, what it isn’t. It isn’t an issue with multiple browsers from the same PC or multiple tabs within the same browser.
To recreate,
- Access https://app.plex.tv/desktop#
- In my case, the server is Remote
- Play item.
- Open another web tab/browser, repeat steps 1 - 3, see everything play correctly.
- With the items still playing, open Plex Media Player
- In my case, the server is Remote
- Play item.
- Watch item play on PMP, and tabs will freeze as they output the error message.
My daughter has a Kindle Fire and we were having issues playing items while I was watching something, I would assume that this is the cause. No error message was returned on her Kindle Fire, and I am unable to test it again because she is at the beach right now.
My server. this server, is actually on a linux box. My windows box is down right now or else I would test that too. My clients are all windows.
Server version: V 1.13.2
Server OS: Linux
Clients, w/ versions, if applicable: Windows Browsers w/ Plex Web 3.59.1 & Plex Media Player - up to date.
EDIT : I have now replicated this in both the hosted plex app and the bundled plex app, again by the same method, beginning playing of the file, and then playing a file in PMP.
Relevant info from the Debug Log, though my media is not bad, these are shows I have watched over and over again.
Error code 3, per https://developer.mozilla.org/en-US/docs/Web/API/MediaError
{
“type”: “log:message”,
“level”: 1,
“message”: “[Player] A critical HTML media error occurred: 3 (Decode); the player cannot recover”,
“time”: “2018-07-09T20:10:20.861Z”
},
{
“type”: “log:message”,
“level”: 1,
“message”: “[Player] A critical Shaka error occurred: 3016 (Media); the player cannot recover”,
“time”: “2018-07-09T20:10:20.862Z”
},
Shaka error 3015/3016, https://shaka-player-demo.appspot.com/docs/api/shaka.util.Error.html
So this is just some theorizing, but I would venture a guess the Access-Control headers are…getting confused on their original source. ie, not being kept per stream instance, and instead being kept globally. But it’s just a theory.
I got Error Code s3016 and cannot play any media via web app.
Logs shows some problem with Realtek audio codec (can’t find the codec)
using MS Edge
I can play media on youtube and other video streaming services with no problem as well as using other apps.
Plex App Player’s (Windows 10 app) playback is fine.
Thank you for the detailed post and for adding later a couple of log entries from Plex Web - I have server logs from you covering Jul 08, 2018 02:28:09 to Jul 09, 2018 16:39:09
What time was the error ?
I presume your log extract from Plex Web for the shaka error was after you got the server logs. I would need to have the shaka error as showing in the Plex Web matched to the server log to start an investigation.
You said
It isn’t an issue with multiple browsers from the same PC or multiple tabs within the same browser.
But your steps to reproduce the issue do say open multiple sessions on the same machine
Open another web tab/browser, repeat steps 1 - 3, see everything play correctly.
With the items still playing, open Plex Media Player
So this is a case of having multiple playback sessions on same machine
To identify sources of requests in the server logs i would actually also need verbose logging on the server - but what is absolutely important is knowing the exact time of error
Logs please and time of error
Best to reproduce after restarting the server. Before restarting the server ensure debug logging is enabled
see
https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
Dolby Audio driver on Acer laptop cause the problem. When I disable Dolby Audio improvements, then I can play media on Plex Web App.
I experienced this issue today and think I have a solution (at least one that worked for me). Check if you have any other audio devices or programs running that have captured your audio output. In my case, I run Roon to serve audio as my preferred streamer. I decided to add my music library to Plex today because I can’t get my family to bother with using Roon. When I shut down the Roon application (not the server, just the local UI) on my desktop, the error went away and Plex played the audio file locally without issue.
austingonzo
1 Like
austingonzo led me to the solution.
Plex Media Player, TV Mode, Audio Settings, Exclusive Mode is the culprit. Unticking that option solved my playback issue.
Same problem here. My mac mini playing live tv via HDHR extend using safari browser is doing the same thing. Error s3015. This use to work fine. No idea why its not now. The mac mini is also my plex server. All software is up to date.
Is this still an issue. The problem could not be reproduced after update to Safari version 12
If you continue to get this with Safari 12, please get diagnostics,
Enable Web logging (settings / web / show advanced / debug and set verbose logging)
Ensure server has debug logging (Settings / Server / General / Show advanced / enable debug logging)
Then reproduce the error, take a screenshot and not the exact time.
Then capture the web app log (settings / web / show advanced / debug and view log. Select all and copy to text file
and collect server logs (settings / server / help and troubleshooting / download logs)
1 Like
s3015 fix by changing the setting at the bottom to original no transcodeing and then plays fine.
hi, same problem here. I cannot find the option to change to “no transcoding”. May you show me where?
thanks!
The settings bar at the bottom of the video looks like a EQ kinda then change to original under drop down. Thought there was a setting for this also in setting but it now appeared to be gone after updating the PMS.
Same problem. Everything was ok… Until Error s3015. Always and everything. Any ideas? …“EQ” button on the bottom does’t help me.
Just updated to the latest version of Plex.( Version 1.14.1.5488 Up to date), and now I am getting this error code every few minutes during livetv. I haven’t tried other sources like movies, etc. attached are the diag logs. If I need to start a new thread please let me know. This is on a linux server running unraid. Though I am using the linuxserver build instead of the limetech build.
I am also playing over the current version of chrome.
I started the stream again, and will attach logs as soon as it messes up.
please let me know if I need to attach anything else.
Thanks,
Chris
issue occured. I received an s3016 error this time. attached are the logs, and the issue happened around 11:58am.Plex Media Server Logs_2019-02-11_11-58-52.zip (3.3 MB)
Issue occurred after waking laptop from sleep mode. Refresh page with no avail. Had to nuke browser to terminate instance to unlock session. Shall continue to monitor, post results is issue reoccur
Does this still happen ? The logs show at 11:55am watching an existing live tv session and then at 11:58 Plex Web reported an error condition. There is no indication from the server side as to why that arose
If this is still happening with later versions of Plex Web (the version in use at the time was 3.77.4) then would like to get Plex Web diagnostics (log) as well as the server. And if easily reproducible may need to run with dev console enabled and network browser capture - see https://support.plex.tv/articles/201611836-plex-web-app-logs/ for enabling web verbose logging
I have not received the error for some time now. This issue may now be resolved. Thanks for the follow up!
