tjazar 1 Posted December 27, 2017 Share Posted December 27, 2017 I recently upgraded my Emby server to the latest 3.2.60.0, but after doing so, my media seems (at best) to be hit or miss in terms of actually playing. My setup is Emby server running on Ubuntu 16.04, with the Emby channel on a Roku 4 playing content on a local network. If I use 3.2.60.0, I repeatedly get "Corrupted Content" errors in Firefox when trying to load the Emby server page. Trying in an Incognito window usually works, but it seems to forget my settings all the time. On my Roku, attempting to play media gets met with an error message along the lines of "Malformed HTTP response". Further, none of my media will play on the server itself (in the browser), regardless of codec. This is despite the same media playing on server 3.2.50.0. My solution at this point has been to downgrade to 3.2.50.0. Everything seems to be working again, which makes the family happy. Link to comment Share on other sites More sharing options...
Luke 37214 Posted December 27, 2017 Share Posted December 27, 2017 hi, can you give an example of a url that shows this? can you provide the console output from firefox? thanks,. Link to comment Share on other sites More sharing options...
tjazar 1 Posted December 27, 2017 Author Share Posted December 27, 2017 Well, I've since downgraded to 3.2.50.0, but the answers to your questions are simple: the error was produced when trying to visit localhost:8096/, even after uninstalling and reinstalling. The console was empty, because that error message is from Firefox itself, not Emby. Firefox refused to load anything, because (as it claimed) the content was corrupted. It looked a lot like this image: Link to comment Share on other sites More sharing options...
mastrmind11 717 Posted December 27, 2017 Share Posted December 27, 2017 Well, I've since downgraded to 3.2.50.0, but the answers to your questions are simple: the error was produced when trying to visit localhost:8096/, even after uninstalling and reinstalling. The console was empty, because that error message is from Firefox itself, not Emby. Firefox refused to load anything, because (as it claimed) the content was corrupted. It looked a lot like this image: https://support.mozilla.org/en-US/questions/1011249 Link to comment Share on other sites More sharing options...
tjazar 1 Posted December 27, 2017 Author Share Posted December 27, 2017 I wiped my entire Firefox storage of cache/cookies/etc., and the problem still popped up. Using Incognito could get around it, and using a new container worked for a while, too. However, that doesn't explain the error on the Roku, which doesn't use Firefox to fetch Emby (at least, to my knowledge...). Link to comment Share on other sites More sharing options...
mastrmind11 717 Posted December 28, 2017 Share Posted December 28, 2017 So is this a local server or remote? Is SSL involved? What other intermediaries are there? Link to comment Share on other sites More sharing options...
tjazar 1 Posted December 28, 2017 Author Share Posted December 28, 2017 Local server, no SSL. Emby is on my Ubuntu 16.04 machine, and the Roku is on the same network. Link to comment Share on other sites More sharing options...
tjazar 1 Posted January 12, 2018 Author Share Posted January 12, 2018 I figure an update on this issue might be warranted. I have since wiped my hard drive and installed Solus OS. Emby is not packaged for Solus, so I downloaded the Docker install. Unfortunately, that gave me the same result on my Roku (and locally with Firefox). I must admit, I'm stumped as to what causes it. However, I wiped again on installed elementary OS, which is based on Ubuntu 16.04. I installed the Emby package, set it up, and everything is working just fine on Roku and Firefox. Again, I have no idea why, but at this point I'm just happy that I can watch my media again. 1 Link to comment Share on other sites More sharing options...
Luke 37214 Posted January 12, 2018 Share Posted January 12, 2018 Can you give an example? Thanks. Link to comment Share on other sites More sharing options...
tjazar 1 Posted January 12, 2018 Author Share Posted January 12, 2018 Can you give an example? Thanks. I'm not sure I follow -- an example of what? The problem is gone, and as I have wiped my hard drive, the logs are gone too. As I recall, the Roku app gave me a message about a problem with HTTP headers for any file I tried playing, including files that played previously with no problem. Link to comment Share on other sites More sharing options...
Luke 37214 Posted January 13, 2018 Share Posted January 13, 2018 Ok, thanks for the info. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now