2014-08-28, 23:48
configuring by hostname makes more sense to me, having lived/worked for a couple of decades in the industry and dealt with many 1000s of devices/servers that dont always have a static IP. What doesn't make sense to me is that the hostname of your device is set to "localhost" when it's clearly not local to anything other than itself in a network context Also the nature of these devices is that you are likely to end up with more than 1 in the same house/network making it even weirder to not have them named uniquely. If you renamed it to "FireTV1" or whatever, then you could manage multiple devices with unique hostnames and DHCP allocated IP addresses, which don't have to be static reservations. Anyway as of the latest ServerWMC release you can use IP address for the restrictions again if you prefer (although the device will still identify itself by it's hostname in the ServerWMC logs and so on).
now in terms of your problem, the log file you posted shows no restricti0ons are enabled. This could either be because you haven't set "ClientRestrictionsEnabled" to true, or because you don't actually have any configured (you mentioned a crash, and your config file going back to default).
In terms of this crash, if you can reproduce it and provide clearer instructions on how to reproduce it, and post the log, we can look into that to. Im not sure I currently can see how the config file could be reverted to default.
In terms of media browser stuff, the ^MediaBrowser thing is appended to client names coming from MB3 but ServerWMC still knows it is running on "HTPC" for the server side. Krusty will probably have to answer more fully because I think the way media browser clients are dealt with has changed recently, so there is a legacy way and a new way. The log shows the client name as "'MediaBrowser^HTPC" so you could try configuring a restriction using that client name and seeing if it applies. If you want to restrict just 1 client that is hanging off MediaBrowser im not sure how to do that or whether it's supported
now in terms of your problem, the log file you posted shows no restricti0ons are enabled. This could either be because you haven't set "ClientRestrictionsEnabled" to true, or because you don't actually have any configured (you mentioned a crash, and your config file going back to default).
In terms of this crash, if you can reproduce it and provide clearer instructions on how to reproduce it, and post the log, we can look into that to. Im not sure I currently can see how the config file could be reverted to default.
In terms of media browser stuff, the ^MediaBrowser thing is appended to client names coming from MB3 but ServerWMC still knows it is running on "HTPC" for the server side. Krusty will probably have to answer more fully because I think the way media browser clients are dealt with has changed recently, so there is a legacy way and a new way. The log shows the client name as "'MediaBrowser^HTPC" so you could try configuring a restriction using that client name and seeing if it applies. If you want to restrict just 1 client that is hanging off MediaBrowser im not sure how to do that or whether it's supported