Thank you so very much! What a great service you are providing for Plex users. The reason a lot of people avoid Plex is it seems difficult for them and a lot of work if you have to rip a huge library of DVD’s but it is worth it in the long run. God bless you!
Ok so everything seems done now. The only issue i see is that in my list of Plex servers i see 2 old entries, my old server name as well as copy of my current library name but both “unavailable”. These are in addition to my current (and working) library.
Is there a way to delete the 2 old entries?
Thanks,
Will
Awesome, all set now! Really appreciate the help. You should implement a “buy you a beer” button on this forum 
Descrivo la mia situazione. PSM mi dice in esecuzione, ma qualsiasi device uso mi da il server offline. Vi prego, che devo fare ? Grazie.
Per DSM7,
-
Disinstallare il pacchetto, utilizzare l’opzione ‘mantieni’ per conservare tutte le informazioni. Questa è l’azione predefinita.
-
Reinstallare il pacchetto utilizzando l’opzione “Token attestazione Plex”.
un. Fare clic sul collegamento “Ottieni token di richiesta”
B. COPIA il token dal tuo browser.
C. Incolla nella piccola finestra sotto l’opzione del pulsante.
D. Fare clic su AVANTI -
L’installazione richiederà circa 20-30 secondi in più del normale. Il programma di installazione sta comunicando con Plex.tv per richiedere nuovamente il server per te.
-
In caso di successo, stamperà il pop-up che mostra il tuo nome utente Plex.
-
Il server è ora ricollegato al tuo account…
================================
For DSM 7,
-
Uninstall the package, use the ‘keep’ option to retain all information. This is the default action.
-
Reinstall the package using the “Plex claim token” option.
a. Click “Get Claim Token” link
b. COPY the token from your browser.
c. Paste into the small window below the button option.
d. Click NEXT -
It will take approximately 20-30 seconds longer to install than normal. The installer is communicating with Plex.tv to claim the server again for you.
-
When successful, it will print the pop-up showing your Plex username.
-
The server is now reattached to your account…
Hi, I just updated to DSM 7.0.1 and have a problem.
- I uninstalled the PLEX app on 6.2.4, then upgraded to 7.0.1
- Restarted
- Downloaded the PLEX Package for DSM 7 and did a manual install.
But the “Setup” Process seemingly did not see my previous DSM 6 data and made a fresh install.
I now have the old Plex folder with all my data as well as the new PlexMediaServer folder which is used by the PMS app.
(The old Plex folder is a couple of GB and the new PlexMediaServer has about 4 MB)
How can I fix this?
-
Uninstall + ERASE option. This will remove the errant DSM 7 installation
-
Now I must ask the exact UPPER/lower case spelling of your “Plex” shared folder.
-
If it’s been renamed/moved by you and is not “Plex” or “plex” then the installer won’t see it. (Capitalization is important on Linux).
-
If you moved / renamed it at any point, it’s easy to correct. Please let me know
Thanks for the quick answer.
OK I uninstalled the package with Erase option.
I never touched my Plex shared folder and as far I can see it´s just “Plex” with upper case “P” and lower case “lex” - You mean the folder seen in the screenshot I posted above I assume?
I tried an installation once again but it still does not see my DSM6 data.
Lo stato è questo e i client funzionano. Ma se cerco di aprire il server, cliccando su apri, mi da questo errore.
Now that it’s done, Reinstall again and see if migration engages automatically (it should).
If not, then Uninstall + ERASE again. ( MAKE CERTAIN your server info is still in the Plex share before clicking ERASE)
I’ve seen this happen when the REPAIR button was pressed during DSM 6->7 upgrade. (it creates an invisible and unusable instance).
The second ERASE clears it out.
Lastly, if the migration does not engage – again uninstall + ERASE then
- Rename the Plex share to “Plex-renamed”
- SAVE that
- Rename it back to “Plex”
between clearing out any errant DSM 7 instances (any of which will block migration)
and the shared folder renaming – it must engage – UNLESS it doesn’t see a legitimate installation in the Plex shared folder (we can examine that next)
Thanks again but I still have no luck.
I uninstalled (with Erase) now multiple times including renaming my shared folder and renaming it back to “Plex”.
When installing I still get a fresh install without migration.
I don’t know if this has anything to do with this but I migrated my Windows 10 PMS data to my NAS a couple of months back. Maybe because of this it does not see it as a valid PMS folder?
I think I might have it.
Since I had the PlexMediaServer user I gave him all permissions according to the Migration-Walkthrough.
Then I installed PMS again and now I am sitting at the …installing… screen for a couple of minutes, so I think it is finally migrating
And it just finished migrating.
=> OK it seems all fine now. But the point remains that without permissions it did not produce an error message and just made a fresh installation out of it.
Should NOT have happened. ( I am the author and it doesn’t work that way ) 
Something else in the muck there ; we just need to identify it for others.
Migrating from windows might be the key and I VERY much would like to understand what could fool the installer into thinking it doesn’t have a valid installation if PMS was actually running on the machine.
If you’re installing / migrated over – ALL GOOD
I still want to figure out and handle WHY
@ChuckPa
OK, I think I am finished and PMS is running as it should. All the Data is in the PlexMediaServer share and the server is up and running.
If you want to find the root cause of my problem I am happy to help - just let me know what I can do
With it all migrated, it’s hard to post mortem it.
Maybe if you write down what you did to get it to trigger (line item style), adding what the name(s) were and what you renamed to where applicable, I might be able to reverse engineer it.
Open the server by using its IP address in your browser. Let’s see if this is a DSM issue or a Plex issue. The screen you show “Synology” is pointing to this being a Synology redirection problem.
Apri il server utilizzando il suo indirizzo IP nel tuo browser. Vediamo se questo è un problema DSM o un problema Plex. La schermata che mostri “Synology” indica che si tratta di un problema di reindirizzamento di Synology.
Thank you for quick reply!
- DNS resolver config.
a. Host → modem router → ISP / other DNS as you wish
Can you please elaborate? I don’t know what this means.
Hi @ChuckPa ,
I just had a very similar problem with the last version of Plex and DSM 7.0.1…
In my case:
- I didn’t came to the Plex forums prior to upgrade to DSM 7.0.1 so I didn’t see I had to delete Plex for DSM 6 before, and I upgraded to DSM 7.0.1 first.
- I came to the Plex forums prior to upgrade Plex so I started to follow your procedure and deleted Plex (not repaired)
- I downloaded Plex for DSM 7 and installed it manually (Normal installation - PMS & the data were in the same folder, but the package delete)
At the end, I didn’t got any warning and also didn’t got any migration confirmation screen.
Plex didn’t see my DSM 6 data and just made a fresh install.
So I gave the full rights to the PlexMediaServer user on the \Plex\ folder, deleted the package (2nd option: Sign out and unclaim this server. Keep all existing files for future re-installation.) and reinstalled Plex, but still the same, always a fresh install. I did it 2 or 3 times, no change.
It’s only when I saw your answers to mike4001 that I finally removed Plex deleting all the data of this DSM 7 install (3rd option in red) and that the next installation finally worked, my DSM 6 data were found and I finally got the migration confirmation screen.
All this to confirm that this case were we get no error message and no migration confirmation screen exists and is not described in your migration instruction and help topic. So the users get a bit lost, not really knowing what’s going on.
Last things:
1/ My Plex is now running fine but the data has not been moved from the old Plex shared folder. Is it normal ? I thought they were supposed to be transferred and we could even delete the old \Plex\ folder?
2/ I already got 2 warnings from Kaspersky saying that there was an unsafe SSL connection running with invalid certificates from (192-168-x-x.d0a05c3c425344b3882d06bf29ae78f6.plex.direct). Are you aware about such issue?
Thanks!
Name lookup works this way:
- Look in the list of known addresses on this “host” (computer)
- If none are found, forward the lookup request to the “DNS Gateway” IP address listed in the adapter’s configuration. Since that’s a modem/router with no stored info (some do) it forwards out to the ISP.
- The ISP continues to forward the request until SOMEBODY knows the answer and then sends back the reply (the IP address).
That’s the connectivity (definition) you don’t have.
In your case, safest config –
- The IP address of your modem/router should also be your DNS lookup IP address
Did you hit “Repair” ? it sounds like you did
As long as you have data in your “Plex” shared folder without the server performing its migration (moving the data), ERASE when you uninstall.
At this point,
-
reinstall
-
Uninstall + erase
-
Do it again.
-
After the 2nd erasure – having confirmed your data is still in the Plex share,
-
Install that third time. It will engage
The reason it does this is I have written the installer to not overwrite an existing installation – that’s why it doesn’t start migrating
What happens is:
- Repair puts a bad , inaccessible, invisible server data on the system.
- First attempt to install moves that to the old location
- Second attempt moves that to PlexMediaServer shared folder.
- Third time, having deleted all that DSM 7 stuff in the way, it will engage
(there is a shell game happening with data behind the scenes. eventually it all moves to the front where ERASE really does erase what was causing the block and clear the path for a proper migration)
