That’s if QNAP can get the Networking thing sorted out…:)
Which networking thing?
QNAP networking is Just Fine 
lol
I think I have figured out how to make it such that PMS doesn’t get confused.
The ‘trick’ is the enumeration sequence.
- Create the network (Bond) first,
- Add the V-switch to push the IP out, making it the default
- The containers and VMs will fall in line and into the V-switch. They will be NAT uncoupled or Host IP
So is this problem only happening in PMS in Containers and VM’s?
PMS, in a container, on a host which (QNAP) which probably has either 2 or, more likely, 4 adapters, is going to present a problem if you don’t control the network enumeration and architecture.
I do not put PMS in a container on any host where there is a native package for it. It introduces port / networking complexities I have no time or desire to deal with.
Here you see the enumeration sequence and how it looks when illustrated.
Yes, I use PMS as a Native app. I’m going to upgrade the 4.3.5. beta 2 this weekend and play around with the PMS versions.
In 4.3.5 B2, you’ll spot the network adapter enumeration changes.
Those are the current issue for most.
It will work flawlessly or it won’t work at all. It’s 50/50.
I have all the previous version of PMS so I can roll back as needed.
The new QNAP builds are now available as Forum Preview.
- Volume selection & Migration as promised
- Known packaging bug we’re working on. (Size is bigger not smaller… ooops)
Thank you! I installed it and migrated the app overnight (took a while 
) to my SSD Raid 1 volume. It made such a big difference! The UI is so much more responsive! If you have a large library, I can only say that moving the Plex App to an SSD volume is a must!
Sebastian,
Would you mind checking the box and marking this as solved?
Thanks,
C
PS: you’ll also find the occasional false Error indication when installing is now gone.
I can’t find where I can mark this as solved. I think the OP can only do that?
Marked as solved 
