Hello all.
I just installed a “new” DS214se - upgraded to 6.1.1 update 4, installed Plex 1.7.2.3878.
Upon launch and going to :32400/web - I signed in with my existing Plex account.
New disk station was not found.
At this time I screwed up and when under server signed out, my existing Synology DS1815+ from my plex account, which is not affected by the same issue. More later.
For ■■■■ & giggles I signed out, created a new plex account, and it just shows “looking for server…” and never finds the server.
Now my existing Plex account dropped the existing Plex server, and I can’t seem to re-add it either. Same version Plex, same version DSM.
Until you complete the first-time setup / initialization after install (which you access by opening the IP address of the Syno), you will not find it anywhere on your account because it isn’t linked to it yet.
Chuck,
After installing Plex on the syno, I went to http://:32400/web - which asked me to either signin/signup for Plex account.
I chose Signin - it showed me the existing media libraries on my shared on own existing servers, but no setup.
You didn’t screw up but things did change a great deal.
Since 0.9.17.0 (when it all changed with the advent of console security), if not careful setting it up, you can get yourself locked out (it doesn’t recognize you as owner… it has a ‘null’ owner).
Easy to recover from.
Stop PMS on the new Syno
Open File Station, Navigate into the Plex share -> Library / Application Support / Plex Media Server
Delete Preferences.xml
Open a browser tab and prepare to access the server http://ip.addr.of.syno:32400/web but don’t hit it just yet
Start PMS in Package Center
Let it get going (20 seconds)
Now access via that browser tab
Be greeted and the ‘Got it’
Now it will want to sign into your account. Do it
If asked whether you want to Claim the nas, do so.
Now you will proceed through the first-run setup wizard where you create your libraries (this part hasn’t changed much)
No dice. I can delete the file, startup PMS, but it returns me to the login screen.
I’ve attached the PMS log, it looks like it’s trying up upload a crash report and that it can’t reach the discovery service?
Jun 07, 2017 21:57:18.489 [0x439ed400] DEBUG - Job running: ‘/volume1/@appstore/Plex Media Server/CrashUploader’ ‘–directory=/volume1/Plex/Library/Application Support/Plex Media Server/Crash Reports/1.7.2.3878-8088811b8’ ‘–version=1.7.2.3878-8088811b8’ ‘–platform=linux-synology-armv7 (3.2.40 (#15101 Mon May 22 10:01:34 CST 2017))’ ‘–serverUuid=’ ‘–userId=NOUSERID’ ‘–url=https://crashreport.plexapp.com’
Jun 07, 2017 21:57:33.346 [0x44ac2400] WARN - HTTP error requesting POST http://127.0.0.1:32600/devices/discover (0, No error) (Failed connect to 127.0.0.1:32600; Connection refused)
I found the problem. Since you’ve last configured a server, part of the new security is how which IP addresses are automatically considered local versus those which are remote.
This usually isn’t a problem but your LAN configuration is one of those which does have the problem.
Jun 07, 2017 21:59:07.557 [0x44416400] DEBUG - Request came in with unrecognized domain / IP ‘59.5.0.134’ in header Host; treating as non-local
Jun 07, 2017 21:59:07.558 [0x447d4400] DEBUG - Request came in with unrecognized domain / IP ‘59.5.0.134’ in header Host; treating as non-local
Jun 07, 2017 21:59:07.579 [0x44416400] DEBUG - Request came in with unrecognized domain / IP ‘59.5.0.134’ in header Host; treating as non-local
The only addresses which PMS recognizes, by default, as LAN local are those in the 10.x.x.x and 192.168.x.x as per RFC 1918 Private LANs.
PMS is starting, seeing your requests coming from 59.5.0.134, considering you to be remote, therefore you can’t possibly be the owner at this point.
The best solution is to change everything to either of the two Private LAN ranges.
As an alternative, if you are comfortable doing so, is to edit the Preferences.xml file using the Synology text editors and “White listing” your LAN. Only then will you be able to continue.
If you white list your LAN in this manner, should you ever need to reinstall / re-initialze, you’ll have to manually allow yourself again. This is why making the LAN change is the best choice. Change it at the modem/router once, Have all the addresses (DHCP) update on each device and it will be done. If you have any devices with static IPs, you’ll need to change them by hand as well.
Chuck - That did it. I appreciate it!
I have several networks available, and ended up moving the DS214se onto a different network, 10.x.x.x/8 base, jumping onto a RDP session on a machine within the same subnet and voila.
I was able to get my existing Plex server re-claimed by visting it from same subnet as that Syno unit.
Did not realize Plex had that many checks built in - while this was a bit of a PITA, glad for it, and much appreciative of your assistance and guidance.
Marco,
You’re welcome! I know it’s a pain, but what it gave us was the ability to properly protect PMS from CG NAT (Carrier Grade NAT) networks where even the WAN address is a private LAN.
Now that you have it claimed, if you want to start whitelisting your subnets, go ahead. I recommend keeping a copy of the Preferences.xml file when you’re all done as it contains the whitelisted ranges. It will let you recover/rebuild without need of doing this again.
I enabled SSH on the Synology. Tried signing in through putty using 65.x.x.48 (my IP address) as my host name, 8888 as my source port, 65.x.x.209:32400 (synology’s address) as my destination. And I got a blank command window.
Tried signing in through putty using 65.x.x.209 (synology’s address) as my host name, 8888 as my source port, 65.x.x.209:32400 (synology’s address) as my destination. Could sign in as admin. Got “Could not chdir to home directory /var/services/homes/admin: No such file or directory” Then, let the command line sit. “admin@ServerName:/$”
I think its failing because i’m using the same address as host name and destination, but when I use my IP address as host name and the synology’s address as destination, I get a blank command window.
right click plex media server and hit “open plugins folder”
now delete the whole plex folder not just the plugins folder
uninstall plex
Delete the reg entry.
for windows: hold Windows key+R
Search for…Its “user” keys or something like that…user being the key word. Then search for the “software” folder. In that folder, you will find a plex folder. Delete that.
