Has anyone from Plex acknowledged this problem? Will it be fixed in the next release?
Maybe I missed it but I haven’t seen anyone from Plex reply or acknowledge this issue.
Standard.
1 Like
@aztbr This may be of some use to you if you want to rollback to an earlier version.
https://forums.plex.tv/t/i-need-to-rollback-from-the-latest-plex-update/233585/2
For an earlier version of Plex for Windows, there is an archive on Github of past plexmediaserver download urls. Find the version you need and the link will initiate the download from the Plex Download Server.
https://github.com/axlecrusher/plex_download_urls?tab=readme-ov-file
I have seen no official acknowledgment of this issue. I don’t want to “workaround” a problem on the “stable” channel, @plex_devs , test case right here, make sure browse endpoints are reachable / validated before stable release.
Also @plex_support some official acknowledgment here in this forum post would be good, as long as people know an issue will be fixed at somepoint they are usually happy to wait.
1 Like
I think that plex support is somewhat aware that some are having an issue:
https://forums.plex.tv/t/browse-in-livetv-tab-reports-error/920628/14
My suggestion is that each person with this issue start a new post on here. Be very specific on what the issue is. The title should be very specific. Like - Updating from 1.41.7xxxx to 1.41.8.xxxx caused this problem.
Follow all the guidelines: https://forums.plex.tv/t/help-us-help-you-how-to-provide-logs-to-get-your-problems-identified-and-hopefully-resolved/672904
Be sure to list your OS and version. Your current pms version. Which players work. Which players don’t. And their version.
Most important: Post your Logs. Full Logs.
Is anyone else having problems downloading logs? Every time I’ve tried, for months now, it’s failed. It opens a browser, points it at an address at plex.direct which contains what I assume is a v6 IP address (though I haven’t confirmed that) but the browser fails to connect. Is there some way I can pull the logs directly from the server?
This post might help you locate where the Logs are at:
https://forums.plex.tv/t/using-plex-sqlite-on-freebsd/805450/2
It looks like a Plex Employee acknowledges the issue in a similar thread…
Browse in LiveTV Tab reports error - Live TV & DVR - Plex Forum
1 Like
Resolved issue by downgrading to previous version. ( Version 1.41.7.9823)
Plex needs to make a statement about the latest version being broken if they aren’t going to fix it soon.
I am having the same issue.
To confirm the latest PlexMediaServer-1.41.9.9961-46083195d-x86_64_DSM72.spk
DOES NOT fix this issue.
Same here, 1.41.9.9961 does not fix the Problem. With this issue persisting using the DVR function of Plex becomes increasingly senseless and with that paying for the Plex Pass.
This is fixed with the latest beta of Plex Media Server 1.42.0.9975:
3 Likes
Thanks for the heads up. I’m normally against using Beta software on my NAS system, but in this case I can confirm that the Error is gone on my Asustor NAS now.
1 Like
Ditto, I have a family who will complain at me constantly if I live on any beta, this issue should not have made it to stable, there is an obvious function test here to make sure browse endpoints don’t return 500 errors. Please consider adding a test, i’m a long time user of plex now and this is not the first time Browse and search have broken in stable.
some love for OTA broadcasting support.
Still love plex and a blip every now and again is really not bad (although now been living with the issue for two weeks with janky search work arounds, is this not hotfix worthy?)
1 Like
I too ran into the same issue as well as the inability to search the TV Guide data when I restarted my Plex server. It seems to be caused by a missing column in the SQL Lite database. I reverted back to 1.41.7 where the browse and search function are now working correctly. The bug started in version 1.4.8.
Here are the two Error logs that I discovered.
Level
Error
Thread
Message
[Req#502f4f] SQLITE3:0x208, 1, no such column: media_items.begins_at in “select metadata_items.id from metadata_items join metadata_items as parents on parents.id=metadata_items.parent_id join metadata_items as grandparents on grandparents.id=parents.parent_id where metadata_items.library_section_id in (2) and metadata_items.metadata_type=4 order by media_items.begins_at asc, metadata_items.id asc, media_items.width desc, metadata_items.originally_available_at asc, media_parts.id asc”
Level
Error
Thread
Message
Got exception from request handler: sqlite3_statement_backend::prepare: no such column: media_items.begins_at for SQL: select metadata_items.id from metadata_items join metadata_items as parents on parents.id=metadata_items.parent_id join metadata_items as grandparents on grandparents.id=parents.parent_id where metadata_items.library_section_id in (2) and metadata_items.metadata_type=4 order by media_items.begins_at asc, metadata_items.id asc, media_items.width desc, metadata_items.originally_available_at asc, media_parts.id asc
was this fixed?
yes, it was
I can confirm this is now fixed for synology servers in the latest stable version PlexMediaServer-1.42.1.10054-f333bdaa8-x86_64_DSM72.spk
From a customer perspective using only stable, this problem lasted ~2 months.
Thankyou!
