Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Issue]: DLNA service / announcement seems to not like bind-address being configured #30

Open
1 task done
niclan opened this issue Oct 30, 2023 · 3 comments
Open
1 task done

Comments

@niclan
Copy link

niclan commented Oct 30, 2023

Please describe your bug

Two weeks ago DLNA playback from Jellyfin on our Samsung TV started randomly crashing during playback. No biggie, just restart the DLNA client and select the same file. Jellyfin even remembered how far along the playback had come! But a nusiance. Some days ago I had added a ip-alias to our server because two (unrelated) docker-containers I wanted to run at the same time wanted the same ports. Finding no error messages anywhere I wanted to eliminate the extra interface and told jellyfin to bind to the servers old address.

I later realized that Jellyfin did not appear as a DLNA source in the DLNA players anymore: Not the TV, not VLC, not my phone DLNA client. No problem, just restarted the jellyfin server. Indeed Jellyfin was shown as a service and and I could easily choose the media to play taking however long I needed.

And the next time the same repeated but I did not think too closely about it. This happened a couple more times and I deferred the problem.

Because a couple of other devices had vagues issues I last weekend replaced the switch that the TV and these devices were attached to. I restarted the Jellyfin service, selected a movie and it played trough without a problem. Before the switch replacement it would have crashed several times. (Interestingly the Disney+ client on the TV never had any issues, but I guess it has been made more rugged against network issues). So the playback crashes was due to the old switch. But, the DLNA service still goes off the air after something like one UPNP announcement. If the DLNA clients are not listening at that momemt they will not see Jellyfin.

I found a old case (#972) that sort of looked like my problem. I removed the bind-address setting and restarted. Didn't look like it helped. Started writing up this ticket, this took a while. Restarted jellyfin again. And now it sticks! I can restart the TV, restart the phone DLNA client over and over and start playback and so on.

Jellyfin Version

Other

if other:

10.8.11

Environment

- OS: Ubuntu 22.04.3 LTS
- Linux Kernel: 5.15.0-87-generic
- Virtualization: Jellyfin running on the metal. Server also hosts VirtualBox and docker
- Clients: Samsung Smart TV, VLC, MediaHouse Pro
- Browser: No problems with browser playback
- FFmpeg Version: ffmpeg version 5.1.3-Jellyfin
- Playback Method: DLNA
- Hardware Acceleration: N/A
- GPU Model: N/A
- Plugins: AudioDB, MusicBrainz, OMDb, StudioImages, TMDb
- Reverse Proxy:
- Base URL:
- Networking:
- Storage:

Jellyfin logs

I can't find any relevant log output.  Here is from the moment where I removed the bind-address setting.

[2023-10-30 20:10:48.861 +01:00] [INF] Using LAN addresses: "[192.168.1.0/24]"
[2023-10-30 20:10:57.476 +01:00] [INF] Defined LAN addresses : "[192.168.1.0/24]"
[2023-10-30 20:10:57.477 +01:00] [INF] Defined LAN exclusions : "[]"
[2023-10-30 20:10:57.477 +01:00] [INF] Using LAN addresses: "[192.168.1.0/24]"
[2023-10-30 20:10:59.483 +01:00] [INF] Defined LAN addresses : "[192.168.1.0/24]"
[2023-10-30 20:10:59.484 +01:00] [INF] Defined LAN exclusions : "[]"
[2023-10-30 20:10:59.485 +01:00] [INF] Using LAN addresses: "[192.168.1.0/24]"
[2023-10-30 20:11:03.097 +01:00] [INF] Defined LAN addresses : "[10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]"
[2023-10-30 20:11:03.097 +01:00] [INF] Defined LAN exclusions : "[]"
[2023-10-30 20:11:03.098 +01:00] [INF] Using LAN addresses: "[10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]"
[2023-10-30 20:11:03.112 +01:00] [INF] Using bind addresses: "[]"
[2023-10-30 20:11:03.112 +01:00] [INF] Using bind exclusions: "[]"
[2023-10-30 20:11:06.300 +01:00] [INF] Defined LAN addresses : "[10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]"
[2023-10-30 20:11:06.300 +01:00] [INF] Defined LAN exclusions : "[]"
[2023-10-30 20:11:06.300 +01:00] [INF] Using LAN addresses: "[10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]"
[2023-10-30 20:11:08.305 +01:00] [INF] Defined LAN addresses : "[10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]"

Here is the TV when it gets a session when it starts:

[2023-10-30 20:34:29.891 +01:00] [INF] DLNA Session created for "[TV] Living room" - "UE40K5515"

FFmpeg logs

Issue does not relate to playback, just UPNP service announcement. I think.

Please attach any browser or client logs here

No response

Please attach any screenshots here

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@niclan niclan added the bug label Oct 30, 2023
@niclan niclan changed the title [Issue]: DLNA service / announcement stops very quickly after restart [Issue]: DLNA service / announcement seems to not like bind-address being configured Oct 30, 2023
@Shadowghost
Copy link

Likely fixed by jellyfin/jellyfin#8147 and jellyfin/jellyfin#10051

@niclan
Copy link
Author

niclan commented Oct 31, 2023

Which version will these be in?

@Shadowghost
Copy link

The next major version 10.9.0 or current unstable builds

@barronpm barronpm transferred this issue from jellyfin/jellyfin Nov 30, 2023
@github-actions github-actions bot removed the bug label Jun 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Fixed
Development

No branches or pull requests

2 participants