Installed latest PMS file but Plex says I need to udpdate

Server Version#: PlexMediaServer-1.30.1.6483-85af1e381-aarch64_DSM6 (Dec. 7)
NAS: Synology DS220j running DSM 6

Plex stopped working for me in October and I’ve been trying things off and on to get it going.

The current install is noted above, but it seems to have been a reversion from PlexMediaServer-1.30.0.6486-629d58034-aarch64_DSM6 which was the version posted yesterday on Plex.

What I’ve done most recently-
Yesterday:

  1. D/L and upgraded to 1.30.0.6486. Went to claim server using incognito mode and PMS downloads said “An update is available, please install manually.”.
  2. Uninstalled 1.30.0.6486, removed all Plex files from the NAS (I’d been trying several suggestions from the threads and none helped, hence this nuking,) reinstalled 1.30.0.6486. Same issue: “An update is available, please install manually.”.

Today:

  1. Checked for updates in case .6486 was a problem version, and found what seemed to be a reversion to 6483. Downloaded it, uninstalled 1.30.0.6486, installed 1.30.0.6483. Went to claim server: “An update is available, please install manually.”.

Prior to these updates, I was able to reach my server and claim it, but still could ONLY access my movies etc locally, and only using the IP address–in other words, it did not seem to be registering with Plex over the internet at all.

1 Like

Check your Update channel (Settings - Server - General - Show Advanced)

Claiming DSM 6 servers :

  1. Be on the same subnet with it
  2. – close the browser fully (browsers love to keep credentials even in incognito mode)
  3. Now open it (same RFC-1918 compliant subnet)

If that still fails, I’ll give you the link to the reset tool.

Thanks for the reply. It does, indeed, still fail. Even tried with a browser I’ve never used on this PC for good measure. Still prompts for an update.

PC or Syno?

PMS on the Syno will probably prompt (they just changed things today).

Let’s get you working again then deal with that.

Here’s the shell script utility.

I’ll show you how to use it via Task Scheduler if you need to.

Thanks. I learned how to use the terminal software to do this, so that’s good. The result wasn’t great, as it could not get the credentials. :slightly_frowning_face: See below

Clearing Preferences.xml
Getting new credentials from Plex.tv
ERROR: Could not get credentials from plex.tv (Error: 51)

It took about a minute and a half before it returned that message. I’ll try it again tomorrow; maybe it was a glitch in the connection or the plex.tv delivering it.

To clarify, I have been doing a manual install of the software packages. From the Syno box, I see this:

image

As you can see, the latest the Syno store has is many versions back, and is always this way. So I download from a Windows browser and run the install on Syno (via its web interface). I am on the PlexPass channel, by the way. As of right now, the manual download is the same Dec. 7 version that was available earlier today.

OK, I tried this again this morning and got the same result.

I just upgraded and getting the exact same problem. The package won’t run.

Did the token time out ? (The token is only valid for 5 minutes from the instant it appears)

For those servers which won’t start –

Please make a ZIP file of the Logs directory and attach it here.

I’ll look at what’s happening.

Fixed it. I went to the plex.tv download page and grabbed a copy there. For some reason that one worked for me. I usually download it from the general settings page.

It did not time out due to the token being too old–I got it entered within one minute of the token being created. It seems from the error that it had a problem getting to plex.tv or plex.tv had a problem returning whatever it was supposed to return. After I entered the code, it paused for a couple minutes then gave the error.

Logs are attached.
Logs.zip (767.9 KB)

bumping this to see if the logs help solve

When my server did an auto update for 1.30.1.6497, it auto installed the 32-bit version.

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