Server Version#: 1.24.0.4897
Player Version#: 4.62.1
I have a problem recently where Plex server will stop responding, acting as if it has crashed. It is not accessible via web browser, but the Plex logo is still visible in the Mac menu bar. If I click “Open Plex” in the menu bar, it opens a browser but it doesn’t load anything.
The only option is to Quit Plex via the menu bar, and then restart the server. Once I restart, everything is fine again.
I’m including logs that were grabbed immediately after a quit and restart of Plex after this crash occurred. Any help would be greatly appreciated. Thank you (5.2 MB)
Having the same problem here since updating to Big Sur a few weeks ago. The web Server crashes every day, usually while the Mac is asleep and overnight, quitting from the menu bar and restarting always fixes the problem and playback not affected.
Prior to Big Sur Plex Server has run fine on this machine for a few years - no crashes at all and the machine sleeps regularly.
Mac Pro 2013 (Intel) - 64Gb RAM
Server: 1.24.3.5033-757abe6b4
Could you get debug server logs after a crash. Make sure you have debug logging enabled beforehand on the server and server restarted after that if it was disabled before
and also look for crash reports within the paths
~/Library/Application Support/Plex Media Server/Crash Reports/
~/Library/Logs/CrashReporter/
~/Library/Logs/DiagnosticReports/
Well this is disappointing… I provided two sets of logs earlier in this thread, and got no responses at all. I’ve since abandoned my Mac, and set up my Plex server on an Ubuntu machine, and have had no problems at all. But as soon as other people report the same problem, you ask for their logs.
Again, I’ll repeat, I provided two sets of logs when I initially created this thread.
Obviously I did not come across this forum thread prior to today. There is limited number of hours and forum threads can get missed - bumps help in such cases.
I did see your post today but being an August set of diagnostics and a lot of newer versions and updates happened in the mean time, I thought that issue is probably no longer current