Server Version#: Version 1.19.1.2701
Player Version#: n/a
This is a longshot, new Synology NAS, new version and install of PMS, updated manually.
Not unfamilair with PLEX and been using for many years on versions of Synology, since DSM 4.x/DSM5.x/DSM6.x.
But clearly there has been a change I’ve been reading about, which is todo with Public and Private networks, and Configuring the PMS.
This is a Public Network and of course IP Address which cannot be changed, if I allocate a Private IP to the NAS all is well, and can be configured.
BUT using the Public IP Address, always disappears off to the Plex Web website, and cannot login or configure the NAS.
is there any work around, before I put a router in front of the NAS., to route traffic from current LAN >>> PLEX NAS.
I’ve experimented with IP address Auth, custom URLS, changing interfaces prefs…
thanks for this I’ll have a look.
The problem does not seem to be the setup, because I can set it up, using a Private IP Address.
But it cannot be contacted on the Public Network, unless this has something to do with the server is not claimed, because my existing Private does not have internet access.
Well the Tunnel works, but I just get to the Plex Web App, sign in as normal.
But it just shows me two other Plex Servers (the old ones running - Version 1.5.3.3580
I still cannot see this version.
ChuckPa
Split this topic
April 25, 2020, 10:07pm
5
8 posts were split to a new topic: PMS in a data center
I’m stuck here as well, and I cannot modify the client it’s a Samsung TV on the Public Network!
“Having a server, on a public IP, in a datacenter, is fine. – It needs IPv4 capability.”
that’s what we have, and we cannot configure, it just keeps going to Plex Web.
I assume this is a massive change from Version 1.5.3.3580 - which does work.
and the logs do state non-local.
So why the change, yes I’m aware of RFC-1918 and non-routable networks, and their ranges.
Just read this post…
I understand!
Here we go
Plex and not claiming using domain names
This sounds like a confusing way to do things and very much like a bug but it’s quite deliberate.
IPv4 is broken into 3 classes:
a. Class A - 1.x.x.x → 126.x.x.x
b. Class B - 128.0.0.0 → 191.x.x.x
c. Class C - 192.x.x.x → 223.x.x.x
Class A space is used by the main internet itself, extremely large companies, and whole governments. It’s also a very convenient way of partitioning the world’s traffic.
Class B space is…
need to investigate the ssh tunnel again…
you upgraded from 1.5.3 ?
I suspect I know now what happened.
With that big of a change, and all the database schema changes since then , it probably fell off (signed out) of your account.
Yes, I see you posted the SSH tunnel one as I was typing . (there are others)
ssh -L 8888:127.0.0.1:32400 ip.addr.of.remotehost
-sign in
-let ssh session sit idle
In local, incognito window, signed OUT of plex/web from the upper right corner
http://127.0.0.1:8888/web
(jump through the ssh tunnel to end up on the remote’s loopback adapter)
Nope, we have two Plex servers already running 1.5.3 working fine.
Just checking tunnel, tunnels all working… used a different username and password, created a new one for the time being…
now it’s just Constantly looping and display a dash board from the web, and not finding or configuring the server, e.g. add media etc
tried incognito, select add media, and it wants me to download Plex Media Server.
May i have a ZIP or tar.gz of Plex’s Logs directory?
Something isn’t right here.
Also, is this Linux desktop/workstation/remote server or Synology?
I’m getting confused
This is a Synology NAS.
and a standard Windows 10 PC trying to access and configure.
The other PLEX installations, are also on Synology NAS, but much older running 5.2.
Just tested by dual-homing this NAS with two different IPs, e.g. given it a 192.168.1.1
and using a VM on the NAS in 192.168.1.2, PLEX works as expected.
but try to use the Public IP address of the LAN, and it just loops.
and no login to Plex is required.
I’ve just now CLAIMED the server, and it’s logged in as my user, which manages the other PLEX servers.
Let me just check now, if I can login… from the public LAN
Nah, that does not work either direct or via SSH tunnel, it prompts to sign in, and then sign in, and does not show the NAS.
Which logs ?
What will help me the most at this point is to see what PMS sees at startup.
Stop Plex
Wait 3 minutes for the listening port to fully close
Start Plex
Wait 1 more minute for it to startup
Settings-Server- Troubleshooting - Download Logs
Attach that ZIP file please.
There are two different situations going on here.
One appears to be synology on LAN
The other appears to be a normal server with public IP.
I need to split this thread appropriately.
@icepicknz
@einsteinagogo
Please help me out? Please tell me what you have and what the fundamental Ethernet configuration is: LAN or WAN
Thanks.
Okay, I experimented, and noticed, after claiming my Server (on Synology), that there was an explanation mark next to Remote Access, which was not present for the other working Plex servers on earlier versions of Synology NAS (5.2).
So we changed firewall rules, and changed the port to 32401, and then the Remote Access Green tick appeared.
and then
Fully accessible outside your network - Appeared.
On going to https://plex.tv/web .
I could access the new Plex Server and the old versions although it had a moan about them being old and needed upgraded, and to manage them direct.
the something must have happened, because now going to the server…
it all works!!
Thanks for your support, I think I may treat myself to a Plex Pass!!! (lifetime!) it’s about time!
Thanks again @ [ChuckPa]
system
Closed
July 24, 2020, 10:34pm
20
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.