Server Version#:4.141.0
Player Version#:All players, windows, I O/S and remote 3-4 revs back windows client
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>
On fresh boot server now runs for maybe 45 minutes after which it simply stalls on player (local network) I hop onto server and bring up plex browser interface and player continues by reversing a minute or two after which i get between 15-45 minutes again of clear/normal use. Windows 10 platform, Nvidia 8GB graphics, no updates for past year no changes other than Plex itself. External 22TB drive handles only Plex data no changes in past year.
Is your computer going to sleep? There have been reports.
def not, not guessing either as I was a VM network design engineer for 37 years and know my hardware lol. Yesterday i dumped all my cache, cookies, passwords and rebooted plex after that it ran for hours no issue for me… Any way of assigning plex to use a browser away from Edge? i would like to try different thinner browsers if possible.
If you use the “Open Plex” command from the task tray icon, it will simply invoke the default web browser of this Windows user and open the URL http://127.0.0.1:32400/web
You are free to start any browser you want and point it to https://app.plex.tv
Though expect things to break down if you use a browser that is intentionally restricting the functionality of scripts etc. The Plex web app is a real app that is running directly in your browser. To do that, it needs a lot of browser features that you otherwise can restrict/block/disable on regular websites without losing too much functionality.
Update, So i left my default browser running and see that when the plex server goes offline (attached picture hopefully) all i need to do is hit refresh on the browser to solve the offline Plex issue. Does this shine any more light on the issue?
thanks
“Startup maintenance tasks” are only running after an update of the plex server software.
If you have set your server to install updates automatically, you will sometimes encounter this message. i.e. if you leave the web app open while the server is installing a software update on its own.
Though this will probably only happen on machines which are quite slow, or have massive media collections on them.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
