Plex Photos - Library Something went wrong. An unexpected error occurred

Plex Players Desktop Players
, ,
1

Edit: Workaround, clicking refresh loads of the folder correctly allowing for a folder image to be changed. Does anyone understand what is going on?

I am running Plex on my qnap.
All my libraries work normally, music, movies, TV, but my photos library is wonky.
Although it is viewable on my iPad, iPhon, and NVIDIA shield pro using the Plex app (with all the correct cover art for the folders) when viewing this using the Mac, Windows or browser version (with more functionality) I can see the first layer of the photos in library mode where I can see all the correct cover art (decades) and clicking on one of the decades works and opens up the next level showing all the folders (years) and their correct cover art.

However, when clicking again though on any year folder in any decade the following error message is displayed “Something went wrong. An unexpected error occurred”

Plex client now needs to be shut down entirely before any other library will work.
I need this functionality to be able to change to cover art on the deepest level folders, the “months” folders.

I have tried optimising the library, restarting the server, restarting the client, tried on Safari on Mac, Edge on Windows, the app on Windows and the app on MacOS but the error is the same. Updating the server to Version 1.40.4.8679 made no improvement.

What could the problem be?
It is working on the iPad, iPhone, and Shield app perfectly fine, but It’s not possible to change the cover image on that version.

Could it be a corrupt database? if so, is it possible to restore one library and leave the others alone? Or does the entire Plex library need to be restored?

Many thanks in advance to anyone who can help me troubleshoot

3 Likes
2

Having the same problem with this error on my web player over Microsoft Edge, Chrome, and Firefox. It appears to be something with reading folders inside of folders in its first attempt. Refreshing my browser brings everything up. Not sure when it started…

1 Like
3

I have had this issue as well and when I reverted to version 1.40.3.8555 from 1.40.4.8679 it went away.

(Plex Media Server running as Truenas Scale App)

4

I have the exact same problem with the error message “Something went wrong an unexpected error occurred” when I click deeper into my photo library folders. When this error appears, all I have to do is refresh the page and the correct directory appears again until I click again and the error message appears again. My server is on Synology Station DS423+ in version PlexMediaServer-1.41.0.8994. The problem occurs on all web browsers. In mobile applications and in the Samsung TV Tizen application, this problem does not occur. In my opinion, a serious error that makes it difficult to use the photo library. Please support and treat it as a priority.

5

I also have the same issue. Refreshing the page resolves the issue. I think it is a frontend bug. My Plex server is running in docker on a ubuntu machine.

Screenshot 2024-10-14 at 12.09.41 AM
Screenshot 2024-10-14 at 12.09.41 AM1584Ă—316 105 KB

6

Something went wrong. An unexpected error occurred.
Having this issue in photo folders as well and cannot drill down in app or browser. In browser, if I refresh, it forces a logon again and does not resolve issue. It only occurs in some folders. In the app, I have to relaunch to do anything. I tried DB repair and complete reinstall, no change.

Win 11, brave and app

7

It seems a lot of us are having the same issue. When drilling down to a lower folder then I get the message “Something Went Wrong”. Strange thing is the next time I try the folder it works to the next level down and then repeats the error. A bit annoying if you have several levels of folders. (e…g. Family, Decade, Year, Month). Doesn’t matter what device I try to view on, e.g. iPhone, PC or Sony TV, it is the same .

8

Same error messages for me, but, when trying to download a subtitle, never happened before a couple a weeks ago.

9

ALL:

This issue has been filed, reproduced by Engineering, and assigned to an Engineer to resolve.

Thank you all for your posts but no further info is needed,

5 Likes
10

Same issue for me. Refresh workaround is working, but it is an annoying bug

11

same issue in my clients (Windwos, Web, excepting apps at TVs),
My workaround for the web UI and Windows App:
klick at the settings button and after that go back to previous page
(this workaround avoids re-login)
hopefully the engineer assigned is fast for resolving the BIG PROBLEM…
thanks in advance

12

Still doing it for me. I’ve given up on photos in plex (yes im plex pass) There engine needs rewriting - its not fit for purpose. Photos dont display correctly - all sideways. Slow.
Everything else is fine.

13

Do you have an expected release date? Not sure if its related but none of the images will load in the Plex Photos app on iOS either…

14

@john_lento_io

I unfortunately do not have a ETA on this.
The problem is server-side.

15

plex gallery error
plex gallery error723Ă—692 49.4 KB

Opening the same sub-gallery that errored in Chrome worked fine on the Nvidia Shield, Plex app

16

Getting the same issue on a local Mac drive. I saw someone on a prior post who was able to fix this with a Database repair script, but that was only on Windows. Is there not some built in option on the server to fix or rebuild a corrupt database? Right now ALL my photos are giving that message when clicking on them.

17

Documentation includes installing & running under macOS. Works great!

Good luck,

Chris

18

didn’t fix the issue

19

Bummer. Still it’s a good tool to have in your Plex Admin tools. Maybe you’re experiencing the problem ChuckPA referenced that is a server-side bug that they are working on.

Good luck,

Chris

20

I recently setup a new server while my old is running until I’m ready to make the switch. I’m building all new libraries from scratch on the new server (M2 Mac Mini). Source content is stored on a NAS, so each server is seeing exact same files and folder structure.

Old server has no issues. New server has this issue sprinkled throughout. Looks like I won’t be taking the old server offline as soon as I hoped :disappointed: