Thanks.
Confirmed. I have a ticket open with Synology. They are baffled.
From what I can determine:
This is a good indication of which source flags were altered in the build.
I will be forwarding to them immediately.
Thank you.
All right! Good to know.
We solved an issue for Synology. Great!
So I guess I can’t call myself an average user, and yet…
… my issue still persists, guys.
Respectfully the PMS authentication procedure is super cumbersome. My humble note to the dev team is that this bit is utterly cr…p. It’s ripe for a rework, as this is a paid service.
You’re not alone in your belief.
It’s “overly security-retentive” (catch my drift).
To add to that, the Plex/web client is decoupled from the server and will not remain ‘bound’ to the IP it loaded from (it deliberately “floats”) unless the server is cleanly “unclaimed” -or- firmly “claimed”.
How can I help with what you’re seeing?
Unfortunately at step#1 the authentication issue is persistent.
After about half a dozen retries, it logs in, but of course the server through which I tunneled is not visible.
Then I sign out, shut everything down as suggested, delete (rename the preferences.xml) and restart the one server I am trying to authenticate.
I wait 5-6 minutes.
At step #6 I get in the loop again and about 5-6 retries result this:
"Plex is down for maintenance
Don’t worry, it will be back soon"
May I have some basic unfo?
May I ask why you’re running publicly facing/WAN-routable (non RFC-1918) IP addresses on the devices themselves?
It’s just an old convention, and I have plenty reserved via DHCP in that range for several devices.
I normally have no problem with any service. Not even with PMS.
check your PM
thanks
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
