Install help - non private ip range network

Plex Media Server NAS & Devices
1

Hello -

I’m brand new to Plex and i’m quite frustrated hoping someone maybe able to help me get my very first PMS up and running.

my home network is set up with a non private up range (2.15.85.x) and when i launch plex from my synology NAS all it does is continue to search for the server. Now i’ve found the install article about having to ssh if you are on a different network than the PMS however (assuming my tunnel is correct) i still cannot reach the server when using the localhost syntax in an attempt to “claim” my server.

I would really appreciate any help anyone can give.

Possibly even ChuckPA? You really seem to be able to solve issues from what i’ve read over the last 2 weeks of trying to find a resolution to this issue on my own.

thanks!

2

I can tell you right now, having a non-private home LAN IP range is going to drive you nuts.

Your only recourse is to use a SSH tunnel.

In the case of the Synology:

  1. Control Panel - Terminal & SNMP - Enable SSH
  2. Using Putty or SSH, you will need to a) Login to the NAS as user admin and port forward 8888:127.0.0.1:32400 (Putty will show it as L8888 I believe for ‘Local’)
  3. If using SSH itself ssh -L 8888:127.0.0.1:32400 -l admin ip.addr.of.syno
  4. sign in and let the shell session sit idle, we only need the tunnel.
  5. Now, in an in-cognito window, open http://127.0.0.1:8888/web
  6. This will bring you to the Got It and Sign In windows.
  7. Proceed through until you arrive at the dashboard.

Should you ever need to connect with PMS again and re-claim/re-authenticate, you will need do this.

If you can make the home LAN a proper RFC-1918 LAN, you are much better served. I had always thought RFC-1918 LAN addressing was common in your part of the world.

6

jak_jak, even though you’re presumably behind a NAT firewall, you still have a slim possibility of some oddball networking problems cropping up. Probably the biggest would be when you’re attempting to connect to some DNS named service, and name resolution comes back with an IP address hosted on your internal network. In that case, you’ll be chasing failure to connect, timeouts and other similar issues.

ChuckPA’s comment about going to a proper RFC1918 non-routable test network are dead-on. Personally, I cannot conceive of a valid reason to use a public IP address range.

7

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.