Server Version#: PlexMediaServer-1.27.1.5891-c29537f86-x86_64_DSM7.spk
.
This server version above is not the Synoloby beta version for the Synology DS1621+ NAS. but the behaviour is identical with regard installation. I cannot access my Plex Media Server. All I can get to is the player. The article I was provided to fix my issue is “Why am I locked out of Server Settings and how do I get in?” After following the instructions as best as I understood them, they did NOT WORK for me. I’m still locked out. What must I do to reset my server and/or account so I can get a Plex Media Server running with my content?
See Synology FAQ 15: Claiming & Connecting to a troublesome Synology server.
If that does not work, please provide a set of server log files (FAQ 1).
- In Package Center, stop Plex Media Server.
- In File Station, go to /PlexMediaServer/AppData/Plex Media Server. Compress the Logs directory to Logs.zip.
- Upload the zip file to the thread (Drag it into the message window. It will insert at the cursor location).
I had this issue with 1.26, 1.27.0 and now again with 1.27.1 on DSM6
When upgrading to 1.27.0 I was able to regain connection by removing my server and all players from the “authorized devices” list in web view player. Then I logged out of web player and restarted the PMS app in package center. Once it restarted I waited about a minute then went to the web player login page and logged in then claimed my server.
When upgrading to 1.27.1, none of the above worked in any browser or player. I uninstalled and reinstalled PMS and did all the above again, didn’t work. I installed an older version and again, nothing worked. I waited a day after reinstalling and claiming the server and again nothing, it just kept saying not authorized even though it showed my server was authorized.
Finally, I resolved it by logging into the web player on two tabs in the same browser, then on one player tab I went to the console window to view live errors while on the second tab clicking the “Claim Server”. I had to claim it twice since it failed the first try (giving http1.1 500 errors but on the second try it worked no problem and was back up and running again on all players.
Has your situation resolved? If not -
- Restart Plex
- Wait 3 minutes
- Stop Plex
- Using FileStation , manually navigate into the Plex/PlexMediaServer shared folder until you see the
Logs
folder. - Right-Click it and
Compress to Logs.zip
- Download that zip file
- Attach here.
I have no confirmation that log files requested were ever received via any normal reply to the forum e-mails I received. All of my replies came back as undeliverable and I don’t know what I may be doing wrong I would think that if I don’t change anything other than the body of my message, it should work. That does not appear to be the case. This forum, software is not intuitively obvious to use and in my opinion, presents a very bad customer experience. I’ll stop there.
I believe uploded my log files here (4th time I’ve tried to get them to you. Let’s hope this works.
Plex Media Server.zip (408.6 KB)
received. If not, please provide clear directions on how I can get these log files to you.
Thanks for those logs.
Attaching ZIP files to notification replies goes nowhere. AFAIK, the notification is a ‘no-reply’ type address (outbound only).
In looking at your server logs, I see you have public IP addresses for your network adapters.
Specifically, the IP addresses you’re using point to an address in Jessheim, Norway.
Are you aware of the requirement to have your LAN configured for RFC-1918 addresses ? (10.x.x.x, 192.168.x.x, 172.16.x.x → 172.31.x.x)
Thanks, for responding. No I was not aware of the requirement to use regarding RFC-1918 addresses. My IP addresses used to be 192.168.x.x. I just recently became aware that my current addresses were “Public” and you are the 2nd person to confirm… I had previously followed the advice of a YouTuber who said the 192.168.x.x addresses were easy targets for hackers and it’s better to use addresses that don’t use 192.168… addresses. Perhaps that was NOT good advice. I will change my addresses back to what I understand are “Private Addresses”. Will that also fix my Plex Media Server problem?
Bob
With all due respect to those who contribute to YouTube,
That particular YouTuber doesn’t know what he/she is talking about.
Per RFC-1918 ( Private network - Wikipedia ),
all the providers decided on a standard.
In that standard:
-
NO RFC-1918 addresses are publicly routable. (Internet backbone routers will not route any of these addresses. They get dropped upon reception)
-
RFC-1918 addresses only exist on the customer-facing side of the Modem/Router.
-
This type of Network Address Translation (NAT) allows for your modem/router to share access (a single WAN IP address) between all the devices in your home.
-
I can safely tell you (publish here) EVERY LAN address I use and be 100% safe – because the internet doesn’t route RFC-1918 addresses.
-
Knowing this standard is in use allows us to look at an IP address and know if it’s LAN or WAN (This is what made Plex go into lockdown on you)
-
From the security perspective, which is where I’m sure that YouTuber was thinking
– If someone gets inside the modem/router and firewall, it’s because the door for him/her was opened by downloading malware or turning off / misconfiguring the firewall to ‘wide open’ status for critical ports.
– Once inside the LAN, A) you have a bigger problem B) it will take him TWO commands to find everything.ifconfig
andnmap
– *ifconfig
shows all ethernet adapter configurations. (now he knows all the LAN subnet addresses
– * nmap will scan each subnet for hosts and print out a report of what it finds. (Creating complex home networks without the right equipment provides NO PROTECTION)
Crazy, isn’t it?
YES. you will be able to open it by its LAN IP address and claim it again.
Once claimed, it doesn’t matter which address(es) you use
Thanks for your advice. I made the changes you sugested and.My Plex Media Server is back up and running.
Bob
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.