fastknight

Nope - seems to just log all the failed logins which is fair enough - I dont think its been intended for using a public IP - but given how great a system it is it should be!

Its not an experiment to see how quickly it gets hacked - its an experiment to see if it can be a viable media server. If its properly firewalled then I think it will work well. But all the points on it not being hardened are well noted.

Its normal for all servers to be under endless attack though.. Anyway - this thread was about Plex - not about hack attempts which I expect and can fend off with some well crafted firewall rules for filtering on source IPs. I've never tried running unRAID on a public IP before so its interesting to see if it holds up - its just an experiment and no critical data on there - if it can't cope I'll just revert back to Ubuntu. Thanks though.

I have a remote unRAID server that only has a public IP assigned on a dedicated server - I can install the Plex docker ok - but I can't seem to adopt the server into my Plex account when I login through the WebUI. I believe this is because of the public IP address as I seem to remember the first login needs to be on a local subnet before you can then enable remote access in the server settings once its linked to your account. Is there anyway of adopting the server with this configuration - I'm assuming this is something to do with the Plex token? Thanks!

So I started using this Docker which looks really cool, but I had a couple of questions as I don't think its working quite right? 1. Initial install works great - but if I stop the Docker and Start again I never get the WebUI back again? It works great all the way up to me needing to stop/or restart then it never comes back. 2. Where is the config saved? Any updates to the Docker such as changing between Host/Bridge mode reset the Dvblink config. Realise this is still very early - but would appreciate help with this as its working great with my DVB drivers build of Unraid. Thanks,