Server Version#: 4.125.1
Player Version#: 1.40.2.8395
I added some more images to my Plex and now when I click on a selection I am getting the error above. “Something went wrong” “an unexpected error occurred”. This particular Server in on my Mac Studio. I can access ALL folders and sub folders and images from any other play that I have tried (iPhone, another mac, iPad) Everything works except when I run the play right on my Mac Studio. And since I have a Plex Media Server on a Synology NAS system, I cannot even access it from the Plex Player on the Mac Studio. I have check to see is there was a newer version and I am up to date. Also, if I run the Plex Medio Server and not the player, I can access everything on the Mac Studio. I seems to be an issue with just the Plex Player on this Mac Studio.
I will update this a bit. I downloaded a new copy of the Mac OS Plex Player and it still gives me that “Something went wrong” message. Also, if I run the Plex Media Server on this same Mac, it will run just fine.
Any updates on this by chance? I am experiencing the same: Got the latest version (4.132.2) running on Synology NAS. When I access a Photos folder, it says “Something went wrong.” If I hit reload in Safari/Chrome, it asks to “Select profile” and then it shows the content on the folder.
I think I’m on the same situation. For some reason, in a photo library, going deeper than two subfolders will always show a “Something went wrong” error. If I reload (cmd+R), the folder loads correctly, but if I keep going deeper in the folder structure I have to keep reloading to have the directory load correctly. Also, once the error appears, moving to any other library keeps the screen stuck at the error. So I have to keep reloading.
I’ve tried lot’s of things, rescaning the library, refreshing metadata, checking database integrity, rebuilding index, but I keep getting the error. The only way I’ve been able to avoid it, is via browser and using my plex custom domain. Even if I login via app.plex.tv I get the error, but if I do plex.mydomain.com, then it works great.
I am still having this issue and is seems that it doesn’t matter where the server is. If I run a Plex player on other devices that I have, I get this error most of the time. This seems to be JUST the player’s issue, regardless of which player it is. I continue to update them players whenever I can see an update, but this does NOT solve this issue. I am running three servers. two of them are on their own Synology NAS device while the third is on a Mac Studio. I would think that Plex people would help us with this.
I was curious about your cmd+R, so I went to my Plex Player on the Mac and as soon as I click on a folder and it gave me the error message, I did a cmd+R and got my pictures & videos. But, it happened again as I drilled down into deeper folders. The thing is that it seems that if I have very hollow folders, I can get the images without the error, but as was stated, the deeper the folder structure, the error reoccurs as each level.
I have very specific folders. For example, I name each primary such as my name . Then the year <2024>. Then the month <01-January>. And finally the Day <2024-01-12>. So, in most cases, I travel down at least 4 folders before I get to images and/or videos. When I tried the cmd+R on just one of these, I have to perform the cmd+R on each level before I was able to see the next level down and then to finally view the images/videos. Then SURPRISE/SURPRISE!!! once I got to the actual images, it froze the Plex to that level. I could not go back up to a previous level (ie. showing all day within that month. But I could go to a different primary level.
Doesn’t ANYONE have an answer to this? This is getting real irritating. And again, this doesn’t seem to be a problem when you are running Plex from the Server. But, I also found that my player on a PC running Windows 11 Pro also is getting the same problems. Also, this seems to be migrating to my Plex servers that are Synology NAS systems as I am getting the error when trying to access them. And again, it freezes the player. I have to exit or terminate the player to go back in. I have also removed and recreated libraries to see if that is causing the issue. And it doesn’t see to matter if the folder has a lot of images/videos in it or not.
I didn’t realize what you meant by Cmd-R and the first time I used it, I must have done something wrong because it didn’t seem to work. But, after re-reading this, I tried again and I see what you mean about reloading. You are correct, it does reload and it does not let you move around or back out once reloaded. This seems to be an ongoing issue.
I am surprised that someone at PLEX hasn’t responded with why this is doing it.
Come On!!! Isn’t there anyone out there that can resolve this issue. WHY is this happening? I can’t get anywhere on my plex!!! I keep getting this error message!!!
And it freezes the program.
I am no longer able to use Plex on this Mac - WHAT IS GOING ON?
The CMD-R only minimally works. I might be able to get one folder or images/videos, but I can’t back out of it.
I’m now getting this problem too, only in photo albums. It was working fine until recently - not exactly sure when it started. The root level of the photos works, but stepping into a level deeper throws up the “Something went wrong” error. Refreshing in a browser causes the content to appear. It’s doing this with with all albums, old and new.
Here is some more news. I use a Plex player on my iPad (6th generation with 17.5.1 iOS) and have very little issues until about a month ago. If I go into any one of my Plex servers to either view images or videos, I drill down until I get to the actual level of the image/video. If it is a series of images or videos at that level, I will have no issues but, as soon as I am done and back up JUST ONE LEVEL, Plex blows out. Then I have to go back in starting from the top login. My levels are determined by how deep I want to record image date.
An example will most likely be that the main library represents either a person(s) or a place. From there I will drill down into the next level which is a year. Next level is Month and final level will be the day if I have it. Older main folders are not likely to require drilling down that low, since images/videos were not cataloged that precise. Or an Event might just have one level below the main library level.
But, it doesn’t seem to matter how far down I have to go before backing up causes the crash.
One thing though. I have no issues as long as I don’t drill down into the final level of any library. I can back up anywhere with no issues as long as I don’t view the final level.
I have to say that is really unfortunate that someone who is working for Plex doesn’t see these issues in the forum and respond.
I think this is terrible. NO-ONE and I mean NO-ONE is helping us resolve this issue. I cannot even run the Plex Media Player on the Mac any longer. It keeps giving me that same error message “Something went wrong”. Is this the way that Plex people help their dedicated users? I have tried connecting via Web, I have tried accessing by logging into the Synology NAS systems and running the Plex Media Server App there, I can’t think of any else to do. WHERE IS OUR HELP!!!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
