Check whether the DLNA component is installed
A working Jellyfin web login does not establish that a television’s DLNA browser should discover the server. Jellyfin moved DLNA into a first-party plugin from 10.9. Its guide directs administrators to the official catalogue and requires a server restart to complete that installation. Identify the actual installed component before changing media filenames or user passwords.
Review discovery on the intended local network
Jellyfin’s DLNA guide describes SSDP discovery on UDP 1900 and the same-subnet requirement. It says remote DLNA use is not supported by that workflow and documents host networking for a Docker deployment using DLNA. These are requirements for the local discovery path, not instructions to expose a discovery port to the public internet or assume a successful browser connection uses the same protocol.
Compare one local client deliberately
For example, an administrator can verify the official plugin and restart state, then inspect discovery from a television on the intended local subnet. Keep a normal web-client result as a separate reference. If the server is absent only from DLNA, review the discovery-specific logs and network arrangement instead of resetting an unrelated viewing account. Do not install an arbitrary third-party plugin with a similar name to compensate for a missing official component. Record the server version, plugin state and local-network context when seeking help, while keeping private network information out of public screenshots.
Questions, answered
Does a successful web login prove DLNA is installed and discoverable?
No. Jellyfin documents the plugin and local discovery requirements separately.