LiveTV -> Browse -> An unexpected error occurred

Server Version#: 1.41.8.9834-72009834 running on Synology

All worked for year, but now the “Live TV” → “Browse” section shows “Something went wrong; An unexpected error occurred”. “Guide”, “Whats on”, “DVR Schedule” sections in Live TV are working and filled as usual.

But Browse is of course my way to find upcoming streams which I want to record. I restarted the whole Plex Service already, but no change. Any recommendations?


yes its broken plus also when you download the latest beta version of the media server.
I simply removed Plex on my Synology NAS (uninstall only to keep the config files) and then I used the version from Synology package center which is version 1.41.5.9626.

Ensure you go via Install using Plex Claim Token to get back the config etc.

So the way would be to wind back to an older release or wait until the new one has been fixed again?

Yes you can back down to 1.41.7.9823 and it works.

Not sure about this version you mentioned @pl_5309 question is from where you can download it for Synology DSM >7.2?

https://www.plex.tv/media-server-downloads/#plex-media-server

I tried the Intel/AMD 64-bit latest beta version PlexMediaServer-1.41.9.9912-371133ff9-x86_64_DSM72.spk from June 26th , but issue still exists

https://www.plex.tv/media-server-downloads/?cat=nas&plat=synology-dsm72#plex-media-server

Sorry I had 3 conversations going on and didn’t properly scroll to the top for the issue.

Yes it still isn’t fixed in the new beta, the version I listed is the only working 1.41.7 version, you can go to 1.41.6.9685 which was before the database bloat issue.

There is a github project that tracks all Plex Download URL’s you can retrieve the link for any previous version there: GitHub - axlecrusher/plex_download_urls: Archive of Plex mediaserver download URLs

Hello
Je suis aussi concerné avec la version v.1.41.8.9834-071366d65
J’espère que les développeurs de Plex pourront résoudre ce problème et proposer une mise à jour bientôt.
Merci.

Not sure if I want to wind back, but lastest v.1.41.9.9961-46083195d from July 3, 2025 still has not fixed the issue. Is their a bug id which I can track?

There is another thread around this issue. Please see:

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.