Mac server just spins on launch

I paid for plex plus,downloaded the mac media server and double clicked. I get a browser window with a spinner that never stops. What are my next steps? Mac powerbook with 8 megs of memory running 10.15.7. I wasn’t hoping to become a full blown sys admin just to watch OTA tv outside my home. The browser shows: http://127.0.0.1:32400/web/index.html#!/client-setup. Do I need to enable something for the app to talk to Safari?

Here’s the console output:
default 21:33:09.749638-0800 runningboardd Acquiring assertion targeting executable<Plex Media Server(501)> from originator [daemon<com.apple.coreservices.launchservicesd>:256] with description <RBSAssertionDescriptor; frontmost:1746; ID: 502-256-399; target: 1746> attributes = {
<RBSDomainAttribute: 0x7fad1e736f40; domain: com.apple.launchservicesd; name: RoleUserInteractiveFocal; sourceEnvironment: 0x0>;
}
default 21:33:09.750499-0800 runningboardd Assertion 502-256-399 (target:executable<Plex Media Server(501)>) will be created as active
default 21:33:09.773102-0800 runningboardd [executable<Plex Media Server(501)>:1746] Ignoring jetsam update because this process is not memory-managed
default 21:33:09.774545-0800 runningboardd Finished acquiring assertion 502-256-399 (target:executable<Plex Media Server(501)>)
default 21:33:09.780627-0800 runningboardd [executable<Plex Media Server(501)>:1746] Set darwin role to: UserInteractiveFocal
default 21:33:09.782639-0800 runningboardd [executable<Plex Media Server(501)>:1746] Ignoring GPU update because this process is not GPU managed
default 21:33:09.828237-0800 Plex Media Server Opening URL with application
default 21:33:09.859133-0800 Plex Media Server _LSLaunch(’’)
default 21:33:09.863629-0800 Plex Media Server LAUNCHING:0x0-0xa20a2 Safari foreground=1 bringForward=1 seed=191 userActivityCount=0
default 21:33:09.898060-0800 Plex Media Server OSStatus _LSLaunch(LSContext *, FSNode *, LSLaunchFlags, void *, CFArrayRef, const AppleEvent *, const AEDescList *, CFArrayRef, CFDictionaryRef, LSBundleID, const audit_token_t *, const _LSOpen2Options *, ProcessSerialNumber *, Boolean *, NSError **): launching ‘’ result=0
default 21:33:10.500276-0800 runningboardd Invalidating assertion 502-256-399 (target:executable<Plex Media Server(501)>) from originator 256
default 21:33:10.614403-0800 runningboardd [executable<Plex Media Server(501)>:1746] Ignoring jetsam update because this process is not memory-managed
default 21:33:10.615983-0800 runningboardd [executable<Plex Media Server(501)>:1746] Set darwin role to: UserInteractive
default 21:33:10.616168-0800 runningboardd [executable<Plex Media Server(501)>:1746] Ignoring GPU update because this process is not GPU managed
default 21:33:21.240310-0800 Plex Media Server LSExceptions shared instance invalidated for timeout.
default 21:33:25.669051-0800 mDNSResponder [R4357] DNSServiceQueryRecord(1D000, 0, , Addr) START PID[1746](Plex Media Serv)
default 21:33:25.670550-0800 mDNSResponder [R4358] DNSServiceQueryRecord(1D000, 0, , AAAA) START PID[1746](Plex Media Serv)
default 21:33:25.673717-0800 mDNSResponder [R4357] DNSServiceQueryRecord(1D000, 0, , Addr) STOP PID[1746](Plex Media Serv)
default 21:33:25.673993-0800 mDNSResponder [R4358] DNSServiceQueryRecord(1D000, 0, , AAAA) STOP PID[1746](Plex Media Serv)
default 21:33:25.820923-0800 symptomsd defusing ticker tickerFatal having seen progress by flow for com.plexapp.plexmediaserver, rxbytes 4709 duration 86.113 seconds started at time: Thu Jan 20 21:31:59 2022

Do you get the same issue using a different browser or after disabling browser add-ons / blockers?

Yep, Chrome does the same thing.

Any “security” or content/add blocking apps that could interfere with Plex properly connecting?
Would you mind sharing your server logs to see if there’s any server-side issues?

It started working. I rebooted, logged back into plex and re-downloaded the media server. Something in that fixed things. I’m running on Chrome. Not sure if Safari works or not. But as long as I can get it going with Chrome, I’m happy. Thanks for your advice.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.