Plex Web App Home tab spinning, watchlist and Discover yellow triangle

Server Version#: 1.40.4.8840-7008840
Player Version#: 4.132.2

Running Plex server on Synology NAS (7.2.1-69057)

Accessing the web GUI from my computer I am seeing a spinning circle on the Home tab and the Watchlist and Discover tabs have the yellow triangle and say “Unexpected error, go to the forums”.

I have no other issues as I can still access all media from this computer, my TV, and remote streaming. All other devices have these tabs available unless viewing the web GUI. Nothing has changed on the network.

I have tested this on my windows computer with firefox, chrome, and edge as well as safari and firefox on iOS and had the same issues.

Logs.zip (4.3 MB)

1 Like

Exact same here

@iomalley

I see the IPv6 connection terminate (browser closed it)

Your Syno is running primarily on IPv4 , not IPv6

Does the same thing happen when you open it with IPv4 ?
http://192.168.1.151:32400/web

Yeah same result opening that way.

Same for me too! Also, on the latest Synology version.

UPDATE: Installing version 1.41.5.9522 manually and updating from the latest online version which is currently 1.40.4.8840-72008840 fixes my issue.

1 Like

Yes same here - am running on Windows 7 - has been perfect for years but tonight shows Watchlist and Discover in Yellow Triangle - also searching on the server portal very slow - BUT clients on iMac and Android do show Watchlist & Discover as healthy and search is fine - so server basically seems to be functioning OK but it’s the web portal view on the Win 7 machine has the Yellow triangle probs. Any ideas? And yes I know Win 7 is ended but mine has just been clugging along fine.. Also where to find last suppoerted version of the server?

Also can add items to the Watchlist and they become visible from the clients.

@iomalley & all

Please look at Settings - server - Network - Show Advanced

If you’re using IPv4 for your LAN (in any way), even if a dual stack IPv6, turn off
the “Enable Server support for IPv6” option & SAVE

I am seeing

Mar 19, 2025 15:37:27.389 [140681435913016] DEBUG - CERT: incomplete TLS handshake from [::ffff:192.168.1.73]:5430: sslv3 alert certificate unknown (SSL routines)
Mar 19, 2025 15:37:27.400 [140681433803576] DEBUG - CERT: incomplete TLS handshake from [::ffff:192.168.1.73]:5431: sslv3 alert certificate unknown (SSL routines)
Mar 19, 2025 15:37:27.642 [140681433803576] DEBUG - CERT: incomplete TLS handshake from [::ffff:192.168.1.73]:5437: sslv3 alert certificate unknown (SSL routines)
Mar 19, 2025 15:37:30.872 [140681435913016] DEBUG - CERT: incomplete TLS handshake from [::ffff:192.168.1.73]:5444: sslv3 alert certificate unknown (SSL routines)
Mar 19, 2025 15:37:30.887 [140681435913016] DEBUG - CERT: incomplete TLS handshake from [::ffff:192.168.1.73]:5445: sslv3 alert certificate unknown (SSL routines)
Mar 19, 2025 15:37:31.127 [140681433803576] DEBUG - CERT: incomplete TLS handshake from [::ffff:192.168.1.73]:5448: sslv3 alert certificate unknown (SSL routines)
Mar 19, 2025 15:37:31.207 [140681433803576] DEBUG - Request: [192.168.1.73:5450 (Subnet)] GET / (12 live) #24c TLS GZIP Signed-in
Mar 19, 2025 15:37:31.208 [140681433803576] DEBUG - Completed: [192.168.1.73:5450] 401 GET / (12 live) #24c TLS GZIP 0ms 435 bytes
Mar 19, 2025 15:37:31.439 [140681394883384] DEBUG - Request: [192.168.1.73:5458 (Subnet)] GET /web/index.html (12 live) #24d TLS GZIP Signed-in
Mar 19, 2025 15:37:31.439 [140681394883384] DEBUG - [Req#24d] Final path: "/volume1/@appstore/PlexMediaServer/Resources/Plug-ins-1f7662b1a/WebClient.bundle/Contents/Resources/index.html"
Mar 19, 2025 15:37:31.439 [140681394883384] DEBUG - Content-Length of /volume1/@appstore/PlexMediaServer/Resources/Plug-ins-1f7662b1a/WebClient.bundle/Contents/Resources/index.html is 13491 (of total: 13491).
Mar 19, 2025 15:37:31.440 [140681433803576] DEBUG - Completed: [192.168.1.73:5458] 200 GET /web/index.html (12 live) #24d TLS GZIP 0ms 13491 bytes (pipelined: 1)

Turning the option off will tell me if the problem is on the IPv6 side or not.

Turned off support for IPv6, saved, restarted the server, cleared the browser caches and the issue remains.

I did this and makes no difference - also forgot to mention that a search for media does not return any hits.
Surely if this issue has arrived for me on a win 7 server and the above on Synology and it just appeared recently - does it not indicate a change at the Plex end??
Also on my Win 7 server if I use the web access to plex all is fine - watchlist is visable etc and serching works fine - so issue is with the: 127.0.0.1:32400 access built into the server app.

@gregn_aus

When you search the logs, do you find any messages about corruption or malformed ?

Those are the most common indicators when search fails (damaged DB)

Got the same this morning, running on Synology NAS.
Updated Plex from version PlexMediaServer-1.41.0.8994. to PlexMediaServer-1.41.1.9057

This resolved the issue for me

No nothing an database searches return correct and sane results from other clients - Mac, Android etc.
I think I am on the last release available for Windows 7. Can you confirm it’s number etc..?
thanks

The last server version to support Windows 7 was 1.31.3.6868 (from almost exactly 2 years ago):

Hi there !

Could you please help me with my Plex Media Server which keep crashing (stopped manually) as soon I as I launch the Plex web app.

Already tried to reboot, uninstall then re install Plex Media Server with no change at all.

NAS Synology DS1019+
DSM 7.2.2-72806 Update 3
PlexMediaServer-1.41.5.9522–72009522

Attached is my Logs files

Thanks for any help !
Logs.zip (689.8 KB)

@m96fg

You turned off DEBUG logging.

It’s impossible to figure out what’s happening with only a 4KB log file.

You will need to enable DEBUG logging again.

  1. Install the Synology Text Editor (Package Center)
  2. With Plex stopped
  3. Using FileStation,
  4. Navigate - PlexMediaServer/AppData/Plex Media Server
  5. Right-click “Preferences.xml” → Open with Text Editor
  6. Line 2 will be all the preferences.
  7. Look for a logDebug="0", If you have that, change the 01 and save/exit
  8. If you don’t have it, go to the end of the line.
  9. Before the closing />, add logDebug="1". It will look like this.

  1. SAVE the file and exit
  2. Start PMS
  3. Now when it fails, you’ll have DEBUG logging which will give us a lot more info about where it’s failing.

Done !

Not sure if that change anything in the Logs.
Thanks for your precious help.

Logs(2).zip (756.1 KB)

I have the same issues with the home tab not loading.
On my Synology package store there is nothing to update, and trying to install it manually through an spk file gives the error of unsupported package?
How do i get this working?

@illuvattarr

Make certain your’re getting the right DSM package (DSM 7 != DSM 7.2.2+)

Synology changed the package internals at DSM 7.2.2.
This forced us to create the DSM72.spk version.

@m96fg

Do you have the previous version SPK file ?

Can you revert to that package and see if the problem goes away?

I ask because there are no obvious errors (thank you for the DEBUG logs… Infnitely better)