Can you set up Plex server entirely remotely on a NAS?

I recently had a power outage on my Synology NAS and had to wipe the server. I reinstalled Plex and restored the Plex folder from a C2 backup.

However, both Plex Web App and local Server App now do not see the server. There just isn’t anything being displayed (see screenshot) where the server should be. Upon restart, the old server connection was marked “unavailable” and had to be removed.

Now, I also do not see any “claim server message”.

If I log onto the Web App, I am greeted with the old “No Soup for You” logo. Also, there is no “Server” setting under “Settings” in the menu of any app I use.

I have verified via SSH that the server appears to be running fine. It just seems to not be communicating to my Plex account to be registered correctly. I can also access the local Plex App perfectly via URL and IP address.

I should add that I am doing this remotely. Do I, maybe, absolutely have to be on the same local network to set this up? Is there anything I could do via SSH, edit a config file, maybe?

SSH tunnel into the NAS to fake being locally connected. But if I remember it correctly, the SSH server in the NAS might prohibit this (and you can’t change it probably).

Yeah, I tried this. I get a “prohibited” error.

When setting up remotely, you must use SSH tunnel
https://support.plex.tv/articles/200288586-installation/

Scroll down to On a Different Network

Would love to, but that doesn’t work on a Synology NAS. I always get:

“channel 3: open failed: administratively prohibited: open failed”

Use PUTTY and define the port forwarding.
you will need click through to the examples at the bottom

On the Syno, control panel - terminal & SNMP

OK. Will try. Does this also work on macOS? I’m not on a Windows machine here (but probably could rig something, if absolutely necessary.)

on MacOS

ssh -L 8888:127.0.0.1:32400  ip.addr.of.host
  1. Sign in
  2. Let the session sit idle
  3. Open, in the local safari, http://127.0.0.1:8888/web

No go. That’s what produces the aforementioned “open failed” error on a Synology NAS. I could try via PUTTY on Windows, but doubt it would work there.

More info is needed.

The syno is remote?
How are you gaining access to it? which method(s)?

The Syno is remote. Access is through custom domain, via https, or IP (both works). SSH is enabled, but restricted to specific user on alternate port and through keyfile access only (no password). Telnet is deactivated.

You are using the admin username (to which you’ve assigned a password you know) ?

It should respond this way the first time you open it (whether local or remote) IF you have port 22 open (or a port forward from another port)

Chucks-Mac:~ chuck$ ssh -l admin -L 8888:127.0.0.1:32400   192.168.0.21
The authenticity of host '192.168.0.21 (192.168.0.21)' can't be established.
RSA key fingerprint is SHA256:cktpsWLkwQpcvdUdeg+s3UvHzIc+25Irt5hu/igB1tY.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.0.21' (RSA) to the list of known hosts.
admin@192.168.0.21's password: 

Chucks-Mac:~ chuck$ 

If you’ve locked down the syno so hard as I believe you have, you will not be able to setup remotely.

What I show is how Synology sets it up by default: restricted to the admin user.

No, I’m using an alternate user but with admin privileges. Also tried with admin just now, but same problem. Now I’m getting:

channel 3: open failed: connect failed: Connection refused
channel 3: open failed: connect failed: Connection refused

Also tried this, but no change.

Guess I’ll just have to drive over.

I think I replicated what you’re seeing.

admin@moesern:~$ channel 3: open failed: connect failed: Connection refused
channel 3: open failed: connect failed: Connection refused
channel 3: open failed: connect failed: Connection refused
channel 3: open failed: connect failed: Connection refused
channel 3: open failed: connect failed: Connection refused
channel 3: open failed: connect failed: Connection refused

  1. Is port 32400 TCP open in the firewall ?
  2. if so, go grab the plex logs

Chuck, I have no clue what precisely I did. I fiddled with the various parameters in /etc/ssh/sshd_config and now the tunnel thing works via “localhost”.

My best guess is that it eventually worked when I replaced 127.0.0.1 with localhost, but I’m not sure. If I succeed in figuring it out, I’ll post it here.

Thumbs up to your perseverance. :wink:

If you replaced 127.0.0.1 with localhost, one thing comes to mind immediately.

localhost is defined for ipv4 & v6.

Are you a V6-only configuration?

If so, you need enable the v4 stack again. Plex requires is.

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