RickSaysMeh 0 Posted November 12, 2016 Posted November 12, 2016 Emby server: 3.1.6160.5501 dev Roku firmware: 7.5.0 build 4096 Emby channel: 2.24 Blue Neon: 3.94 When trying to play any media on the Roku, Emby quits out to the Roku home screen. Blue Neon Theme gives me an error on connect (Capabilities Error! Failed to Post Capabilities.) but then lets me select my user and shows my content, but selecting any media and then selecting Play gives me an error (Response Error! No Dynamic Playback info Found.(invalid)) and then quits to the Roku home screen. The web interface works perfectly fine with the same content. I add the server manually, not with Emby Connect. I haven't checked any log files yet.
Luke 42078 Posted November 12, 2016 Posted November 12, 2016 Probably related to the dev server. Thank you for testing prerelease versions.
mediacowboy 438 Posted November 12, 2016 Posted November 12, 2016 (edited) @@Luke I am seeing the same behavior. Which stinks as the Roku is my primary streaming device as this time. Update: Was also unable to connect with my iPhone emby app v 1.2.9. Rolled back the server and was able to again connect both iPhone and Roku. Edited November 12, 2016 by mediacowboy
RickSaysMeh 0 Posted November 12, 2016 Author Posted November 12, 2016 I can confirm that rolling back to 3.1.6159.29609 dev resolves the issue with Roku and the Windows Phone app (would not connect when trying to add the server). I don't know if it makes a difference, but I use a reverse proxy to access my server. https://emby.mydomain.com (port 443 with valid SSL cert) is routed to internal http://192.168.0.50:8096. No issues prior to this server update. May not be related.
Happy2Play 9780 Posted November 12, 2016 Posted November 12, 2016 Is there a reason you are using a Dev build? Do you have these issues on Stable build?
mediacowboy 438 Posted November 12, 2016 Posted November 12, 2016 I run dev to help test issues like this Sent from my iPhone using Tapatalk
mediacowboy 438 Posted November 13, 2016 Posted November 13, 2016 Issue appears to be gone in version 3.1.6160.32019 of the server.
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