Updated to 10.9.3 and now can't find Jellyfin as a UPNP service

[merulius]

Thank you for posting. I'm going round and round with this.

It does seem that the move to DLNA as a plug-in was the start of the problem. 

I'm up-to-date with the jellyfin updates (Ubuntu), and although there was an update last night, nothing has changed.

I'm having similar, after updating from a container that was 6 months old and now moving to the version where dlna is a plugin i cannot see the server from my devices, mostly with an lg webos tv. i can see in the jellyfin admin dashboard that it sees my tv and another device but jellyfin is not showing up on the tv's media browser. I've tried setting the bind address in the networking options and it hasnt helped. I initially had to update the profile xml in the plugin folder for lg tv's so now its loading the proper profile, before i edited the profile xml it would post in the log it was using the default profile settings.

this had been working previously, so unless some requirements have changed i dont expect anything on my network to be the cause. i have no firewall enabled on the server and the docker container is set to host networking

edit: i spun up a separate docker container with the old version on the same server and it appears to be working as i can see the directory on my tv again. in the log on the old version which is 10.8.13, im seeing this line which i was not seeing in the new version
Emby.Dlna.ContentDirectory.ContentDirectoryService: StreamBuilder.BuildVideoItem( Profile=LG Smart TV,

There appear to be a number of issues within the past weeks logged on the dlna plugin github (https://github.com/jellyfin/jellyfin-plugin-dlna/issues) for discoverability issues. I guess i'll be running the old version container alongside the updated one to allow viewing on my tv in the mean time while the dev works on getting dlna working again.