Public and private shared content between devices, including whitelisting IPs
Posted: Tue Feb 14, 2023 7:37 pm
I'm trying to figure out the correct way to share content between devices using Whitelisting IPs and configuration for per-device accessing content.
It seems that if I have all the shared content setup through the tab of the -old- UI it cannot be hidden even if I use the per device configuration file setting of folders. Meaning that all shared content is visible to all devices.
So, when sharing different content per-device, the Shared Folders and the per-device configuration is conflicting each-other?
Are whitelisting IPs in higher position than the per-device configuration in accessing/viewing the shared content ?
Also, when doing changes on per-device configurations and/or shared content, the server should be restarted through UI or closed and reopened the whole application ? Because sometimes the restart fails to restart having a message of port already open.
Finally, after any above changes done, the media-player application on the device should be restarted or the permission changes are automatically pushed to the device with every browse move ?
It seems that if I have all the shared content setup through the tab of the -old- UI it cannot be hidden even if I use the per device configuration file setting of folders. Meaning that all shared content is visible to all devices.
So, when sharing different content per-device, the Shared Folders and the per-device configuration is conflicting each-other?
Are whitelisting IPs in higher position than the per-device configuration in accessing/viewing the shared content ?
Also, when doing changes on per-device configurations and/or shared content, the server should be restarted through UI or closed and reopened the whole application ? Because sometimes the restart fails to restart having a message of port already open.
Finally, after any above changes done, the media-player application on the device should be restarted or the permission changes are automatically pushed to the device with every browse move ?