Upgrade to 4.9.3 generates error and no DLNA devices

[NevRimes 0]

I'm running Emby server on a DS414 and today upgraded to version 4.9.3 (from 4.8.11). 

After the upgrade I can see all my Library music and playlists and the only obvious user issue I can see is that my DLNA playback devices are no longer listed.  Looking in the emby server log however I can see an error  (full error in the log attached) : 

2026-01-12 15:04:38.972 Error Server: Error processing web socket message

*** Error Report ***

Version: 4.9.3.0

............(detail removed).............................

Source: System.Memory

TargetSite: Void ThrowIndexOutOfRangeException()

 

 

Music appears to play fine on the local windows device. I've tried restarting EMBY and rebooting the DS414 but the same issue occurs. 

 

Many thanks

 

embyserver.txt

[Luke 42077]

Hi, what are you expecting to be listed?

[NevRimes 0]

So when I click on the "play on another device" button I now only see This device Emby Web, where as before the upgrade I was seeing my AV Amp and my Oppo player listed as two  DLNA options to play on as well.

[Luke 42077]

Have you checked the remote control permissions for your Emby user?

[NevRimes 0]

Would the upgrade have changed that?   

I only have one user with full access, and yes it does have Remote control access, yes.

I'm more concerned about the error in the log file? or is that a red-herring? 

Edited January 12 by NevRimes

[Luke 42077]

The error in the log is not related to dlna.

[NevRimes 0]

Ok, so 2 issues after 4.9.3 ..  do you know what causes the out of range exception? 

Thanks

[NevRimes 0]

.... although after another restart the embyserver.txt no longer shows any errors any longer.     Unfortunately the "play on" DLNA devices are still not appearing though  

I have confirmed that the DLNA devices are still visible to VLC, Foobar and BubbleuPnP and its just the upgraded Emby that for somereason isn't seeing them. Thats true for the EMBY app on Android and the emby web interface on Win 11. 

[Luke 42077]

Quote

I only have one user with full access, and yes it does have Remote control access, yes.

Hi, can you please show us? 

Also how are DLNA settings configured?

[NevRimes 0]

A screen shot of the user access? like this ?

 

DLNA is all default. It was default with 4.8.11 and I just upgraded and haven't altered anything manually.

 

Is that what you wanted to see? Or something else?

Thanks

 

[Luke 42077]

Have you configured any emby server network settings?

[NevRimes 0]

No, everything is default and certainly nothing was changed between 4.8.11 and 4.9.3. 

 

[NevRimes 0]

Which part of the system is key for finding the DLNA devices?  Is it the Emby web client on PC (or app interface on Android) or is it the Synology NAS where the server is running? I've confirmed that I can see the DLNA devices on my PC and my phone, but is it the NAS that is actually where I need to confirm I can see them?  

Thanks.

[NevRimes 0]

I notice that I'm now seeing lots of errors like this : 

2026-01-16 01:16:44.886 Error App: Error sending socket message from 0.0.0.0:1900 to 239.255.255.250:1900
    *** Error Report ***
    Version: 4.9.3.0
    Command line: /volume1/@appstore/EmbyServer/system/EmbyServer.exe -programdata /var/packages/EmbyServer/var -ffdetect /var/packages/EmbyServer/target/bin/ffdetect -ffmpeg /var/packages/EmbyServer/target/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/bin/ffprobe -defaultdirectory /volume1/Public -updatepackage emby-server-synology7-mono_{version}_armv7_legacy.spk -pidfile /var/packages/EmbyServer/var/EmbyServer.pid -nolocalportconfig -noskia -ignore_vaapi_enabled_flag
    Operating system: Linux version 3.2.101 (root@build2) (gcc version 8.5.0 (GCC) ) #42962 SMP Mon Aug 19 15:11:03 CST 2024
    OS/Process: X86/X86
    Framework: Mono: 6.12.0.199 (tarball Mon Mar  4 05:22:02 PM UTC 2024)
    Runtime: volume1/@appstore/EmbyServer/lib/mono/4.5/mscorlib.dll
    Processor count: 2
    Data path: /var/packages/EmbyServer/var
    Application path: /volume1/@appstore/EmbyServer/system
    System.Net.Sockets.SocketException: System.Net.Sockets.SocketException (0x80004005): Network is unreachable
      at Rssdp.SsdpCommunicationsServer.SendFromSocket (System.Tuple`3[T1,T2,T3] socketTuple, System.Memory`1[T] messageData, System.Net.IPEndPoint destination, System.Threading.CancellationToken cancellationToken) [0x000a9] in <a527f4424fba4a8ebc7e41a2c27b1e0b>:0 
    Source: mscorlib
    TargetSite: Void Throw()

 

Does that have anything to do with the missing DLNA devices?  Thanks

embyserver-63904167712.txt

[Luke 42077]

That could make a difference, although I'm surprised it would be different from 4.8.11. The only way to know for sure would be to make a fresh start with 4.8.11 as you would not be able to roll back your existing installation.

[NevRimes 0]

Make a difference in what way? What is the reason for the errors, what network is unreachable? 

I've been running many previous versions of Emby for years with no issue with DLNA devices and I have several large playlists of music which would be a big headache to recreate from scratch unfortunately.

Edited January 16 by NevRimes

[Luke 42077]

Have you tested to see if your NAS can run our more modern armv7 package?

https://github.com/MediaBrowser/Emby.Releases/releases/download/4.9.3.0/emby-server-synology7_4.9.3.0_armv7.spk

It probably can't but it's worth trying. If you install and the server won't start, then just install other armv7 package again over the top.

If that doesn't help, then If you're certain that 4.8.11 worked with this, then the only way to know for sure is to try what I mentioned. I personally would be surprised but of course it is certainly possible. What you could do is first rename the server data folder just so that you can keep a safe copy of it:

Emby Server Data Folder

Then uninstall Emby Server and install the corresponding 4.8.11 package:

https://github.com/MediaBrowser/Emby.Releases/releases/tag/4.8.11.0

This will be a fresh install and then you can test the DLNA features. If that goes well, then try updating that fresh install to 4.9 and see what happens. These tests will help narrow down the source of the problem whether it is settings related, data related, something environmental, or if it is related to the server update.

I would love to give you a better answer but this is a 10 year old NAS and it is quite a challenge just to have a working server package at all, let alone having every single feature work properly.

 

[NevRimes 0]

I will try the modern package and let you know.   I definitely had no issues with DLNA until this update,  My activity log shows I was playing on DLNA device (OPPO BDP-105) just before I did the upgrade :

[NevRimes 0]

As expected the non-legacy package wouldn't even install : 

[NevRimes 0]

I tried 4.9.4.1 beta - but that has the same issue too

[Luke 42077]

Ok I would try the next option that I gave you. Thanks.