[BUG] Purchased lifetime plex pass, now all servers are showing offline / cannot secure connect bug

Disclaimer: I am not tech savvy or literate. Apologies in advance if this is a common issue or my formatting is bad.

Description:

I’ve been loving Plex over the last few weeks, so last night I sprung for the lifetime plex pass for all the premium features. Immediately upon re-logging in to plex on the web app (firefox) to check out said premium features, both servers I have access to (my personal and a friend’s) errored out, are now listed as “offline”. I can’t access on the web app via firefox (hits me with the secure connection error, I’ve confirmed my friend’s server should be visible on not secure connections and is visible to him) or the desktop app or via mobile plex app or prologue (all apps show the red exclamation mark and “offline”). I have confirmed the Synology Nas itself is online (I can connect to it remotely via quickconnect). I have been accessing plex remotely for the last two weeks with no issues, and was actively streaming media remotely on the same private connection wifi with no issues until the moment I purchased the plex pass.

My server is also showing offline to authorized users.

Server Version: v.1.41.3.9314-a0bfb8370 Manually Installed via Docker on Synology Nas DSM version 7.2.2. Router is an ATT supplied generic fiber goober.

App Versions: v.1.105.2.269-12a32491 on Asus whateverbook windows 10. Current Plex and Prologue apps on IOS iphone SE, no idea how to find the version#.

Steps to Reproduce:

  1. Log on to plex on literally any device, app, or wifi.

Expected:
Server should be online

Actual:
Server is listed as offline on apps and “Cannot establish secure connection” on firefox web app.

What I’ve done:

Updated the nas DSM to 7.22, manually installed current Plex Media Server, restarted the nas. Switched to my mobile hotspot (same result). In the desktop app (PC) in settings > advanced I’ve confirmed Allow Fallback to Insecure Connections is set to Always (it was by default).

I don’t know what logs to upload, if someone can point me in the right direction I’ll be happy to upload.

Thanks in advance.

Looking at your forum account email, I see:

  1. Server named ‘Mr Toad****’ as your server
  2. Server named ‘Several****’’ as a server shared to you.

Are these correct ?

When upgrading, it is best to restart the apps.
They don’t know you have a PlexPass until they resync with plex.tv (which happens at startup only :frowning: )

1 Like

Ahoy ChuckPa! Thanks for the response. I’ve read some of your replies on other posts and you seem to be the best person to talk with about this.

Yes 1 & 2 is correct. SeveralHead reset his app and turned off his VPN and his server is now visible! His server is on his tower (not a synology nas) so restarting Plex Media Server was a simple process.

I updated the Plex app on my DSM, still no dice. What should my next step be? Forgive me if this should be a simple answer.

EDIT I tried to access Plex Media Server app via quickconnect to see if there’s an easy way to close / restart. It gives me an error “Sorry, this package cannot be accessed when connected via QuickConnect”

@BobbyThomson

Sorry for the delay (Dr appt).

Instead of using QuickConnect, which routes you out through Synology’s server in Taiwan, use the LAN IP of the server directly http://LAN.IP.of.Syno:32400/web

That failing, Open an incognito window and try it again. It might think it’s unclaimed.

Let me know what you get

1 Like

No worries on the delay. Unfortunately I’ll be offsite until after newyears, but I’ll give this a try then and report back. Thanks for the help so far!

Let me know when you’re ready.

Thought: you can uninstall + reinstall with Claim Token (option 2 in the menu) to force it to reclaim while remote

1 Like

Let’s try the uninstall-reinstall as I’m an impatient person.

For the uninstall, DSM gives me the following options:

  1. Uninstall only. Keep all existing files for future re-installation.
  2. Sign out and unclaim this server. Keep all existing files for future re-installation.
  3. Erase all of Plex Media Server from this system. (Not Recoverable).

I’m assuming 2nd option is what I want for the Reclaim Token? Please advise.

EDIT I pulled the trigger on option 2 to unclaim. Manual Reinstalled via Quickconnect Package Center (PlexMediaServer-1.41.3.9314-a0bfb8370-x86_64_DSM72).

Upon reinstallation I took option 2, generated the claim token, copypaste, via the app in DSM it said “Server successfully claimed by BobbyThomson” (me). Logged back in to plex.tv, wheel of death, server still offline.

Any other suggestions?

Make a ZIP of the “Logs” directory and attach please.

I need to go deep sea fishing :tropical_fish:

1 Like

Heheh sorry about that.

To confirm, you’re asking for the DSM logs I can access via the Log Manager on synology? Not sure how to access any Plex-specific logs.

EDIT - I did the plex pass upgrade around 7-730PM EST yesterday, 12/29/2024

See attached >>>
SynologyLogs.zip (15.2 KB)

The Plex logs:

  • Login to DSM
  • Stop Plex Media Server.
  • Using File Station, navigate to the Plex Data Folder (/PlexMediaServer/AppData/Plex Media Server)
  • Right click on the Logs directory and choose Compress to Logs.zip
  • Attach the zip file to the thread…
1 Like

Thank you FordGuy61 for walking me through that process :- )

Please see attached >>>

Logs.zip (1.3 MB)

Edited to correct attachment

Thanks for those logs.

I do see one problem.

DSM & Plex get confused when you have multiple NICs on the same subnet.

Dec 30, 2024 17:14:07.407 [139840835287696] DEBUG - NetworkInterface: Notified of network changed (force=0)
Dec 30, 2024 17:14:07.407 [139840835287696] DEBUG - Detected primary interface: 192.168.1.70
Dec 30, 2024 17:14:07.407 [139840835287696] DEBUG - Network interfaces:
Dec 30, 2024 17:14:07.407 [139840835287696] DEBUG -  * 1 lo (127.0.0.1) (00-00-00-00-00-00) (loopback: 1)
Dec 30, 2024 17:14:07.408 [139840835287696] DEBUG -  * 3 eth0 (192.168.1.70) (90-09-D0-59-29-76) (loopback: 0)
Dec 30, 2024 17:14:07.408 [139840835287696] DEBUG -  * 4 eth1 (192.168.1.210) (90-09-D0-59-29-77) (loopback: 0)
Dec 30, 2024 17:14:07.408 [139840835287696] DEBUG -  * 1 lo (::1) (00-00-00-00-00-00) (loopback: 1)

If you want to use both NICs, I recommend you go into Control Panel > Network > Network Interface . Click Create > Create Bond , select “Adaptive Load Balancing” option. This will work independent of you having a LACP switch or not.

You’ll end up with two adapters worth of traffic but only one IP address.
Plex will be MUCH happier.

Synology documentation here:

Thanks for the fishing!

I’m not married to the two NICs, I saw on a setup guide they recommended utilizing the second ethernet port. Because I can’t yoink the second ethernet remotely, I’ve set up the bond via your instructions (thank you for also linking the documentation)

Logged back into plex.tv and the desktop app, still unavailable.

Reinstalled the plex media server app, claim token, copy paste, once again successfully claimed. Same result.

Restarted the NAS (have you tried turning it off and on agan?). Same result.

Attached logs from after the restart.

Logs.zip (524.1 KB)

Did you do reclaim it (Claim Token method)

1 Like

Yessir. Claimed token, next, next, done, got the successfully claimed by BobbyThomson message again.

Looking at Plex.tv, your server is alive

Created 19 days ago
Last Seen 14 minutes ago 
Published No

There’s a manual edit to Preferences.xml we can do for this (make it Published)

Are you up for it?

If you are,

  1. Package Center
    – Install the Synology Text Editor package (if not already installed)

  2. Stop Plex

  3. Open FileStation

  4. Navigate “PlexMediaServer/AppData/Plex Media Server”

  5. Right-Click Preferences.xml → Open with Text Editor

  6. LOOK VERY CAREFULLY at each Name="Value" settings pairs.

  7. See if you have a PublishServerOnPlexOnlineKey="1" in the list of settings.

  8. If you don’t, at the end of the last line (it’s a LONG line), right before the closing />, put this value (separated by spaces from the others) PublishServerOnPlexOnlineKey=“1”
    – Looks like this: Something="Value" PublishServerOnPlexOnlineKey="1" />

  9. Save the file

  10. Start Plex

  11. close all browsers and then reopen them

  12. Open the Syno by it’s LAN IP

I have no idea what that means, but I’m down to try anything !

check your PM (upper right)

This did the trick.

After stopping the Plex Media Server app in the DSM, went in to edit Preferenes.xml with the Text Editor, confirmed the the server was claimed successfully, name email etc all correct.

The solve: Manually set PublishServerOnPlexOnlineKey from “0” (false) to “1” (true). Saved the file. Then started Plex Media Server app, logged back in to plex.tv, and we were online.

Thanks again for the help.