I have now disabled all auto-scanning again. The page refreshes way too much. The problem is there’s no downgrade path to remedy this because it’s the Plex web version hosted on Plex servers.
I know about using the local plex web but that’s not really a solution.
Can you confirm that you are referring to your Server’s Library settings? You’ve disabled the first “Scan my library automatically” setting?
After disabling this or another setting, are you no longer observing the issue? If so, can you reproduce the issue by manually starting a library scan?
I personally have not observed this issue so I’m trying to bring as much data to the engineers as possible.
Just want to comment that I have had to do this daily so chrome users can view my library in a stable way. Unchecking “Scan my library automatically” is the only way for it to be stable. Having to manually scan my libraries is a huge pain. Any auto scan causes unbearable refresh glitches.
Are you saying that manually scanning a library does or does not cause the issue to be observed? Can you tell me what your host OS is? Also, what other Server - Library settings do you have enabled? What tasks are being ran when media is added? While you’re observing the issue please capture your PMS logs and share here or DM me please.
Do you need more information about UI refreshes during library scans?
If I open the browser console log when a scan is in progress and UI is being rapidly refreshed, these messages are repeated in the logs every few seconds:
26920-6920-269992da4056366f8ea0-plex-4.125.1-c17e55e.js:2 [Commands] Executing testServerConnection
6920-6920-269992da4056366f8ea0-plex-4.125.1-c17e55e.js:2 [Connections] Testing connection for <Server Name 1> at https://192-168-1-85.redacted.plex.direct:32400/media/providers
6920-6920-269992da4056366f8ea0-plex-4.125.1-c17e55e.js:2 [Connections] Testing connection for <Server Name 1> at https://redacted.redacted.plex.direct:32400/media/providers
6920-6920-269992da4056366f8ea0-plex-4.125.1-c17e55e.js:2 [Connections] <Server Name 1> connected at https://redacted.redacted.plex.direct:32400/media/providers
6920-6920-269992da4056366f8ea0-plex-4.125.1-c17e55e.js:2 [Connections] Active connection to <Server Name 1> is https://redacted.redacted.plex.direct:32400
6920-6920-269992da4056366f8ea0-plex-4.125.1-c17e55e.js:2 [Servers] Found all servers = <Server Name 1>, <Server Name 2>, <Server Name 3>, <Server Name 4>, plex.tv
6920-6920-269992da4056366f8ea0-plex-4.125.1-c17e55e.js:2 [Connections] <Server Name 1> connected at https://192-168-1-85.redacted.plex.direct:32400/media/providers
6920-6920-269992da4056366f8ea0-plex-4.125.1-c17e55e.js:2 [Connections] Active connection to <Server Name 1> is https://192-168-1-85.redacted.plex.direct:32400
6920-6920-269992da4056366f8ea0-plex-4.125.1-c17e55e.js:2 [Connections] Testing all 2 connection(s) for <Server Name 1>
6920-6920-269992da4056366f8ea0-plex-4.125.1-c17e55e.js:2 [Servers] Found all servers = <Server Name 1>, <Server Name 2>, <Server Name 3>, <Server Name 4>, plex.tv
It seems that it is constantly switching between the internal and external plex.direct hostnames.
Occasionally, an additional yellow warning is included alongside these; I’m not sure if it’s relevant.
[Companion] No companion found
If I hang out on the server settings page, I can see that on the ‘Remote Access’ sidebar item which used to always show a green checkbox on account of my port being correctly forwarded will toggle red, and then quickly switch back to green. Once I started digging into it, wouldn’t always switch back to green on it’s own; sometimes I had to click the ‘Check’ button for it to go green. I also noticed at one point when a green check mark was showing, it also said I had an unknown local and public IP. This is very suspect and I’m beginning to wonder if whatever backend provides services for plex.direct is having trouble or received a deployment that could be contributing to this problem.
Interesting observation. I have been getting these messages randomly before on my Discord Notifications, but I have not gotten them since I turned off all auto-scanning.
Tautulli : The Plex Media Server remote access is down. (Plex remote access port mapping unknown)
Tautulli : The Plex Media Server remote access is back up.
From what I understand, the Tautulli developer said whenever remote access turns to red from green it will give this error. It will usually take a minute before the next message “remote access is back up” pops up, but that may just be Tautulli’s polling interval (1 minute).
It seems to be more than a coincidence that these messages have disappeared after turning off auto-scanning. So if other users are experiencing this as well, this has to be related.
Would the mods mind splitting this thread into a new topic “Plex Web UI Constantly Refreshes During Server Library Scanning”?
I have rolled the plex desktop for windows back to v1.86.1.4076-a3ab948d because in the v1.88
I was still having the refresh bug happening but a new problem was introduced, that if it done a refresh/update whilst watching a show the control overlays would disappear, instead of being dumped back to the menu with an error message
all problems don’t exist on v1.86
It looks like Plex Web Version 4.126.1 which just came out, has solved this problem. It’s not mentioned in the notes but I’m no longer getting refreshes and I’ve rescanned 5 times already.
Just had the playback error on LG WebOS TV App. The problem stopped after I rolled back my server, however, it seems to have started again. This error keeps repeating in the console
[Req#27d0ff/Transcode/gkrlt02p9fb24hamqbt54whf] Transcode runner appears to have died.
You’re referring to a completely different issue separate from the title of this thread. This is for UI refreshes, not for the error that interrupted playback.
Any update on this issue. I run playback mainly on the Nvidia Shield and is almost unusable. I don’t want or consider neutering features of my server as a viable solution.
@snoopy_123 The issue in this thread relates to Web, not the Shield. Not really sure what the issue you’re having but if it’s on the Shield it’s something else. Please create a separate post (if you haven’t already) with details on your issue and please include logs.
I am having this issue in the web interface home screen, on both Windows and Mac, Chrome and Firefox. Completely unusable from a browser.
My server is Version 1.40.2.8395, running on Synology (this is showing as the “up to date” version).
@Random_Pants can you please state if you are you using the bundled web app (SynologyIP:32400) or app.plex.tv? Can you also provide the web app version you are seeing the issue? Please provide the version number.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
