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

[merulius]

If this helps, the discovery and upnp works in the network, with speakers such as Sonos being found. But in the web version of Jellyfin, the "play through" button (top right) doesn't give those options (and I think it used to).

[TheDreadPirate]

So the problem isn't that you can't find Jellyfin through service discovery, its that you can't find other devices in Jellyfin casting?

If that is the case, IDK. I've never used that functionality besides with Chromecasts/Android TVs.

[merulius]

It's both.

From, say, VLC on my laptop on the same network as the server, I cannot see Jellyfin. From the Jellyfin web front end, I cannot see the Sonos or Naim speakers (as I can from the laptop).

So something is broken in upnp/DLNA on the server. I need to know how to diagnose that.

I have tried restarting both Unifi devices in the network (the router and the meshed device), with no benefit.

I'm going to find some server tools to check out upnp. Will report back.

So the problem isn't that you can't find Jellyfin through service discovery, its that you can't find other devices in Jellyfin casting?

If that is the case, IDK.  I've never used that functionality besides with Chromecasts/Android TVs.

[disgustipated]

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.

[merulius]

What are the contents of /etc/jellyfin/network.xml?

Code:

<?xml version="1.0" encoding="utf-8"?>
<NetworkConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <BaseUrl />
  <EnableHttps>false</EnableHttps>
  <RequireHttps>false</RequireHttps>
  <CertificatePath>/Users/stephen/Documents/balrog.cer</CertificatePath>
  <InternalHttpPort>8096</InternalHttpPort>
  <InternalHttpsPort>8920</InternalHttpsPort>
  <PublicHttpPort>8096</PublicHttpPort>
  <PublicHttpsPort>8920</PublicHttpsPort>
  <AutoDiscovery>true</AutoDiscovery>
  <EnableUPnP>true</EnableUPnP>
  <EnableIPv4>true</EnableIPv4>
  <EnableIPv6>false</EnableIPv6>
  <EnableRemoteAccess>true</EnableRemoteAccess>
  <LocalNetworkSubnets />
  <LocalNetworkAddresses />
  <KnownProxies />
  <IgnoreVirtualInterfaces>true</IgnoreVirtualInterfaces>
  <VirtualInterfaceNames>
    <string>veth</string>
  </VirtualInterfaceNames>
  <EnablePublishedServerUriByRequest>false</EnablePublishedServerUriByRequest>
  <PublishedServerUriBySubnet />
  <RemoteIPFilter />
  <IsRemoteIPFilterBlacklist>false</IsRemoteIPFilterBlacklist>
</NetworkConfiguration>

---

All looks right to me.

[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.

[merulius]

Update: I have tried a couple of the solutions that were posited on Github for the DLNA plugin, which involved editing network.xml. None of these worked. I have the avahi-daemon working, so auto-discovery should work - and does - for adding (eg) scanners. Actually forget the scanner, that was plugged into the server as USB. But the printer was on the network.

So what might be blocking my view (from the server) of the Sonos and Naim speakers, which are all on the same net- and sub-net (there is only one subnet)?

[merulius]

Minor progress

I edited the /etc/avahi/avahi-daemon.conf file. I added a line for the domain name of the server. Avahi is the UpNp server (aka Bonjour) on Ubuntu (and other flavours of Linux). It appears to have very few options set, hinting that more setup is needed.

Web jellyfin now shows the Naim server in the "Play on" button and it works. (for context, the macbook is playing jellyfin on Brave browser, jellyfin is running on a ubuntu server, and the naim speaker, are all on the same network.)

The Sonos speaker is still not showing, despite identifying as upnp on MacOS Music and VLC.

The problem might well be in the network and upnp rather than Jellyfin, although there are a number of community posts that tell of problems in this area, starting from the time that DLNA became a plug-in.

[merulius]

Yes, the Sonos speaker is showing. Took a while.

[TheDreadPirate]

Huzzah! Glad you figured it out cause I had no idea.