Search the Community

Hello, I didn't see a post about this, so I thought I would ask. I'm pretty sure this has something to do with fedora, because the webplayer works fine at home on chrome/firefix/qutebrowser on arch (client side), however I'm currently on a fresh install of fedora (client side) and when I try to play a move in chrome or firefox, it hangs and in the js console I get a message about websocket problems. I added a few things to my apache config to try and fix this, but I went from a 404, to a 500 and then to a "Invalid Socket response" message. I'm wondering if I just forgot to install some library on the client side that is causing the browsers not to run the web player correctly. I checked the emby server logs and everything on the server end seems to be in order, emby even thinks the transaction was successful and shows the movie currently being played even though the web player stalled out in the browser. Nothing is showing up in the apache logs ether, so the proxypass I have set up is working fine. So my question is, could I be missing some libraries that chrome/firefox needs in order to properly talk over a webshell? I will be happy to provide the logs I mentions if you would like, but I don't know that it will be necessary as both (emby server and apache error logs) are clean.