my problem got solved by restarting my Synology DS-218+ og “reinstall” the plex service… but before restarting i stopped the PLEX service in the DSM menu.
Having same issue on my QNAP TS-451+. PMS Version 1.18.5.
Apologies for the late reply (a weekend of machine rebuild for me).
- Server looks fine. It had a minor burp but fully recovered.
- If the app is being “ignant” (yes, deliberate spelling), uninstall it.
- Also, if uninstalling, Go to Settings - Authorized Devices and remove it (so it can start fresh)
- Reinstall the player app on the TV and link it again.
The apps are totally dependent on Plex.tv for direction where the server feeds Plex.tv
This is why apps go down when Plex.tv has issues.
Anyone else with this problem will probably find relief using this technique as well.
Couldn’t wait for a solution any longer…
I uninstalled Plex completely (expect the registry values) and reinstalled. Everything is working again, but it obviously required a lot of work to setup the server again and its related content permissions and tags.
A bit scary to know that my Plex server can be taken down (and apparently corrupted) by an outage at Plex.
It worked! And installed version 2368 as well.
Thanks ChuckPA!
Heh no thanks 
But you’re missing my point. These “locked out of my own server” bugs have been happening on and off for the past couple years, ever since Plex introduced non-local services like Plex Home. I have yet to see any actual steps taken to fix the root problem – every time this happens, all I see are support threads like these, and then everybody forgets about it and go back to business as usual… but really this is the kind of bug that undermines Plex’s business proposition the most.
I agree getting locked out of my own server is a PITA.
I also understand exactly what you’re saying about the single point of failure being a problem which silently goes unaddressed.
I wish I could influence those who make the decisions but I fought long and hard against this some 4+ years ago and, although winning some arguments, the final decision was as it is now. It’s Plex’s business decisions which have authentication work as it is now.
It will probably take a concerted effort by a large portion of the community, speaking as one voice, to be properly heard by those who make the decisions.
I live in the country where the internet is served on telephone poles and winter outages are quite common.
-
Define my home LAN as not requiring authentication. (Settings - Server - Network - Show Advanced) . I add
192.168.0.0/255.255.255.0 -
Run everything under one account - No need of a Plex Home
-
Have a standby alternate player which only needs LAN access to the NAS.
FWIW: My AppleTV also suffers when the internet goes out. As long as I don’t use Apple services, I can stay in the player app and I’m good to go.
After installing the latest PMS update today I had the same problem. Stopping/starting PMS on my QNAP NAS did nothing. Stopping Plex, rebooting my server and restarting Plex sorted it out.
Thank you all.
Hi!
I do also have problems reaching my library on my SynoNAS from any device as well as plex.tv. My server seems not to be online (even though it is without any other changes done in privileges or firewalls by me for many years and no problems with Plex, just the third 1515+ now because of the Intel c2000-bug)
When I have’t seen any new replies in 5 days I started wondering if there is a solution I have missed out? I have restarted the server as well as reinstalled with the latest PMS (1.18.6.2368-97add474d) but no success. The steps taken by other here didn’t work for me. Are you guys still waiting for an update from Plex or what can I do? I mean so I don’t wait for an upgrade that won’t come… or I haven’t seen or understood to do?
Thanx in advance!
Some others, like me, who recently experienced this, had Verizon Fios and corrected this by going into the FIOS mobile app and disabling Home Network Protection, which is installed on FIOS routers.
In my case, it was blocking requests to my server from Plex.direct. Once I disabled it, my server was visible remotely.
I wasn’t locked out when I was on my network. Again, not sure if this will help you.
Does the FIOS router firmware allow the insertion of a custom rule?
If it does, I suggest, which I use with Pfsense, allow private domain ‘plex.direct’.
Doing so keeps all protections in place and allows Plex’s private DNS to operate.
Thanx for the respond. Well I am locked out even when being on my own network. The internal address from the PMS app in the package center didn’t open at all first (...:32400/web) but after the update and restart of server and PMS I get redirected to the Plex app control but without the buttons for server and network. I can access other servers and resources but not my own.
I have a Synology RT2600 router and can’t find any similar setting like you mentioned. I haven’t made any changes in the settings and neither have the router had any updates since Plex was reachable last. I guess the fact that I can see and get connected to Plex account from my internal address (not redirected) after login on Plex shows the port-forwarding is working (...:32400/web/index.html#!/settings/web/general) I’m not that keen on networking so I’m not very sure about the last.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
