Can't claim remotly an hosted Plex on Synology

Plex Media Server
1

Server Version#: 1.19.4.2893
Player Version#: NA

Hello. I Just installed Plex server into a Synology hosted by Infomaniak
but once I open the remoteIP:32400/web and login with my Plex Account
I just receive a message : Sorry no soup for you.

Tried to disconnect and reconnect.
Restart the Plex server.
Connect to VPN synology.

Nothing is working.
I also tried a SSH tunnel but once I try to connect to localhost tunnel, the page don’t come out.

Help !

2

SSH tunnel is the way to go, you have to be on the same local network (subnet) to claim the server.

4

This is the problem.
How can I be on the same subnet, if I procceed the claim from another network ???

5

Via SSH tunnel if you do it properly :wink:

Scroll down to “On a different network”

6

I tried wit Putty

Session :
RemoteHostIP:22

Connection: SSH: Tunel : Source port: 8888
Destination : localhost:32400

Open the connection, windows logon and I log with my Synology admin

then tried to open localhost:32400/web

is not working

7

Other way round I guess. 32400 source, 8888 destination, no?
Then you open localhost:8888

Not sure about the first part (switched source and dest) but definitely sure about the second. This is also what the guide says.

8

help said:

  • Gateway : ip.address.of.server (here the Remote server IP)
  • Source Port : 8888
  • Destination : localhost:32400 (don’t know if I must leave localhost or put my desktop IP)

Once you have the SSH tunnel set up:

  1. Open a browser window
  2. Type http://localhost:8888/web into the address bar
9

Obviously not what you did :wink:

10

just tried to open http://localhost:8888/web
and it’s not working :frowning:

11

so I tried with a terminal console and apparently “localhost” can’t be resolved by the remote server.

image

@ChuckPa
I there another way to claim this server ?
xml.pref ?
Token to handle with ssh terminal ?

12

All my procedures specifically state: 127.0.0.1
I am mandating the use of the IPv4 loopback interface.

Which version of DSM are you using?

I just tried here locally and see even worse.

[chuck@lizum ~.501]$ ssh -l admin -L 8888:127.0.0.1:32400 192.168.0.23
admin@192.168.0.23's password: 
admin@moesern:~$ hostname
moesern
admin@moesern:~$ uname 
Linux
admin@moesern:~$ uname -a
Linux moesern 3.10.105 #25426 SMP Tue May 12 04:51:33 CST 2020 x86_64 GNU/Linux synology_avoton_1815+
admin@moesern:~$ channel 3: open failed: connect failed: Connection refused
channel 4: open failed: connect failed: Connection refused

This is something new with DSM’s most recent updates.
I will investigate and report back

UPDATE:

  1. DS418j - works as expected with SSH-tunnel
  2. DS1815+ - rejects SSH-tunnel
  3. Ticket created with Synology ( “+” models are different)
13

RS820+ with DSM 6.2.3-25426

14

Any news from Synology about this issue ?

15

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