Utilising non-default interface

[Didenko]

@Volts

Can you directly connect to Plex (http://10.0.20.11:32400/web ) from a host on that network? I wonder if there’s a routing or firewall issue.

Indeed, why didn’t the simple step occurred to me, thank you!

The issue was caused by the “Client Device Isolation” setting turned on on the WiFi portion of the 10.0.20.0/24 network. Connecting from a wired client on that network was immediately successful.

@Volts

May PMS be actually configured to operate only on a non-primary interface?

Not really.

The ADVERTISE_IP and Preferred network interface settings don’t do that.

Multihomed hosts almost never work the way people expect. Without using additional fancy OS-level stuff, there’s no form of source-based or policy-based routing to say “when I talk to X, use this address, but when I talk to Y, use this other address”.

Yeah, that I respectfully disagree with. Tons or products allow to bind to a specific interface as a part of configuration and the rest is in the hands of the a person to decide to go down a rabbit hole.

@Volts

Since you’re already using podman containers, you could configure the container for Plex to be singlehomed and only use the network you want - whether it’s a physical/bridge interface on that network, or a namespace with the subnet/address you want.

I tried that. Since the problem was elsewhere it did not solve the access issue. It also requires root-level container, which is not what I want. At least on my current version of the server, as pasta is not yet shipped with the LTS distro.

@Volts

Does the 10.0.20/24 network have a gateway? Plex does need Internet access for authentication and metadata.

Gateway and access to Plex on the internet was fine.

Really appreciate the tip!