Jellyfin Forum
Unable to play/scream via the Webinterface on Chrome based browsers - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Unable to play/scream via the Webinterface on Chrome based browsers (/t-unable-to-play-scream-via-the-webinterface-on-chrome-based-browsers)

Pages: 1 2


Unable to play/scream via the Webinterface on Chrome based browsers - MikeSouth - 2024-07-24

Hi,
I am unable to stream/play any videos via the web interface using Chrome based browsers, it works fine using the apps as well as on Firefox. The error message I get is "Playback failed due to a fatal player error."

So I have jellyfin 10.9.8 running on ubuntu 22.04 on a baremetal Haswell CPU. It doesn't matter what Codec is used in the video, I can't play anything in Chrome, it doesn't matter what Client OS I use.

Full log: https://pastebin.com/mfBB5wRi
My encoding.xml: https://pastebin.com/EWNEAixk

More info about my setup
Code:
[root@<SERVERNAME> /var/log/jellyfin $ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.4 LTS
Release: 22.04
Codename: jammy
[root@<SERVERNAME> /var/log/jellyfin $ dpkg -l | grep jelly
ii  jellyfin                              10.9.8+ubu2204                          all          Jellyfin is the Free Software Media System.
rc  jellyfin-ffmpeg5                      5.1.4-3-jammy                          amd64        Tools for transcoding, streaming and playing of multimedia files
ii  jellyfin-ffmpeg6                      6.0.1-7-jammy                          amd64        Tools for transcoding, streaming and playing of multimedia files
ii  jellyfin-server                        10.9.8+ubu2204                          amd64        Jellyfin is the Free Software Media System.
ii  jellyfin-web                          10.9.8+ubu2204                          all          Jellyfin is the Free Software Media System.
[root@<SERVERNAME> /var/log/jellyfin $ lscpu | grep "Model name"
Model name:                        Intel(R) Xeon(R) CPU E3-1271 v3 @ 3.60GHz

Could someone please point me to to what I am doing wrong?

Thanks in advance,
Mike


RE: Unable to play/scream via the Webinterface - TheDreadPirate - 2024-07-24

Instead of using an override logging.json, can you remove that file and set the log level to Debug directly in logging.default.json in /etc/jellyfin? The log is much cleaner and easier to read when Debug is set in the default json file.

Also, you should remove jellyfin-ffmpeg5.

Code:
sudo systemctl stop jellyfin
sudo apt remove jellyfin-ffmpeg5

Ignore the prompts about "jellyfin-server not being needed". It won't actually remove them.

Code:
sudo apt reinstall jellyfin-ffmpeg6
sudo systemctl start jellyfin

Once you've reinstalled jellyfin-ffmpeg6, replicate the problem and share the new jellyfin log.


RE: Unable to play/scream via the Webinterface on Chrome based browsers - MikeSouth - 2024-07-24

They TheDreadPirate, thank you very much for your help.
I've just edited my thread because I only experience this on Chrome based browsers, it took a while to realize this as I basically only use Chrome based browsers.
jellyfin-ffmpeg5 was not installed but still had config files "^rc", of I've purged it. The process > https://pastebin.com/RDQHXMBa
Here is the jellyfin log after removing logging.json and restarting jellyfin  > https://pastebin.com/wB5yX3HT
Here is the ffmpeg output > https://pastebin.com/WxefdkYz

The browser used was a google chrome version 127.0.6533.72 on ubuntu 24.04 linux with zero extensions.

Here is the working ffmpeg logfile when using Firefox 128.0.2 on OSX
https://pastebin.com/pqcyAidA


RE: Unable to play/scream via the Webinterface on Chrome based browsers - theguymadmax - 2024-07-24

Code:
  <AllowAv1Encoding>true</AllowAv1Encoding>

Turn off AV1 encoding. Your iGPU doesn't support it.


RE: Unable to play/scream via the Webinterface on Chrome based browsers - MikeSouth - 2024-07-24

(2024-07-24, 04:12 PM)theguymadmax Wrote:
Code:
  <AllowAv1Encoding>true</AllowAv1Encoding>

Turn off AV1 encoding. Your iGPU doesn't support it.

Thank you for your input, unfortiently this didn't solve the issue
Code:
[root@<SERVERNAME> /etc/jellyfin $ service jellyfin restart
[root@<SERVERNAME> /etc/jellyfin $ grep Av1 encoding.xml
  <AllowAv1Encoding>false</AllowAv1Encoding>

It still depends on the browser, see [Image: jh4nwHX.jpg]


RE: Unable to play/scream via the Webinterface on Chrome based browsers - TheDreadPirate - 2024-07-24

(2024-07-24, 04:12 PM)theguymadmax Wrote:
Code:
  <AllowAv1Encoding>true</AllowAv1Encoding>

Turn off AV1 encoding. Your iGPU doesn't support it.

They didn't have HWA enabled, so it doesn't matter.

Code:
<HardwareAccelerationType />

But the CPU is probably not up to the task either.  So it should have been disabled anyway.

Are you using a reverse proxy?  If so which one?


RE: Unable to play/scream via the Webinterface on Chrome based browsers - MikeSouth - 2024-07-24

Yes I do use a reverse proxy, nginx Version 1.18.0-6ubuntu14.4
Config: https://pastebin.com/UdLsg7We


RE: Unable to play/scream via the Webinterface on Chrome based browsers - theguymadmax - 2024-07-24

Try disabling hevc encoding. That could be difference between Chrome and Firefox.

Also to correct my prior post, your processor doesn't have an iGPU, so I'm assuming this is a headless system.


RE: Unable to play/scream via the Webinterface on Chrome based browsers - MikeSouth - 2024-07-24

(2024-07-24, 04:47 PM)theguymadmax Wrote: Try disabling hevc encoding. That could be difference between Chrome and Firefox.

I just did that, unfortiently it didn't change anything.
Code:
[root@<SERVERNAME> /etc/jellyfin $ service jellyfin restart
[root@<SERVERNAME> /etc/jellyfin $ grep HevcEncoding encoding.xml
  <AllowHevcEncoding>false</AllowHevcEncoding>

jellyfin log: https://pastebin.com/n8LhC0Fc
ffmpeg log (much much longer then before): https://pastebin.com/QBgj5gU2


RE: Unable to play/scream via the Webinterface on Chrome based browsers - theguymadmax - 2024-07-24

Unless I'm missing something, your processor has no hardware codec support so everything should be disabled.