I have been struggling with an issue where anyone new whom I share with cannot See the server in the listed server options.
Existing users where fine, but new users on new devices could not connect to the server at all.
After my previous thread debacle (See the linked thread at the bottom), I ended up doing the following:
Bought a new SSD
Reinstalled Ubuntu Server 18.04
Racked my server in a Datacenter
Mounted the media drives
Installed Plex Media Server on it
I did not migrate anything Server wise (sans the media itself) onto this new install.
I was able to tunnel in and claim the server to my user. At which time, all of my currently authorized devices can connect to and see the server.
So this is a brand new server install essentially, with no firewall to prevent connection issues.
I have not tampered with any of the network server settings.
After Re-adding all my shared users, the server fails to authorize any new device authorization attempts.
At this point, the issue seems to be tied to my account somewhere.
You’ve got serious problems in the metadata already.
2019-01-01 22:37:45,767 (7ffa137fe700) : DEBUG (agentservice:638) - Combining subtitles for media bundle at '/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Media/localhost/c/c907788bf0db56a8a6f958703c9c27e34c39631.bundle'
2019-01-01 22:37:45,767 (7ffa137fe700) : DEBUG (sandbox:19) - >>> No file found at path /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Media/localhost/c/c907788bf0db56a8a6f958703c9c27e34c39631.bundle/Contents/Subtitle Contributions/com.plexapp.agents.localmedia.xml
2019-01-01 22:37:45,767 (7ffa137fe700) : DEBUG (sandbox:19) - >>> No file found at path /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Media/localhost/c/c907788bf0db56a8a6f958703c9c27e34c39631.bundle/Contents/Subtitle Contributions/com.plexapp.agents.moviemania.xml
2019-01-01 22:37:45,767 (7ffa137fe700) : DEBUG (sandbox:19) - >>> No file found at path /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Media/localhost/c/c907788bf0db56a8a6f958703c9c27e34c39631.bundle/Contents/Subtitle Contributions/com.plexapp.agents.opensubtitles.xml
2019-01-01 22:37:45,768 (7ffa137fe700) : DEBUG (sandbox:19) - >>> No file found at path /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Media/localhost/c/c907788bf0db56a8a6f958703c9c27e34c39631.bundle/Contents/Subtitle Contributions/com.plexapp.agents.thetvdb.xml
2019-01-01 22:37:45,768 (7ffa137fe700) : DEBUG (sandbox:19) - >>> No file found at path /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Media/localhost/c/c907788bf0db56a8a6f958703c9c27e34c39631.bundle/Contents/Subtitle Contributions/com.plexapp.agents.plexthememusic.xml
2019-01-01 22:37:45,768 (7ffa137fe700) : DEBUG (sandbox:19) - >>> Creating combined XML file from {}
2019-01-01 22:37:45,768 (7ffa137fe700) : DEBUG (sandbox:19) - Combined XML data: <?xml version='1.0' encoding='utf8'?>
<Subtitles/>
This looks like an installation was migrated and permissions got all messed up or there is serious corruption from the onset.
As for the authentication. There ris NO way to see it from the singular server log.
With a stroke of luck, this headache has finally been resolved.
Steps taken:
Removed all authorized devices
Re-Claimed Server
Stopped Plex Service
Edited Preferences.xml with the following
Changed PubSubServer=“184.105.148.97” to PubSubServer=“184.105.148.98”
Started Plex Service
Re-added all users and everyone can connect fine now.
So I’m not sure why the pubsub02.spop.sjc.plex.bz Server kept messing up everything to do with my account but pubsub03.spop.sjc.plex.bz is working fine it seems.
Nevermind,
Looks like that was only a temporary fix. The issue has returned with a vengeance and changing the pubsub server does not seem to fix anything anymore. While a majority of devices can now connect fine, I still cannot connect from my home PC, nor can a couple of my friends connect.
Once again, this has nothing to do with the network, as my roommates can connect fine from the same home network. It is some authorization error somewhere.