Helppppp

Server Version#: 1.20.1.3252-a78fef9a9
Player Version#:

I run DSM 7 preview on my DS218. I’ve got it working just by starting it again with the start stop status script. I have installed it with a PLEX-account where I have activated a yearly PLEX PASS.

At the end of my subscription I have made a new email-account wich I have decided to use for all of my software installed on my server. On this email account I have bought a lifetime plex account.

I logged out of my PLEX SERVER and wanted to log in again on my new plex account, thinking that I could simply claim it again…

But this didn’t worked out the way I expected. Please advice me how to get back into PLEX SERVER and claim my server in order to use it again.

Thx for the help.

Have you already checked the entries related claiming/reclaiming a server in the Synology FAQ?

@Terneusen

If you have no success there, please reach out again.

While we don’t yet officially support DSM 7, I can give you the manual instructions for getting the server back into your account again.

Hi ChuckPa,

Does it matter that my formal account does not have a plex subscription anymore?
As I wrote in my message I have created a new Plex Account with a liftetime subscription…

I have tried everything except the part where I have to do a re-install… Simply because I can’t, I’m running DSM 7…

Everything worked untill I accidently pushed the logout button to logout account #1. I even deleted the preferences.xml file (I made a copy before…).

Please send me the manual, thanks alot!

I now get the message: “No soup…”

It does not matter which account the server was attached to.

Given you’re using the Community-created start-stop-status script workaround, you can run what you have until DSM 7 public beta unveils the new package we’ve been working on.

I do urge you to get your DSM 7 server properly connected to your Plex Pass account prior to advancing further because of the packaging changes we needed to implement in DSM 7.

Here’s the schtick :slight_smile:

Part A - Remove it from Plex.tv

  1. Stop the server
  2. Open a browser window
  3. http://app.plex.tv
  4. Sign into the account which currently owns your Syno.
  5. Settings - Authorized Devices - Server (dropdown)
  6. “X” (Remove) your Syno from that list for now. (it will return under your new account)
  7. Sign out of Plex.tv and close that window MOST IMPORTANT

Part B - Make it forget where it was

  1. Install Synology Text Editor app (beta)
  2. If you don’t see the Plex share in FileStation, give yourself R/W
    permission to edit it in Control Panel - Shared Folders - Plex - EDIT - Permissions tab
  3. Navigate into Plex / Library / Application Support/ Plex Media Server
  4. Right Click Preferences.xml - Open in Text Editor

This is where you must be careful.
All preferences are of the format Name=“value” and separated by spaces.

Remove each of the following Name=“Value” sets for:

  1. PlexOnlineUsername=“value”
  2. PlexOnlineToken=“value”
  3. PlexOnlineMail=“value”
  4. PlexOnlineHome=“value” (if you are using a Plex Home)

Save the file.

At this point, the existing server is no longer owned by the old account.

Part C - Start and claim the server

  1. start the server under DSM 7
  2. open http://ip.addr.of.syno:32400/web (you must be on the same subnet)
  3. Sign it in and claim it under the new Plex Pass account.

Hi ChuckPa,

Thx, but this didn’t work for me…

I’ve got the “No soup message…”

Hi Trumpy81,

I created a new local IP-range: 28.8.82.1-254

Does this matter? No matter what I try, I still got the message NO SOUP…

I have attached the logs.

Thx for helping me out

Logs.rar (550.4 KB)

As trumpy stated,

You cannot use a publicly routable IP address on your home LAN.

Your LAN must comply with RFC-1918

192.168.x.x
172.16.x.x - 172.31.x.x
10.x.x.x

OK, thx for explaining… This part was not very clear to me because it has worked before.

Why did it worked before? Under that new created ip-range…?

Or can I just simply put it back after I restored the server?

Once the server is logged into your account, you can use any addressing you want.

The problem is that PMS, when it sees itself as having a public IP address, is extra cautious about letting someone claim it. (you must log into the system and use 127.0.0.1 in those cases)

Once you have your server logged in, and for as long as it remains signed in, you can use any addressing you want.

The owner of the IP range you’re using won’t be too happy though – FYI
(which appears to be isws.illinois.edu)

I’ve tried log in through the 127.0.0.1 address but this is not working…

When I look at the preference.xml file, there is also mentioned my own-created IP-range. Does this effects some how or can I leave this as it is…

Or is it better to (make a backup first) delete the preference.xml file?

Best is to use the proper IP addressing range.

I think I gonna put back the initial ip-range given by my FritzBox

whatever you wish.

Regarding the xml-file…

Can I just leave it as it is or delete it?

personal Preferences.xml files with personally-identifying information are removed.

This is policy to protect your privacy.

Sorry for that…
I’ve deleted the attachment in my previous answer aswell.

FIXED IT.

Thanks guys for saving my marriage… LOL

Goodmorning ChuckPa,

I’ve got a small question regarding DSM7 BETA.

Can I update my PMS to the latest version now, or…
Package centre still says that PMS is not compatible, but I’ve think the old version is the cause of this error.

Please advise me what to do.
Thx

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