Don’t forward UDP packets from the outside. Plex remote access only uses TCP.
I hope the “Any” means “any external IP address”, and not “any external port”?
1 Like
for what it’s worth, it seems like it’s been happening for a couple weeks now? This previous thread (and the other linked thread in here) all seem to be similar. for my part I can confirm reverting back to the old version was a placebo - after about a week it shut itself down out of nowhere again as well. Granted, the reasons why it seems to be happening are varying, but the commonality is that multiple mac plex pass users are all, in the space of a few weeks, after updating, having a server that previously never shut itself down before, doing so repeatedly
I updated to the new version (again) and it’s doing the same thing (again) - Is this simply a matter of going back to an even older version in the meantime?
@BigWheel : Any update?
Just to add to the convo, I am seeing this same behavior. PMS just shuts down randomly.
macOS 10.13.6
Plex Version - Version 1.32.3.7192
1 Like
Sorry no update. Thanks for chiming in @binaryecho It is interesting you are both on 10.13.6.
Something of note. I found out the person that was watching my Plex each time it shut off has Verizon as their provider.
Weird part is, he watched “movie x” and it kept shutting down my plex at exactly 1hr 17m. We tested it multiple times. I ran a database check to see if anything was corrupt. Nothing. Deleted the “movie x”.
He watched 2 movies, uninterrupted, watched “movie y”, shut down my plex at 45 minutes each time. A mutual friend went back to his house, has Comcast as a provider. Watch “movie y” beginning to end, nothing happened to plex.
Same User that watched movie x and y (and shut everything down), went out of town this weekend. Logged in as himself, watched my plex, and my plex never shut down. Our conclusion is that it has to be something with that User’s home network or router. But that still doesn’t explain how their remote connection can shut down my application.
I’m not sure if you changed your port forwarding to not use UDP. as mentioned above remote access uses TCP.
You can ask your friend with Verizon to disable Home Network Protection in their verizon router to see if that changed anything
Has anyone checked if there are any .ips files created by MacOS in here round the time of the exits - just to eliminate the OS forcing the Plex Media Server app to exit:
Use the Finder’s Go menu, select Go To Folder… then enter the following in the dialog box that pops up:
~/Library/Logs/DiagnosticReports/
Hi @sa2000 : I just did this and there are 13 files in here. It’s all greek to me 
FYI: When I logged into my machine today, PMS was already shut off. I know it was on last night cause we were watching movies from it, but I do not see a file for anything in the last 24 hours in this folder
Here’s what’s in there
Yes I have done this already.
I’m running into this as well, more often when starting a new stream, but only periodically. A few times the server has crashed with no interaction. The server is segfaulting with a bad address call:
"exception" : {"codes":"0x0000000000000001, 0x0000000000000028","rawCodes":[1,40],"type":"EXC_BAD_ACCESS","signal":"SIGSEGV","subtype":"KERN_INVALID_ADDRESS at 0x0000000000000028"},
"termination" : {"flags":0,"code":11,"namespace":"SIGNAL","indicator":"Segmentation fault: 11","byProc":"exc handler","byPid":1793},
"vmregioninfo" : "0x28 is not in any region. Bytes before following region: 140737487237080\n REGION TYPE START - END [ VSIZE] PRT\/MAX SHRMOD REGION DETAIL\n UNUSED SPACE AT START\n---> \n shared memory 7fffffeef000-7fffffef0000 [ 4K] r-x\/r-x SM=SHM ",
This is on Mac OS 13.2.1 on server Version 1.32.4.7195-7c8f9d3b6, on an Intel Macmini8,1.
I’ve been experiencing the same issue for a while, and so far none of my troubleshooting is bringing me closer to a solution! I’m the only user in my account, so everything is streamed over my wifi (remote access is disabled). I figured it may have been a recently added file that is corrupt, so I’ve moved all my recent stuff to a separate hard-drive, refreshed the directories, but it’s still happening. Usually after 2-3 hours, Plex will just shut down.
Archive.zip (27.5 KB)
I’m on MacOS Venture V13.0
Plex version 1.32.4.7195
I do have a Plugin that I can’t remove. ExportTools V2.0.0.14, when I try to remove it I get this error “This plugin could not be uninstalled.” Could that be the problem?
Shut down the server
then delete the plugin’s *.bundle folder manually.
https://support.plex.tv/articles/201106098-how-do-i-find-the-plug-ins-folder/
Thanks, OttoKerner - I was able to remove the plugin, Plex is back up and running so I’ll come back if it still shuts down unexpectedly.
Intriguing. Thank you
I looked at the original server logs from the 14th June - and whilst there were signal 0 shutdown - i do not think these were the times of the crashes
So for the 14th - I can see
Launch Jun 14, 2023 13:09:21 - PMS process exited at Jun 14, 2023 13:49:29
Playback at the time on LG OLED55C8PUA
Launch Jun 14, 2023 15:00:22 - PMS process exited at Jun 14, 2023 15:12:44
There was a transcode in progress
Launch Jun 14, 2023 15:44:34 - PMS process exited at Jun 14, 2023 18:24:14
As per the other two cases there was a transcode in progress
Launch Jun 14, 2023 19:34:56 - PMS was shutdown at Jun 14, 2023 19:39:15.
It was idle
Launch Jun 14, 2023 19:43:34 - PMS was shutdown at Jun 14, 2023 19:45:41.
It was idle
Launch at launch Jun 14, 2023 20:08:51
Logs zip captured at Jun 14, 2023 20:10:11
What is intriguing is that the ips files you gave me show transcoder process segfault crashes at the 3 times when the PMS process exited ! I will refer this to the development team and thanks for the logs and ips files
@sa2000 : Thank you for taking a look!
At this point is there anything I can or should do, or look into? Or is it out of my hands at this point?
UPDATE: Plex was shut off again when I checked this morning. This is the report from today
Plex Transcoder_2023-06-22-004845_Chuns-iMac.crash.zip (15.0 KB)
Well - suggest the following
- Upgrade to the latest beta in case the bug got fixed in that release
- Avoid Transcoder crashes as the bug appears to be that the parent process exits when that happens
For the second, suggest:
- identify the media files involved,
- see if a small sample from the media file brings in a transcoder crash
- submit to me logs + ips file + smallest media file that brings in a transcoder crash
- avoid playing that media file until the issue is resolved
The 3 transcoder processes that crashed on the 14th were for:
Transcoder crash at 13:49:29
Media File: /Users/chunlee/Movies/Guy.Ritchies.The.Covenant.2023.mkv
Transcoder crash at 15:12:44
Media File: /Users/chunlee/Movies/Guy.Ritchies.The.Covenant.2023.mkv
Transcoder crash at 18:24:14
Media File /Users/chunlee/Movies/Guy.Ritchies.The.Covenant.2023.mkv
So it looks like the same media file transcode each time - please let me have a sample from it to see if we can reproduce the transcoder segfault
I updated my last post above - same media file in each case
I will now look at the new diagnostics from the 21st / 22nd June
sorry - i would need corresponding sets of diagnostics - the ips files from the ~/Library/Logs/DiagnosticReports/ plus the debug server logs. All I can tell from the ips file is that the transcoder had a segfault at 2023-06-22 00:48:41. Don’t know which media file it was
What you included in the archive.zip are the latest server log files that were created when the server was relaunched after the crash. The logs cover Jun 21, 2023 12:29:10 onwards. The crash was just before this time !
Please copy out and zip all log files when zipping manually logs from ~/Library/Logs/Plex Media Server/ - alternatively after the crash, restart plex media server and use Plex Web Troubleshooting menu to download the logs - that will ensure logs leading up to the crash are in the zip
and in case your problem is similar to the other one I investigated above, please also copy out and zip files from ~/Library/Logs/DiagnosticReports/
