mr_zc 1 Posted October 25, 2025 Posted October 25, 2025 After the most recent build update to Emby for Roku (v 4.1.50), My Movies library fails to load and I receive a timeout error (the error appears after about 5 seconds or so). This did not happen prior to the most recent Emby Roku app update. It's been over a week now and, for the life of me, I cannot figure out how to fix it. I've attached some excerpts from my Emby log (debugging enabled), around the time I took the screenshots (~18:31:00 - 18:33:00). For anonymity, I've replaced certain data with generic placeholders (e.g. <PORT>, <SSL_PORT>, etc.) Any help or suggestions would be greatly appreciated. TIA! emby_log_excerpt.txt
Luke 42419 Posted October 26, 2025 Posted October 26, 2025 Hi, how does doing the same things in the Emby web app compare?
mr_zc 1 Posted October 26, 2025 Author Posted October 26, 2025 (edited) No issues in the web app nor in the iOS mobile app (both also up-to-date). Although, there is (and always has been) a little bit of lag when loading my Movie library. Edited October 26, 2025 by mr_zc
ebr 16414 Posted October 26, 2025 Posted October 26, 2025 Getting the subviews for that library is taking over 30 seconds: Debug SqliteItemRepository: GetSubviews_links query time (slow 6x): 30085ms. Much more likely this is related to the server update rather than the app one - or is just a coincidence.
mr_zc 1 Posted October 26, 2025 Author Posted October 26, 2025 4 hours ago, ebr said: Getting the subviews for that library is taking over 30 seconds: Debug SqliteItemRepository: GetSubviews_links query time (slow 6x): 30085ms. Much more likely this is related to the server update rather than the app one - or is just a coincidence. That's what I initially thought, but one of my TVs had a non-updated Emby for Roku and I tested on there -- everything worked as normal. Sadly, shortly after my tests, Roku auto-updated the app and then the Timeout error started showing. Additional Info: My Emby is running/installed on an external SSD via USB3 and my machine is kind of outdated, so the slow sql query speed isn't surprising (I have the same issue with other programs that utilize sqlite on my machine, via USB). Most of my libraries stored are on locally-hosted NASes, as well as on external HDDs. I think that too might be affecting the sql query speed.
Luke 42419 Posted October 28, 2025 Posted October 28, 2025 Hi there, please attach the Emby server log from when the problem occurred: How to Report a Problem Thanks!
mr_zc 1 Posted October 29, 2025 Author Posted October 29, 2025 21 hours ago, Luke said: Hi there, please attach the Emby server log from when the problem occurred: How to Report a Problem Thanks! Attached here. embyserver-anonymized.txt
mr_zc 1 Posted December 14, 2025 Author Posted December 14, 2025 On 10/31/2025 at 12:34 PM, Luke said: Hi we are looking into it. Thanks. This seems to have been resolved. Not sure which update fixed it, but it's fixed. Thanks! 1
andrikpinedasan 0 Posted 1 hour ago Posted 1 hour ago On 3/13/2026 at 6:21 PM, bennymac said: Hi Team, I have run Full Library Scans, refreshes after moving Media and not sure how best to proceed. In the past week we went from Media Libraries pointing to Local internal disks to a dedicated NAS and consolidated paths to single UNC path on the NAS for each content type. All libraries were updated and Library Scan's completed. From what i can see 90+ % seem fines although some media is not playing showing a failed artwork icon. For some files are not playing with "No Compatible Streams Available" Error. Looking into further some paths on content as pointing to old Path. E.g. TV Show library was configured for Z:\TV\XXX, D:\TV\XXX, F:\TV\XXX Now it's all \\192.168.1.221\Media\TV On some media we are getting a Playback Error On those media's metadata the old path shows. There is an alternative version of the same name. presumably what is being reference in the previous file path? We have run manual library scan's and freshed many times but it's not updating the paths. We've even removed the media from the library, refreshed and re-added. It displays the same behavior. Any idea's would be super appreciated. On 3/7/2026 at 3:12 AM, Kyz_Mini_Zal said: поставил в своей локальной сети On 5/1/2026 at 8:11 PM, Luke said: @sa2000
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