[Issue]: DLNA broadcasting not working as soon as https is activated #4493

New Issue

OVERLORD · 2026-02-07T00:53:17+03:00

OVERLORD commented

2026-02-07 00:53:17 +03:00

Originally created by @Tinigriffy on GitHub (Jan 8, 2023).

Please describe your bug

Hi my issue is quiet simple and I have seen many report around it but it was supposed to be fixed in serie 1.8.X.X or the issue were closed automatically.

So as soon as I activated HTTPS option (but I do not enforce it) the DLNA boradcasting is not working.
The WS call are done using the ip and http, but wireshark shows that the stream url provided to my old jongo S3 is using https. Unfortunately it is does not support it and it even reports that the url is wrong when it tries to play it.

Here a file with the wireshark dump. renderer ip is 192.168.10.40 and jelly is 192.168.0.17
dlna_error.txt

Jellyfin Version

10.8.0

if other:

10.8.8

Environment

- OS: Linux Fedroa 37
- Virtualization: podman with jellyfin/jellyfin:lastest image
- Clients: none
- Browser: firefox 108.0.1
- FFmpeg Version: version embeded is the odcker image
- Playback Method: dnla
- Hardware Acceleration: no
- Plugins: no
- Reverse Proxy: non
- Base URL: default
- Networking: macvlan
- Storage: local

Jellyfin logs

No response

FFmpeg logs

No response

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

Originally created by @Tinigriffy on GitHub (Jan 8, 2023). ### Please describe your bug Hi my issue is quiet simple and I have seen many report around it but it was supposed to be fixed in serie 1.8.X.X or the issue were closed automatically. So as soon as I activated HTTPS option (but I do not enforce it) the DLNA boradcasting is not working. The WS call are done using the ip and http, but wireshark shows that the stream url provided to my old jongo S3 is using https. Unfortunately it is does not support it and it even reports that the url is wrong when it tries to play it. Here a file with the wireshark dump. renderer ip is 192.168.10.40 and jelly is 192.168.0.17 [dlna_error.txt](https://github.com/jellyfin/jellyfin/files/10367404/dlna_error.txt) ### Jellyfin Version 10.8.0 ### if other: 10.8.8 ### Environment ```markdown - OS: Linux Fedroa 37 - Virtualization: podman with jellyfin/jellyfin:lastest image - Clients: none - Browser: firefox 108.0.1 - FFmpeg Version: version embeded is the odcker image - Playback Method: dnla - Hardware Acceleration: no - Plugins: no - Reverse Proxy: non - Base URL: default - Networking: macvlan - Storage: local ``` ### Jellyfin logs _No response_ ### FFmpeg logs _No response_ ### Please attach any browser or client logs here _No response_ ### Please attach any screenshots here _No response_ ### Code of Conduct - [X] I agree to follow this project's Code of Conduct

OVERLORD added the bug stale labels 2026-02-07 00:53:17 +03:00

OVERLORD closed this issue

2026-02-07 00:53:19 +03:00

OVERLORD commented

2026-02-07 00:53:20 +03:00

@jellyfin-bot commented on GitHub (Jul 26, 2023):

This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.

If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.

This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.

@jellyfin-bot commented on GitHub (Jul 26, 2023): This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments. If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label. This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on [Matrix or Social Media](https://docs.jellyfin.org/general/getting-help.html).

OVERLORD commented

2026-02-07 00:53:21 +03:00

@Shadowghost commented on GitHub (Jul 28, 2023):

Likely fixed by #8147 - please reopen if this still happens on unstable.

@Shadowghost commented on GitHub (Jul 28, 2023): Likely fixed by #8147 - please reopen if this still happens on unstable.

OVERLORD referenced this issue

2026-02-07 06:14:18 +03:00

[PR #4493] [MERGED] Fix dockerfiles #10110

Sign in to join this conversation.

Branches Tags

master

release-10.11.z

renovate/skiasharp-monorepo

JPVenson-patch-1

renovate/morestachio-5.x

release-10.9.z

openapi-cache

release-10.10.z

explicit-load

explicit-load-v2

feature/entity-framework

only-count-folder-item

fix/ci-workflow-refactor

release-10.8.z

release-10.7.z

EraYaN-add-management-interface

release-10.6.z

release-10.5.z

release-10.4.z

release-10.3.z

release-10.2.z

release-10.1.0

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/jellyfin#4493