Remote access no longer works when I have more than one NIC (network card)

Plex Media Server NAS & Devices
1

Hi all, I’m up against a strange one.
I have a Synology DS2411+ and has 2 ethernet ports, eth0 and eth1
I’ve been using Plex remotely for years without a problem.
Just recently I upgraded to a more recent version of Plex and I now have the following problem.

  • Plex will default to eth1 and not eth0
  • My internal camera network is isolated on eth1 and there is no external/internet access.
    I have always run everything from eth0 and there has never been a problem.
  • eth0 has external access, not eth1
    If I choose the settings > server > network >Network interface to listen on to All or just eth1 it will only use eth1.
    Under server / remote access > enable remote access, the private IP is always eth1. If I disconnect eth1 and reboot, it still shows eth1.
    I like this new feature where you can select the network interface to listen on, but it does not work.
    I’m running 1.13.5.5291 but have also changed to the public beta and I still have the same problem.

I have also removed the plex from /volume1 and i still haver the same problem.

Any advice is always welcome.

Thanks in advance,

Mr J

3

Thanks for the reply.
I’m on the same subnet (wired) and not connecting remotely
The eth0 interface was selected and saved. The note below this setting mentioneds that the server needs to be restarted. I restarted the server. I’ve also restarted the Synology box.
If I ssh to the server, rename the Preferences.xml to *.bck and reinstall, I have the same problem.
The Preferences.xml did contain the ‘eth0’ but it still uses eth1
I’ve also mv /volume1/Plex to /volume1/Plex.old and reinstalled. When I install Plex (manually also) the same problem occurs.

I’m happy to share some logs or anything useful.

Thanks in advance.

Mr J

5

thanks for the update. I have pressed save and it mades no difference.
Let me confim the steps again.

  1. Connect to the Plex server using plex.app on the Mac (High Sierra)
    (the plex.app client is kept current)
  2. Select Settings -> Server -> Remote Access
  3. ‘Not available outside you network is selected’
  4. Private IP is showing my Camera network ‘eth1’ on my Synology
  5. Select Network
  6. Network interface to listen on eth0 (10.0.0.10)
  7. Select SAVE CHANGES
  8. Plex is restarted via Packages Stop/Start
  9. Setting Server -> Remote Access (red !)
  10. Try to enable remote access and get the message not available outside you network.

Preferences.xml
LastAutomaticMappedPort=“0” ButlerUpdateChannel=“8” LanguageInCloud=“1” ServerBindInterface=“eth0” ManualPortMappingMode=“1” secureConnections=“0”

I’ve used plex for 10 years now and have had very few problems. I will only contact the forum after all my other options have been exausted. I can create a video to show you the steps if you think something is missing?

I have repeated all these steps using Chrome Version 68.0.3440.106 and have the same problem.

Thanks,

Mr J

7

Are you able to confirm that this is unusual behaviour.
I have been able to use plex.tv to connect to the box (a few months ago) without a port forward.
Port forward is actually set.
The original question was about the wrong interface being used.

this used to work and no longer work after some more recent updates.

thanks in adavnce

9

So I have tried the latest beta (that provides the option to select the interface), we have also tried the public release which does not have the option (the optin still exisits in the Preferences.xml). We went into the Preferences.xml, changed the ServerBindInterface=“eth0” and still no luck.

We have also tried the follwoing:
eth0 = 10.0.0.10
dns 8.8.8.8
set as the default gateway
eth1 = 10.0.55.10

  1. Disconnect the eth1 (second ethernet) and rebooted. (this connection has been removed for 2 days now)
  • the server still shows the 10.0.55.10
  1. Rebooted the Synology and my fortigate switch.
  2. Switched the eth0 and eth1 ip addresses, still the same problem, it binds to the 10.0.55.10 in ALL situations.
  3. Edited the Preferences.xml to eth0, stop/started and to eth1 stop/started, still no change. it is like it is being ignored.
  4. Installed the original ISP router, which is set to allow everything outbound (this would at least support the plex.tv connection without requiring port forwarding) this does not work also.

Also on the same ISP and they do not block traffic.

I’m now lost, it used to work. I’m more than happy to backup the Library directory and completely remove from my system. At this point I can try to create a new install from scratch. It is worth noting that the Synoloigy install will only allow for an install to the original volume '/volume1 and not another volume. If I try this, it fails. Details on how to remove eveything woudl help.

I’m now going to accept that must be a bug, and wait until someone else flags it to get your attention. I’ve been a customer for 10 years and have recommended it to my friends, We produce vlogs so not having the remote access for our clients has been extremely limiting.

We will resort to the traditonal fire transfer for now.

Thanks,

Mr J

10

Just to be clear:
Currently using: Version 1.13.4.5271
The Beta PlexMediaServer-1.13.5.5291-6fa5e50a8-x86_64 has also be used a number of times, removed reinstalled and still the same problem.

In May this year, eveything was working well, the upgrades have caused this problem.
At the very least, I should be able to use the Plex.tv connection instead of a port forward and this does not work also.

Thanks,

Mr J

11

May I assist?

May I have the server logs (DEBUG logging only - not VERBOSE),
A quick screenshot of the settings details for each of your two adapters (expanded view) ?

12

Thanks Chuck.

Heplex-log.txt (46.3 KB)

eth1%20-%20JumboStation%C2%A0-%C2%A0Synology%C2%A0DiskStation
eth1%20-%20JumboStation%C2%A0-%C2%A0Synology%C2%A0DiskStation821×609 55.5 KB
eth0%20-%20JumboStation%C2%A0-%C2%A0Synology%C2%A0DiskStation
eth0%20-%20JumboStation%C2%A0-%C2%A0Synology%C2%A0DiskStation886×564 48.9 KB
after%20disable%20remote%20access%20-%20Plex_Media_Player
after%20disable%20remote%20access%20-%20Plex_Media_Player908×551 98.7 KB
after%20enable%20remote%20access%20Plex_Media_Player
after%20enable%20remote%20access%20Plex_Media_Player922×542 109 KB
re goes:

13

Thanks. I found your problem.

IP: 10.0.55.11
Gateway: 10.0.55.1 – which is NOT an internet gateway. This field should be empty.

14

As separate resolution method:

  1. eth0 is the first adapter Plex always finds. Make it the internet gateway connection
  2. eth1 can be LAN-only without harm

(swap them)

In either case, if the adapter does not have have an ethernet connection, it does not get a “Gateway” address value

15

Hi Chuck,

The gateway on the 10.0.55.1 eth1 has been removed.

  • I still have the same problem, The Synology was also restarted.
    Earlier on in the thread, I’ve mentioned that swapping the adapters makes no difference.
    I’ve also disconnected the eth1 (port 2) on the Synology, rebooted and shows ‘Disconnected’, still the same problem.

Very strange indeed.

Thanks.

16

I’m doing a little experimenting myself.

Care to grab me a fresh set of logs please?

17

Sure thing, here goes.
Thanks
fresh-log-plex.txt (105.6 KB)

18

Sorry, wrong type :smiley:

Settings - Server - Help - Download Logs.

Attach the ZIP

19

sure, can I PM these to you, or upload somewhere, there is some PII info in the logs etc.

cheers

20

Enabled. PM away

21

In the future, Please keep Verbose OFF until requested. I get to see a lot more data. Verbose logging only gives 1-2 minutes in the entire set. The Verbose lines waste log space at this level. I got 5 useful lines out of that block. This is why we request it off until needed.

Example:

Aug 13, 2018 12:51:14.926 [0x7fa7cd911700] DEBUG - Auth: authenticated user 1 as JR68000
Aug 13, 2018 12:51:14.926 [0x7fa7cd911700] VERBOSE - Auth: Came in with a super-token, authorization succeeded.
Aug 13, 2018 12:51:14.927 [0x7fa7c7911700] DEBUG - Request: [10.0.10.101:52283 (Subnet)] GET / (8 live) TLS GZIP Signed-in Token (JR68000)
Aug 13, 2018 12:51:14.927 [0x7fa7c7911700] VERBOSE -  * Host => 10-0-10-10.d08231af44c74bd29d43970e85dc60fa.plex.direct:32400
Aug 13, 2018 12:51:14.927 [0x7fa7c7911700] VERBOSE -  * Connection => keep-alive
Aug 13, 2018 12:51:14.927 [0x7fa7c7911700] VERBOSE -  * Accept => text/plain, */*; q=0.01
Aug 13, 2018 12:51:14.927 [0x7fa7c7911700] VERBOSE -  * Accept-Language => en
Aug 13, 2018 12:51:14.927 [0x7fa7c7911700] VERBOSE -  * User-Agent => PlexMediaPlayer 2.16.0.885-f2338b5e (macosx-x86_64 10.13)
Aug 13, 2018 12:51:14.928 [0x7fa7c7911700] VERBOSE -  * Accept-Encoding => gzip, deflate, br
Aug 13, 2018 12:51:14.928 [0x7fa7c7911700] VERBOSE -  * X-Plex-Client-Capabilities => protocols=shoutcast,http-video;videoDecoders=h264{profile:high&resolution:2160&level:52};audioDecoders=mp3,aac,dts{bitrate:800000&channels:8},ac3{bitrate:800000&channels:8}
Aug 13, 2018 12:51:14.928 [0x7fa7c7911700] VERBOSE -  * X-Plex-Client-Identifier => 8v1a5sgju7qsu0620g9wl8fr
Aug 13, 2018 12:51:14.928 [0x7fa7c7911700] VERBOSE -  * X-Plex-Device => OSX
Aug 13, 2018 12:51:14.928 [0x7fa7c7911700] VERBOSE -  * X-Plex-Device-Name => XXXXX 
Aug 13, 2018 12:51:14.928 [0x7fa7c7911700] VERBOSE -  * X-Plex-Device-Screen-Resolution => 1280x840,1680x1050
Aug 13, 2018 12:51:14.929 [0x7fa7c7911700] VERBOSE -  * X-Plex-Language => en
Aug 13, 2018 12:51:14.929 [0x7fa7c7911700] VERBOSE -  * X-Plex-Model => 10.13
Aug 13, 2018 12:51:14.929 [0x7fa7c7911700] VERBOSE -  * X-Plex-Platform => Konvergo
Aug 13, 2018 12:51:14.929 [0x7fa7c7911700] VERBOSE -  * X-Plex-Platform-Version => 2.16.0.885-f2338b5e
Aug 13, 2018 12:51:14.929 [0x7fa7c7911700] VERBOSE -  * X-Plex-Product => Plex Media Player
Aug 13, 2018 12:51:14.929 [0x7fa7c7911700] VERBOSE -  * X-Plex-Token => xxxxxxxxxxxxxxxxxxxx
Aug 13, 2018 12:51:14.930 [0x7fa7c7911700] VERBOSE -  * X-Plex-Version => 3.63.1
Aug 13, 2018 12:51:14.930 [0x7fa7c7911700] VERBOSE -  * X-Plex-Client-Identifier => 8v1a5sgju7qsu0620g9wl8fr
Aug 13, 2018 12:51:14.930 [0x7fa7c7911700] VERBOSE -  * X-Plex-Device-Screen-Resolution => 1280x840,1680x1050
Aug 13, 2018 12:51:14.930 [0x7fa7c7911700] VERBOSE -  * X-Plex-Version => 3.63.1
Aug 13, 2018 12:51:14.930 [0x7fa7c7911700] VERBOSE -  * X-Plex-Client-Capabilities => protocols=shoutcast,http-video;videoDecoders=h264{profile:high&resolution:2160&level:52};audioDecoders=mp3,aac,dts{bitrate:800000&channels:8},ac3{bitrate:800000&channels:8}
Aug 13, 2018 12:51:14.930 [0x7fa7c7911700] VERBOSE -  * X-Plex-Product => Plex Media Player
Aug 13, 2018 12:51:14.930 [0x7fa7c7911700] VERBOSE -  * X-Plex-Platform => Konvergo
Aug 13, 2018 12:51:14.931 [0x7fa7c7911700] VERBOSE -  * X-Plex-Platform-Version => 2.16.0.885-f2338b5e
Aug 13, 2018 12:51:14.931 [0x7fa7c7911700] VERBOSE -  * X-Plex-Device => OSX
Aug 13, 2018 12:51:14.931 [0x7fa7c7911700] VERBOSE -  * X-Plex-Device-Name => XXXXXXX 
Aug 13, 2018 12:51:14.932 [0x7fa7c7911700] VERBOSE -  * X-Plex-Model => 10.13
Aug 13, 2018 12:51:14.932 [0x7fa7c7911700] VERBOSE -  * X-Plex-Token => xxxxxxxxxxxxxxxxxxxx
Aug 13, 2018 12:51:14.932 [0x7fa7c7911700] VERBOSE -  * X-Plex-Language => en
Aug 13, 2018 12:51:14.938 [0x7fa7c7911700] DEBUG - (Capabilities) Platform 'Konvergo' not matched by plugin platform requirements
Aug 13, 2018 12:51:14.941 [0x7fa7c7911700] DEBUG - (Capabilities) Platform 'Konvergo' not matched by plugin platform requirements
Aug 13, 2018 12:51:14.944 [0x7fa7c7911700] VERBOSE - It took 0.0 sec to serialize a list with 23 elements.
Aug 13, 2018 12:51:14.954 [0x7fa7cd911700] DEBUG - Completed: [10.0.10.101:52283] 200 GET / (6 live) TLS GZIP 27ms 2382 bytes (pipelined: 3)
Aug 13, 2018 12:51:14.998 [0x7fa7cd911700] VERBOSE - Auth: We found auth token (xxxxxxxxxxxxxxxxxxxx), enabling token-based authentication.
Aug 13, 2018 12:51:14.999 [0x7fa7cd911700] DEBUG - Auth: authenticated user 1 as JR68000
Aug 13, 2018 12:51:14.999 [0x7fa7cd911700] VERBOSE - Auth: Came in with a super-token, authorization succeeded.
Aug 13, 2018 12:51:15.000 [0x7fa7c7bff700] DEBUG - Request: [10.0.10.101:52297 (Subnet)] GET /:/websockets/notifications (6 live) TLS GZIP Signed-in Token (JR68000)
Aug 13, 2018 12:51:15.000 [0x7fa7c7bff700] VERBOSE -  * Host => 10-0-10-10.d08231af44c74bd29d43970e85dc60fa.plex.direct:32400
Aug 13, 2018 12:51:15.000 [0x7fa7c7bff700] VERBOSE -  * Connection => Upgrade
Aug 13, 2018 12:51:15.001 [0x7fa7c7bff700] VERBOSE -  * Pragma => no-cache
Aug 13, 2018 12:51:15.001 [0x7fa7c7bff700] VERBOSE -  * Cache-Control => no-cache
Aug 13, 2018 12:51:15.001 [0x7fa7c7bff700] VERBOSE -  * Upgrade => websocket
Aug 13, 2018 12:51:15.001 [0x7fa7c7bff700] VERBOSE -  * Origin => file://
Aug 13, 2018 12:51:15.001 [0x7fa7c7bff700] VERBOSE -  * Sec-WebSocket-Version => 13
Aug 13, 2018 12:51:15.001 [0x7fa7c7bff700] VERBOSE -  * User-Agent => PlexMediaPlayer 2.16.0.885-f2338b5e (macosx-x86_64 10.13)
Aug 13, 2018 12:51:15.001 [0x7fa7c7bff700] VERBOSE -  * Accept-Encoding => gzip, deflate, br
Aug 13, 2018 12:51:15.002 [0x7fa7c7bff700] VERBOSE -  * Sec-WebSocket-Key => JSfv4LVgGmjbfYgbVBi56A==
22

got it, that was my concern.
I wan’t sure where i turn verbose off, as it is an oiption on the web part.

23

Settings - Server - General . Always a nice place to start :slight_smile:

24

yes, i see it, verbose logging. Will switch it off. Cheers