• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support Troubleshooting Networking & Access SOLVED: DLNA devices no longer visible to Jellyfin after playing FLAC

     
    • 0 Vote(s) - 0 Average

    SOLVED: DLNA devices no longer visible to Jellyfin after playing FLAC

    Strobe2000
    Offline

    Junior Member

    Posts: 4
    Threads: 1
    Joined: 2025 Feb
    Reputation: 0
    #1
    2025-02-20, 12:20 AM (This post was last modified: 2025-02-22, 10:54 PM by Strobe2000. Edited 1 time in total.)
    Hi,

    New to Jellyfin and really enjoying the features so far.  One issue that I am having a hard time figuring out is why DLNA services are no longer working.  I can no longer access the DLNA Jellyfin content and Jellyfin no longer is able to see DLNA devices.

    I was connected to my receiver and played some flac/mp3 files to it, then I was trying to access some other files on the app and the music stopped.  I could no longer access the Jellyfin files and Jellyfin no longer sees any DLNA devices.  I had a Blu Ray player that could also access Jellyfin files and that no longer works as well.

    Here is the before logs when it was working.
    https://pastebin.com/h0ShzFNQ

    Here is the after where it is not working.
    https://pastebin.com/uBLRj3va

    Running inside portainer docker in Ubuntu.

    Server version: 10.10.6
    Port configuration
    0.0.0.0:1900 -> 1900/udp
    :::1900  -> 1900/udp
    0.0.0.0:7359 -> 7359/udp
    :::7359 -> 7359/udp
    0.0.0.0:8096 -> 8096/tcp
    :::8096 -> 8096/tcp

    Thanks for any help or insights.
    Go to solution
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #2
    2025-02-20, 03:44 PM (This post was last modified: 2025-02-20, 03:46 PM by TheDreadPirate. Edited 2 times in total.)
    Did you change network modes? For the log that was "working" I see this.

    Code:
    Filtered interface addresses: ["127.0.0.1", "192.168.1.151", "172.17.0.1"]

    For the log that was not working I see this.

    Code:
    Filtered interface addresses: ["127.0.0.1", "172.17.0.3"]

    I interpret this as going from host networking to bridge networking+port publishing.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    Strobe2000
    Offline

    Junior Member

    Posts: 4
    Threads: 1
    Joined: 2025 Feb
    Reputation: 0
    #3
    2025-02-20, 08:21 PM
    (2025-02-20, 03:44 PM)TheDreadPirate Wrote: Did you change network modes?  For the log that was "working" I see this.

    Code:
    Filtered interface addresses: ["127.0.0.1", "192.168.1.151", "172.17.0.1"]

    For the log that was not working I see this.

    Code:
    Filtered interface addresses: ["127.0.0.1", "172.17.0.3"]

    I interpret this as going from host networking to bridge networking+port publishing.

    Yes you are absolutely on point.  You are good!  I have tried several changes to the networking to see if it would change anything before posting.

    Did some digging and I was able to find the exact point where I queued up a FLAC file, played several other files to test then I couldn't play or find the device anymore.  This log should show the original network settings.  Sorry probably should have shared this log first.

    https://pastebin.com/F7cHWR0s
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #4
    2025-02-20, 09:13 PM
    In this log it looks like the container just can't find or utilize any network interface.

    Code:
    Filtered interface addresses: []

    And it looks like this changed while Jellyfin was already running.

    Regardless, what I'm reading says that you need to use host networking. DLNA broadcasts only work on the same subnet as the DLNA server.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    Strobe2000
    Offline

    Junior Member

    Posts: 4
    Threads: 1
    Joined: 2025 Feb
    Reputation: 0
    #5
    2025-02-21, 10:19 PM
    (2025-02-20, 09:13 PM)TheDreadPirate Wrote: Regardless, what I'm reading says that you need to use host networking.  DLNA broadcasts only work on the same subnet as the DLNA server.

    Thank you Dread this got the device back online after recreating the container!

    I was able to reproduce the issue that I saw before.  Below are the exact steps.

    - Use Jellyfin Mobile (iOS) 1.5.0 app or web browser to select DLNA receiver
    - Play 1st audio FLAC file, it plays fine
    - Select 2nd audio FLAC, plays for 3 seconds then no audio
    - DLNA devices and DLNA server no longer running on the network
    - Stop container and shows exit code 137 in portainer
    - Redeploy container and DLNA devices are back.

    Notes:
    I tried switching multiple MP3 files and didn't have any issues
    If I try to access multiple FLAC files directly on the DLNA server they play fine (Using Yamaha mobile app)

    Logs after redeploying container and initiating DLNA failure.
    https://pastebin.com/S4Sw5Pc3

    If I am playing through Jellyfin, is Jellyfin doing the decoding vs if I play directly from the server my receiver is doing the decoding?
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #6
    2025-02-21, 11:45 PM (This post was last modified: 2025-02-23, 03:23 AM by TheDreadPirate. Edited 1 time in total.)
    The client will always decode regardless of what the server does. The server will decode only when it is transcoding, but only because decoding is necessary to then re-encode.

    My guess is that the default profile isn't sending a compatible stream to your receiver. It looks like it is just sending a straight up .flac stream to the receiver.

    If you had a custom profile before, you will need to place it in /config/data/plugins/configurations/dlna/user. If you don't have a custom profile already, there are templates in /config/data/plugins/DLNA_6.0.0.0/profiles. "Denon AVR" is probably a good starting point.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    Strobe2000
    Offline

    Junior Member

    Posts: 4
    Threads: 1
    Joined: 2025 Feb
    Reputation: 0
    #7
    2025-02-22, 10:54 PM
    DreadPirate you are right on again! Assigning my receiver to match the Denon AVR profile fixed the issue of playing multiple FLAC files directly on the receiver.

    Thank you for all the help and your expertise.
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode