My Plex Server is set up on a VM in VirtualBox.
I don’t know why but the VM has two NICs. One is NAT and the other is bridged and it won’t run with just the bridged NIC.
NIC1 (NAT): 10.0.2.15
NIC2 (Bridged): 192.168.188.15
Now my LAN is set to 192.168.188.0/24
I’m not sure why it needs that NAT interface because my Plex Server is reachable through 192.168.188.15
But only if that NAT interface is activated
However. In my Plex Server I set the preferred network interface to the 192.168.188.15
But in remote access it shows the 10.0.2.15, which is kind of odd because my remote access works but it’s kinda slow.
I put up another post regarding the slow speed (Slow access to libraries) and I’m wondering if that is related to each other.
Anyone have any idea why it won’t take the correct interface for remote access and if that’s the reason it’s taking so long to load my libraries?
Well… this really isn’t a Plex question, it’s a VirtualBox VM networking question. Solve this, and your PMS issues will probably go away.
Caveat:: I stopped running VirtualBox quite some time ago. What I do recall will be dated.
NICs in a VirtualBox VM can be bridged to an host NIC, or set up with a NATted address & network. The latter is handy if you’re tinkering with something you want significant isolation from your house network, but probably isn’t really what you want for a PMS VM. The bridged network connection makes your VM visible on your local network, and this will make PMS visible and usable. Something definitely sounds cranky in your network configuration, I’d log in at the VM console, and look at the routing tables while activating and deactivating NIC1. It sounds like the VM is considering 192.16.188.0/24 to be a remote network for some reason.
Personally, I can’t think of a use case where I’d want both a bridged interface and a NATted interface onto the same local network.
Agreed… but he also says that the NAT interface is required for PMS to be accessible. I’m pretty sure that he’s got some pretty funky network configurations. He almost certainly really only wants the single NIC bridged onto his home network, and the NAT interface configuration should be dropped. I have a funny feeling that his routing table is decidedly strange.
I would start with a new VM and make it bridged-only from the git-go.
Give it a peer address on the LAN. (it can piggy-back the host’s adapter on the same subnet)
Test that VM
Move the mounts and metadata to it after confirmed successful.
After struggling with virtual box I finally moved my whole installation to a new VM on VMWare.
The problems with the NICs are gone now since VMWare works just fine with only the bridged adapter.
