PreferredNetworkInterface ignored for RemoteAccess

Server Version#: 1.14.0.5470
Player Version#:N/A

I have a Linux machine (Ubuntu 14.04) running the latest plex (1.14.0.5470).

It has two local network addresses, xx.xx.xx.85 and xx.xx.xx.86. The .85 network address has an incoming path to service external plex access, the .86 network address doesn’t.

I want plex to preferentially use the .85 network address, but the option Settings-Network-PreferredNetworkInterface appears to have no effect upon the private IP address automatically chosen in Settings-RemoteAccess.

My solution (so far) is to manually down the .86 address (sudo ifconfig), THEN start plex and enable remote access, and THEN bring up the .86 network address.

When plex is restarted, it will (randomly) grab the “wrong” network address, and the Settings-Network-PreferredNetworkInterface does not appear to affect this.

I’ve only recently been having this problem, so I think it might be a recent bug.

Yep. still a problem and will be until Engineering works it out.

Preferred interface is for the HTTP server, not the outbound traffic.
For as much as bind() is desired, it does not exist yet.

Just so you know… the last octet in any address is the host ID, not part of the network / subnet address unless you’re splitting down to within 8-bit blocks.

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