After updating the PMS on one laptop last night, it wouldn’t stay open. It won’t persist in the toolbar or open directly from Applications. I’ve uninstalled it and reinstalled it multiple times, including using instructions to do a clean reinstall and a total uninstall through Terminal. Any help would be appreciated. Should I roll it back? Should I Time Machine my way back to the old version of the PMS? I’ve been using this for years on two machines without issue.
Awkwardly, I just purchased the lifetime Plex Pass earlier this month. :-/
OS X v 10.14.1 on a MBP with plenty of space and RAM
Thanks for at least letting me know I’m not alone with the problem. Unfortunately, I did such a complete uninstall that I think I’ve lost my previous versions of the PMS download. I found a very very old version (for Lion) and downloaded it—it stayed open but wouldn’t build a library even from scratch. Any idea where to get the previous version? Is doing a time machine roll back to a previous app a dumb thing?
I have the same problem! I have tried to install and reinstall the latest version on two different Macs. Its the same problem with both. When started up it crashes 3 seconds later. What to do?!
I’m not sure how to get the logs. If you tell me how, I’m happy to provide them. I might have deleted them along with everything else in my scorched-earth approach to a clean reinstall.
I have had the same issue for all releases after 1.13.9.5456. Install completes ok, but starting the app it closes after ~15 seconds of running. Rolling back to the above version works but would be nice to get working again. Am running Mac Mini + OSX 10.12.6
Same issue for me here. I have saved a copy of both a 1.13 release that works, as well as the current download for 1.14.0, so I can try anything that would help troubleshoot the issue - just let me know what I can do to help!
Ok, scratch that. Managed to get it working, thanks to the solution posted in this thread: PMS 1.14.0.5470 Crashing on start on Mojave Apparently the problem arrises when there are multiple IP’s on the loopback interface, and removing the additional loopback IP’s fixed the issue. In my case, it would appear that the additional IP’s were added by OpenVPN, but your case may be different.