Add in an outbound firewall rule if you want to block unwanted clients. On a network that has multiple people, advertising plex may not be desirable. In some, it is automatic with DHCP reservations. Most home routers will provide this with just a little setup. Why NOT have that setup? Every networked client knows about DNS. Not a big deal, especially if your network handles name resolution correctly already. Using Kodi or other DLNA controllers and renderers means having to manually enter the plex server hostname (I have internal DNS) 1 time on the controller. I don't use official plex clients - don't like their interfaces. Clients need to know the IP/DNS for the server. This is no different than using ssh, sftp, or samba on a network. It doesn't have avahi installed or running. I do run Plex Server on an ubuntu 14.04 server install. In macOS it gets even better since the Avahi announced Samba server will automatically show up under Shared on the left side panel of the mac file manager. Once that is in place I can open the file manager in Linux > Network and see the Samba Server listed.

If I set up a samba server with avahi-daemon running the clients to this machine cannot 'discover' it automatically unless I create a rvice file in /etc/avahi which looks a lot like the one above except the and are different. But what plex does is create an avahi / plex service announcement file ( rvice ) that apparently looks something like this:Īs I do not use plex all I can do is use Samba as an analogy. All it does is allow another Bonjour / Avahi / Win10 machine access to it by using it's host name with a. Having avahi-daemon running by itself won't do anything automatically. Unless you install and run Avahi, the server will not show upįirst of all Bonjour is an Apple thing and in Linux it's called Avahi. The only known external dependency it has is Avahi (), which is required to provideīonjour-based discovery. While doing something else I stumbled upon this from :

Plex media server ubuntu 14.04