Unable to "Claim Server" and unable to setup remote server

Plex Media Server NAS & Devices
1

Hey Guys!

Plex Version: 1.3.4.3285
DSM: DSM 6.0.2-8451 Update 9
NAS: DS 412+

I recently switches ISPs, from Brighthouse/Spectrum to Centurylink Prism Fiber.
I have DDNS setup on my ASUS RT-66U router (running Merlin) and a whole mess of point forwarding setup to access my Synology (which has a fixed local IP).

Anyway, the DDNS seems to be working okay through the router, however, I cant seem to get it setup on the Synology (not sure its necessary though since the router does it).

I tried to access Plex outside my network unsuccessfully, I can get the home screen/page, but of course it says it cannot find the plex server.
So in my debugging I updated Plex was on something like 0.9.X), I’ve flushed the router DNS, I’ve tried disabling the synology firewall, I’ve tried stopping then restarting plex… I’m just not sure.

1 thing I did find that was weird is when I attempt to login and “Claim the Server” the browser console says this: FischStation is unavailable at https://142-197-164-123.22447632450a43b494a27a2b8dd3dd69.plex.direct:11026/ Which is very strange to me because 142.197.164.123 is a Brighthouse IP address not a CenturyLink IP (https://who.is/whois-ip/ip-address/142.197.164.123)

I used to be able to access and see the homepage for plex via my DDNS domain:32400… but now it reports that it cannot find ANY servers at all, I can only see the plex server when I access plex from the local IP 192.168.1.XXX:32400

Curious what other peoples thoughts are… (does it seem weird that plex is attempting to make a request to the wrong external IP address when my router is reporting the RIGHT external IP address?)

2

You need to SSH tunnel to the DiskStation itself and create a ‘remote console’ web browser session.

Go here https://support.plex.tv/hc/en-us/articles/200288586-Installation

and scroll down to On a Different Network

3

@ChuckPA Is this step/ssh only necessary to “claim the server” then after that I can access it locally or remotely?
(because I am able to get to the 192.168.1.132:32400 page and see the library/etc I just cant “claim the server”.)

4

@ChuckPA Also, I meant to ask, should the IP address of the server be the local IP (192.168.1.132) or should it be the current IP the DDNS is reporting (71.3.XX.XXX)?

5

you create the SSH to the remote IP of the server and specify the combination

ssh -l admin -L 8888:localhost:32400 ip.address.of.machine

once signed in (that’s all you need do), go back to your local browser and open http://127.0.0.1:8888/web

What the tunnel does is take port 8888 and redirects it to 32400 on the remote.

Now you have browser access to your remote machine just as if it had a graphics card locally.

1 Like
6

@ChuckPA Alright, ran through that but still experiencing the same issue, get an error that it cannot log into plex. (even though I’m logged into plex in that window, it cant log into plex within that claim server frame)

From the console.log:

[Connections] FischStation is unavailable at https://192-168-1-132.22447632450a43b494a27a2b8dd3dd69.plex.direct:32400/ (Status 0)
[Connections] Prevented fallback to insecure connection for FischStation
XHR finished loading: GET "http://127.0.0.1:8888/?X-Plex-Product=Plex%20Web&X-Plex-Version=2.13.0&X-Pl…x%20Web%20%28Chrome%29&X-Plex-Device-Screen-Resolution=1440x799%2C1440x900".
[Connections] FischStation connected at http://127.0.0.1:8888/
GET "https://plex.tv/api/resources?includeHttps=1&includeRelay=1&X-Plex-Product=…ce-Screen-Resolution=1440x799%2C1440x900&X-Plex-Token=uoR8jUCqp1qxbpMzRSmS".
[Servers] Found 3 resources through plex.tv
[Servers] Found all servers = FischStation, plex.tv
XHR finished loading: GET "http://127.0.0.1:8888/player/proxy/poll?deviceClass=pc&protocolVersion=1&pr…ce-Screen-Resolution=1440x799%2C1440x900&X-Plex-Token=uoR8jUCqp1qxbpMzRSmS".
[Companion] Opening long poll to FischStation at http://127.0.0.1:8888/player/proxy/poll
XHR failed loading: GET "https://142-197-164-123.22447632450a43b494a27a2b8dd3dd69.plex.direct:11026/…x%20Web%20%28Chrome%29&X-Plex-Device-Screen-Resolution=1440x799%2C1440x900".
[Connections] FischStation is unavailable at https://142-197-164-123.22447632450a43b494a27a2b8dd3dd69.plex.direct:11026/ (Status 0)
[Connections] Prevented fallback to insecure connection for FischStation
7

what am I looking at? Is that an edited log file fragment?

What should happen is the SSH session should be 100% silent after you log in.

Everything you do happens through your browser.

8

@ChuckPA, I’m sorry, I understand what happens with the SSH work.

I was able to access 192.168.1.132:32400 before just fine. I can log into the plex server, I can see my library, I can even play media just fine within that interface.

I cannot however “claim my server” or setup “remote access”. Any attempt to do that fails. I was sending along the a snippet from browser console.logs just to show that it seems to be continuing to reference an IP address that should no longer exist (142.XX…). My assumption is that if it was using the proper IP (71.3.XX.XXX) then perhaps I could successfully login to claim the server and setup remote access. (But I’m not sure)

9

ah ha solved it!

For anyone running into the same issue, check the DNS settings on your NAS -> Control Panel -> Network -> General

Make sure that the “default gateway” and the “preferred DNS server” match, they should be the IP of your router, typically 192.168.1.XXX
Also the “Manually configure DNS server” should be CHECKED.

2 Likes
10

Thanks, was worring that is was my NAS and version. It is working.!!

11

Thank you aaron big help

12

@“aaronfisch@gmail.com” said:
ah ha solved it!

For anyone running into the same issue, check the DNS settings on your NAS → Control Panel → Network → General

Make sure that the “default gateway” and the “preferred DNS server” match, they should be the IP of your router, typically 192.168.1.XXX
Also the “Manually configure DNS server” should be CHECKED.

I could kiss you…so many people looking for zebras in the code it makes my head spin. This was fixed my issue.

13

Aaron- After hours of trying your post saved the day. Thanks