PLEX server indirect/remote

[SPARKZ]

so i have a mini PC running proxmox, ubuntu VM with docker running plex in a container, network mode is bridge on the container. i cant get plex on my local devices to show as direct and as such playing anything is chewing up my bandwith as its all going out to their relay servers.

i know very little about docker and pretty much used a compose file off github. i had plex running on my synology NAS (app) not container, up until now and it was working fine.

docker subnet - 172.28.10.0
LAN subnet - 28.28.28.0
docker pc - 28.28.28.48

looking online/reddit i saw some posts about setting up a static route between the two subnets and in my mind it does seem like a routing issue, i just need them to be able to see eachother.

i have played around with the static route page, set up a gateway for the docker subnet and set up a route. this actaully allows me to open the containers on my main PC using the docker PC IP and the containers port so im getting somewhere or nowhere i really dont know.

i feel like there is a simple solution to this as many people run plex in a container with no issues.

any suggestions would be very apprecitated as im running out of reddit posts to help me   

[caplam]

are these ip the ones you are using?
you can't use 28.28.28.0/24 for your lan it's a public ip. You may face a lot of issues using these ip.
 

[cookiemonster]

This seems a question about docker containers and as such probably belongs in some other forum/site.

[meyergru]

No, you cannot use 28.28.28.0/24 as a private LAN.

And how to address docker containers in bridged mode is not up to OpnSense, you have to do that on the docker host.

The bridged network can only be seen on the docker host itself and you cannot access it from outside unless you expose some services via host ports. From inside to out, there is usually a masquerading rule such that the docker host will appear as the sender of packets. Thus, all of your containers will have internet access via NAT (on the docker host) and will be accessible via their repective exposed ports on the docker host.

You should not route docker local networks anywhere. To map exposed ports to container-internal ports is exactly what the "-p" option is for: https://docs.docker.com/get-started/docker-concepts/running-containers/publishing-ports/.

That is just how docker will be set up per default when you install it on, say, Debian or Ubuntu.

If you have many containers and want to make them addressable by name instead of port numbers, there are docker-specific reverse proxies like Traefik.