[Issue]: DLNA server response uses https even if RequireHttps is false #3432

Closed
opened 2026-02-06 23:21:18 +03:00 by OVERLORD · 2 comments
Owner

Originally created by @jirgais on GitHub (Dec 9, 2021).

Please describe your bug

The DLNA server is only discoverable if HTTPS is disabled in the network settings. When HTTPS is enabled, the DLNA server response uses HTTPS which is not supported by all clients:

[2021-12-08 23:30:17.534 +01:00] [DBG] Sent byebye notification MediaServer - 30656318b41c4165a8facf7a9f5e357f - https://192.168.9.18:8920/dlna/30656318b41c4165a8facf7a9f5e357f/description.xml

Shouldn't the DLNA server instead send a HTTP response/port if EnableHttps is true but RequireHttps is false in the settings? As it is now, an unsecured HTTP connection must be used for remote Jellyfin clients, or DLNA on the local network will not work.

Jellyfin Version

10.7.7

if other:

No response

Environment

- OS: Ubuntu 20.04
- Virtualization:-
- Clients:Sony TV, VLC, Twonky Player
- Browser: Firefox

Jellyfin logs

EnableHttps = true, RequireHttps = false

[2021-12-08 23:30:17.534 +01:00] [DBG] Sent byebye notification MediaServer - 30656318b41c4165a8facf7a9f5e357f - https://192.168.9.18:8920/dlna/30656318b41c4165a8facf7a9f5e357f/description.xml

EnableHttps = false, RequireHttps = false

[2021-12-08 23:30:20.461 +01:00] [DBG] Device Added MediaServer - 30656318b41c4165a8facf7a9f5e357f - http://192.168.9.18:8096/dlna/30656318b41c4165a8facf7a9f5e357f/description.xml

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 @jirgais on GitHub (Dec 9, 2021). ### Please describe your bug The DLNA server is only discoverable if HTTPS is disabled in the network settings. When HTTPS is enabled, the DLNA server response uses HTTPS which is not supported by all clients: [2021-12-08 23:30:17.534 +01:00] [DBG] Sent byebye notification MediaServer - 30656318b41c4165a8facf7a9f5e357f - https://192.168.9.18:8920/dlna/30656318b41c4165a8facf7a9f5e357f/description.xml Shouldn't the DLNA server instead send a HTTP response/port if EnableHttps is true but RequireHttps is false in the settings? As it is now, an unsecured HTTP connection must be used for remote Jellyfin clients, or DLNA on the local network will not work. ### Jellyfin Version 10.7.7 ### if other: _No response_ ### Environment ```markdown - OS: Ubuntu 20.04 - Virtualization:- - Clients:Sony TV, VLC, Twonky Player - Browser: Firefox ``` ### Jellyfin logs ```shell EnableHttps = true, RequireHttps = false [2021-12-08 23:30:17.534 +01:00] [DBG] Sent byebye notification MediaServer - 30656318b41c4165a8facf7a9f5e357f - https://192.168.9.18:8920/dlna/30656318b41c4165a8facf7a9f5e357f/description.xml EnableHttps = false, RequireHttps = false [2021-12-08 23:30:20.461 +01:00] [DBG] Device Added MediaServer - 30656318b41c4165a8facf7a9f5e357f - http://192.168.9.18:8096/dlna/30656318b41c4165a8facf7a9f5e357f/description.xml ``` ### 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 label 2026-02-06 23:21:18 +03:00
Author
Owner

@cvium commented on GitHub (Dec 9, 2021):

Fixed by https://github.com/jellyfin/jellyfin/pull/5905

@cvium commented on GitHub (Dec 9, 2021): Fixed by https://github.com/jellyfin/jellyfin/pull/5905
Author
Owner

@jirgais commented on GitHub (Dec 9, 2021):

Installed jellyfin-server_20211208.7-unstable_amd64 and it solves the problem.
Many thanks!!

@jirgais commented on GitHub (Dec 9, 2021): Installed jellyfin-server_20211208.7-unstable_amd64 and it solves the problem. Many thanks!!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#3432