Version 3.4.0.0 DLNA not working

[rb07 0]

Hi,

 

I just installed the latest version available (3.4.0) for my Synology NAS, and everything seems fine except that the DLNA server is not seen by any device.

 

No problem with the installation, server shows "running" and the Web part, media scanning, etc. is fine.  Also the firewall on the NAS should be configured correctly (which is part of the installation, opening the 4, or 5 ports).  On the same NAS I have other DLNA servers that have no problem working (Serviio, Plex); of course I stopped them before the installation, and there are other servers claiming port 1900, Synology's own AudioStation, and there's a minissdpd, but Serviio, for instance, works fine with those running.

 

I did try several tests:

 

1.  Emby's own rundiags, no real problem found, but several oddities: CPU 0 is marked as disabled, it is not, it finds several copies of ffmpeg, ffprobe (but Emby's log say its using its own, and this has nothing to do with DLNA).

 

2. Since my TV didn't find the server, and also Windows didn't show it, I tried to connect Kodi from my PC, but it doesn't detect the DLNA server.  Same for Device Spy.

 

3. I deleted the installation, and did it again.  No change.

 

4. I started changing settings, enabling debug logs, specifying bind address (Emby is binding to the IPv6 address, which I think is mostly useless, the TV uses only IPv4), setting the default user.

 

The log does show that Emby finds the TV, and identifies it correctly.  But it was Emby finding the TV, not the other way around.  Nothing else in the log points to an obvious problem, but there are lots of messages like this (for each device on my LAN):

 

2018-05-04 19:27:31.279 Error HttpServer: Could not find handler for /dlna/9ff1b741560944b0bdeb8499f7c80d9e/description.xml
2018-05-04 19:27:31.279 Info HttpServer: HTTP Response 404 to 192.168.10.5. Time: 14ms. http://192.168.10.4:8096/dlna/9ff1b741560944b0bdeb8499f7c80d9e/description.xml 
2018-05-04 19:27:31.279 Info HttpServer: HTTP Response 404 to 192.168.10.50. Time: 6ms. http://192.168.10.4:8096/dlna/9ff1b741560944b0bdeb8499f7c80d9e/description.xml 

404 is the "not found" error message.

 

Anyway I'm attaching a copy of the log, maybe somebody can spot the problem.

 

TIA

 

Emby Log.7z

Edited May 5, 2018 by rb07

[Luke 38831]

hi @@rb07, apologies. I see the problem and it is only affecting the Synology builds right now. We'll get a new release out by Monday to address this. It may also be available on the beta channel prior to that. Thanks.

[GiTo 0]

Same happened to me, I also did a reinstallation, tried some configuration changes, nothing helped. The DLNA isn´t shown either on my Samsung TV or  my Windows 10 PC or other LAN-Devices.

 

Also got the 404-Errors (IP´s edited):

 

 

2018-05-05 07:53:44.178 Info HttpServer: HTTP Response 404 to 192.168.XXX.XXX. Time: 1ms. http://192.168.XXX.XXX:8096/dlna/d4b4a408b95a499db8dcbe95ebad125b/description.xml 

2018-05-05 07:53:59.978 Info Dlna: DLNA Session created for [TV] Samsung 6 Series (55) - UE55KU6510

2018-05-05 07:54:03.438 Info HttpServer: HTTP GET http://192.168.XXX.XXX:8096/dlna/d4b4a408b95a499db8dcbe95ebad125b/description.xml. UserAgent: DLNADOC/1.50 SEC_HHP_[TV] Samsung 6 Series (55)/1.0 UPnP/1.0

2018-05-05 07:54:03.438 Error HttpServer: Could not find handler for /dlna/d4b4a408b95a499db8dcbe95ebad125b/description.xml

2018-05-05 07:54:03.439 Info HttpServer: HTTP Response 404 to 192.168.XXX.XXX. Time: 1ms. http://192.168.XXX.XXX:8096/dlna/d4b4a408b95a499db8dcbe95ebad125b/description.xml 

2018-05-05 07:54:03.536 Info HttpServer: HTTP GET http://192.168.XXX.XXX:8096/dlna/d4b4a408b95a499db8dcbe95ebad125b/description.xml. UserAgent: DLNADOC/1.50 SEC_HHP_[TV] Samsung 6 Series (55)/1.0 UPnP/1.0

2018-05-05 07:54:03.537 Error HttpServer: Could not find handler for /dlna/d4b4a408b95a499db8dcbe95ebad125b/description.xml

2018-05-05 07:54:03.538 Info HttpServer: HTTP Response 404 to 192.168.XXX.XXX. Time: 1ms. http://192.168.XXX.XXX:8096/dlna/d4b4a408b95a499db8dcbe95ebad125b/description.xml 

2018-05-05 07:54:03.635 Info HttpServer: HTTP GET http://192.168.XXX.XXX:8096/dlna/d4b4a408b95a499db8dcbe95ebad125b/description.xml. UserAgent: DLNADOC/1.50 SEC_HHP_[TV] Samsung 6 Series (55)/1.0 UPnP/1.0

2018-05-05 07:54:03.636 Error HttpServer: Could not find handler for /dlna/d4b4a408b95a499db8dcbe95ebad125b/description.xml

 

Would be great if we can get a fast solution

 

Thank you for your support

 

GiTo

Edited May 5, 2018 by GiTo

[rb07 0]

Hi @@Luke,

 

Thanks for your reply.  I will do a reinstall on Monday.

[Luke 38831]

 

Same happened to me, I also did a reinstallation, tried some configuration changes, nothing helped. The DLNA isn´t shown either on my Samsung TV or  my Windows 10 PC or other LAN-Devices.

 

Also got the 404-Errors (IP´s edited):

 

 

2018-05-05 07:53:44.178 Info HttpServer: HTTP Response 404 to 192.168.XXX.XXX. Time: 1ms. http://192.168.XXX.XXX:8096/dlna/d4b4a408b95a499db8dcbe95ebad125b/description.xml 

2018-05-05 07:53:59.978 Info Dlna: DLNA Session created for [TV] Samsung 6 Series (55) - UE55KU6510

2018-05-05 07:54:03.438 Info HttpServer: HTTP GET http://192.168.XXX.XXX:8096/dlna/d4b4a408b95a499db8dcbe95ebad125b/description.xml. UserAgent: DLNADOC/1.50 SEC_HHP_[TV] Samsung 6 Series (55)/1.0 UPnP/1.0

2018-05-05 07:54:03.438 Error HttpServer: Could not find handler for /dlna/d4b4a408b95a499db8dcbe95ebad125b/description.xml

2018-05-05 07:54:03.439 Info HttpServer: HTTP Response 404 to 192.168.XXX.XXX. Time: 1ms. http://192.168.XXX.XXX:8096/dlna/d4b4a408b95a499db8dcbe95ebad125b/description.xml 

2018-05-05 07:54:03.536 Info HttpServer: HTTP GET http://192.168.XXX.XXX:8096/dlna/d4b4a408b95a499db8dcbe95ebad125b/description.xml. UserAgent: DLNADOC/1.50 SEC_HHP_[TV] Samsung 6 Series (55)/1.0 UPnP/1.0

2018-05-05 07:54:03.537 Error HttpServer: Could not find handler for /dlna/d4b4a408b95a499db8dcbe95ebad125b/description.xml

2018-05-05 07:54:03.538 Info HttpServer: HTTP Response 404 to 192.168.XXX.XXX. Time: 1ms. http://192.168.XXX.XXX:8096/dlna/d4b4a408b95a499db8dcbe95ebad125b/description.xml 

2018-05-05 07:54:03.635 Info HttpServer: HTTP GET http://192.168.XXX.XXX:8096/dlna/d4b4a408b95a499db8dcbe95ebad125b/description.xml. UserAgent: DLNADOC/1.50 SEC_HHP_[TV] Samsung 6 Series (55)/1.0 UPnP/1.0

2018-05-05 07:54:03.636 Error HttpServer: Could not find handler for /dlna/d4b4a408b95a499db8dcbe95ebad125b/description.xml

 

Would be great if we can get a fast solution

 

Thank you for your support

 

GiTo

 

 

We will get a new update out by Monday to address this, thanks.

[russpurg 0]

Hi all,

I was hoping to do some binge watching this weekend.  How can I downgrade my Emby server on my Synology NAS until this gets fixed?

[shihjay2 0]

Just also wanted to report this is also the same DLNA behavior (Emby server not seen by other DLNA capable devices) since upgrading to 3.4.0.0 which is installed on an Arch Linux server.

[Luke 38831]

Just also wanted to report this is also the same DLNA behavior (Emby server not seen by other DLNA capable devices) since upgrading to 3.4.0.0 which is installed on an Arch Linux server.

Actually it's not. If you're using our official arch Linux package then it won't be affected by this.

[russpurg 0]

Hi Luke,

Is there a way to downgrade until this gets fixed.   I can't seem to get access to the repository directly to download a package.  I'd like to do some binge watching this weekend.

[Luke 38831]

The repository is currently the only place where the packages are hosted. I would just give it a try again later.

[shihjay2 0]

On Arch Linux the version for the community package is 3.3.0.1; what I was referring to was version 3.4.0.0; however, upgrading to 3.4.0.3 beta using AUR did fix the problem;

[Luke 38831]

Ok thanks for the info. I would suggest trying our official package as it will perform better, and it's what we're testing.

[tchirou 23]

Hi

Do you know when the fix will be available in the stable version ?

Thanks

[Luke 38831]

Today.

[tchirou 23]

Today.

Great ! Ups just called and is going to deliver my oculus go in a few minutes so I really need DLNA [emoji1303]

Thanks a lot

[tchirou 23]

Hi

The server says a new version is available but there is no update on the package center in DSM. I rebooted the NAs several times to trigger the update but no luck.

Is there a way to get the spk to install it manually instead of waiting for it ? This is a hot fix

 

Thanks

[Luke 38831]

I think we just have to wait for solabc16 to publish the new release. Thanks.

[tchirou 23]

Ok thanks

[GiTo 0]

Installed and working!   Well done, thank you!

[Luke 38831]

Thanks for the feedback.