I’m not using Docker.Not that I know of just PMS install on my NAS and using the Web Client.
Seems like I am having the same problem of a error if I sort by title and if I try anything else is seems ok for now. But this is frustrating.
Like I said, I’m ignorant on the NAS systems. It may still be worth seeing is there is any way to tell Plex to put it’s config on a single drive rather than the entire array, but that’s out of my scope of knowledge.
I have read many of the posts on several of the similar topics relating to unexpected error loading… bla. While I don’t know what error handling in the code will display this very general type message, I started thinking about the vast amount of directions which lead to the error and it pointed me in one direction. Of course, this worked for me, but several other things worked for many people and not me.
I had a hard drive go bad (Windows Server) and didn’t want to take the time to back up the database/files, etc., so I just slapped in a new HDD and rebuilt the system with Windows Server 2019. The external storage with the media is fine and I thought, just rebuild, plug in and not problem until I got this error and searched the posts.
I’m a Desktop Engineer, so my thought process might take several different paths than most. LOL. One of the biggest challenges for any Operating System or application Development Team is security. No matter what your flavor of OS you like to use or your favorite App… you experience problems and mostly due to security updates. Browsers are apps that are very security sensitive and get many updates/configuration changes due to security concerns. Most of the time users complain about the data harvesting bla bla bla…
Anyway, knowing that a Windows Server OS is very clamped down as far as the browser settings, I use Chrome to manage my Plex server. Assuming that Plex is more of a browser app than a web page, I figured it needs a little more freedom than internet/cloud based pages. Also, knowing that this is hosted locally and I’m not trying to attack myself, I went into the Chrome Settings for the local host page " [http://127.0.0.1:32400]", not the global Chrome settings, but particularly for this local site and opened the settings. I don’t know which one(s) in particular, but things like allowing media to play without prompting and so on. There are many configurations in any browser to prompt if certain pictures load, if certain videos or music loads. Basically, Chrome was not configured to give Plex Server permission to load the library.
So, basically, I opened up the security controls for the local Plex Server interface and it’s working now. Like I said, for me… Hope this long winded explanation helps at least one other person.
I am having the same problem for my TV only – also, so far using my mobile app works, but not from the browser on my computer.
Ubuntu 18.10
I can even delete TV and rebuild it. I have been a user for > 8 years and have never seen anything this bad before.
I moved to Emby lol.
Paid for a lifetime subscrption and got this error on first use of the software. Did I just waste my money on it?
You did brother,
You did. I still have yet to resolve this errors
I’ve been trying to solve it for ages.
Thanks for the fast reply - pity about it. Whilst I get the error on my PC the library has loaded into my AppleTV menu so at least that’s half good.
I’m having the same problems on a fresh, from scratch Windows 10 install and newest download of Plex. All the movie files are on one drive. I’m not using Decker or Unraid or any raid software, nothing unusual at all.
So, I’ve read through this series of posts, and I haven’t found anyone with my particular set of circumstances - at least of those who provided any details.
Mine is a brand new installation. I have no unRaid or anything else, just a massive external hard drive that is working just fine, thanks. I pointed PlexMS at the folder of music and told it to create a new library. It whirred at that for a while. And then came to this error. So my database is living on my local machine’s hard drive. For what it’s worth, I’m on a MacOS box running the latest 10.14.6.
Not really sure where to go with this at this point. There’s no additional details in the error message. What is going on here? What troubleshooting steps should I be taking that I’m not because I’ve never used this software before?
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
