I can’t seem to transcode anything anymore. I get the error Shaka1002 Network when I try to transcode anything. Plex crashes and wont’ restart with the Plex Tuner still running.
Anyone have an idea what’s going on? The logs say nothing
I can’t seem to transcode anything anymore. I get the error Shaka1002 Network when I try to transcode anything. Plex crashes and wont’ restart with the Plex Tuner still running.
Anyone have an idea what’s going on? The logs say nothing
I’ve noticed this behavior as of late to. Like on old YouTube ddl’s that I think were vorbis? IDK.
-wbm
ps. except PMS doesn’t crash, i jez bypass and carry on.
It only happens when transcoding. Direct play works fine. Are there transcoding logs anywhere?
I’m using a i3-8100 with Ubuntu 17.10, fresh install
If you recreate the error, before the logs are overwritten by subsequent log activity, Settings - Server - Help - Download Logs
Please attach the ZIP file it presents you here with your next post
I will also need the client logs, while sitting at the error popup, as this is a browser error. https://support.plex.tv/hc/en-us/articles/201611836
Here you go. I think the issue may be the hardware transcoding.
Has there been any solution to this, yet? I’m having the same issue. My PMS is on a Mac Mini. Looks like if there’s transcoding to be done, I get the shaka1002 Network error. It completely crashes PMS, and I have to SSH into the Mac to reboot it.
It started the other day, when trying to play anything through PlexConnect was crashing the server (with no error reported). Then tested in PlexWeb, and it throws the shaka error.
Tried different transcoding settings, and turning on/off DirectPlay and DirectStream, with no solve yet. The only thing I see that’s odd is my “Transcoder temporary directory” setting is empty, but near as I can tell it’s always been that way (I never specifically set it).
UPDATE: I may have solved it for me; turned OFF “Use hardware acceleration when available”, and now everything seems to play correctly in PlexWeb AND PlexConnect.
Sorry for the late reply. I fixed the issue by updating the libva and vaapi drivers from Intel’s github.