Not sure if its because I added my music library, or just updated to the new PMS version for my Synology NAS but in the web interface all I get now is the following message when I load plex into my browser:
There was an unexpected error loading the dashboard
Please visit our forums if you continue to experience problems
It would depend on how you are trying to access Plex Web. See Opening Plex Web App.
I had an issue with localhost IP (127.0.0.1) access to PlexWeb because of changes to the router/local network and found it easiest to just uninstall and reinstall PMS and let Plex find the new network info. If you do not mess with the AppData it will keep your library info.
I have no issues connecting to PMS nor have I changed any routing information. It just will not load my Home dashboard I keep getting that error message. I can go to the individual categories tv, movies etc.
Only 2 things have happened since this issue began, I added my music library (very large library) and I updated PMS for Synology NAS. Both happened at the same time so Im not sure which caused this
There are several possible causes - most common are database needing optimization or some database corruption
Best action is to enable debug logging on the server and restart the server and on next error, provide full screenshot and attach the Plex Medua Server.log
@wexxwuther said:
Not sure if this is what you want but I hope so
Thanks in advance
No - that is not what I wanted. This is a Plex Web App log.
I wanted the server log file after enabling debug logging for it and restarting the server and then trying to get the problem and then finding the Plex Media Server.log file
The home dashboard searches different areas and any issue with database not being optimized could affect it and not respond within the 15 second timeout set by Plex Web. Also database corruptions would stop such requests from working
@wexxwuther said:
I have deselected this option and Im still getting the same error. Still trying to figure out how to access the PMS log in the root directory
You need to get the server logs outlined in earlier posts so that one can see what the issue is. It may be just that you need to optimize the library. Or maybe there is database corruption