I am running the v0.4.0 beta and trying to connect to Jellyfin from my TV. Everything runs on the same network but the Jellyfin TV app won’t detect my server. What extra information would be needed to troubleshoot my issue (please keep in mind, i’m not technical at all and highly regarded!)?
We’d need to know something about the issue. Essentially, “TV” doesn’t tell me much about what you’re using and “won’t detect” isn’t an error I recognize! 
One of the common issues we’ve seen with Jellyfin on v040 so far is that many platforms are too retarded to allow their users to use HTTPS with SSL certificates on their LAN, with no ability to import a Root CA. Perhaps it’s that?
It’s a Samsung TV, so I guess that’s Android or Bixby of some kind. The Jellyfin App is loaded from the Samsung App Store. It has a “auto-listen” function which does not find any server on the local LAN. Also entering the URL manually (with http and https) did not work. I would have to check if the TV has a function to import a Root CA, but with Samsung locking pretty much everything down, I highly doubt it.
That auto detect feature will be looking for a specific port.
You’ll need to provide the full address yourself…
i.e.
https:// + <IP> + : + <PORT>/
Your interfaces are provided for you in the Jellyfin service page.
After some research, it looks like the Samsung issue is the same with Roku and other platforms.
As of early 2026, Jellyfin is officially available natively on Samsung’s Tizen TV operating system, after a multi-year wait. The rollout focuses on newer Samsung TVs, likely running Tizen 6 or newer, with reports suggesting it’s already live on many Samsung TVs from 2021 and newer, though availability still varies by model and region. Source: XDA Developers
You can point the app at https://<IP>:<PORT>, but from what I am reading it usually won’t work because the Jellyfin client apps don’t allow for self-signed certificates, and you can’t get a publicly trusted cert for a raw IP address (Let’s Encrypt and other public CAs won’t issue them).
The Jellyfin maintainers have stated: “We will never add the option to ignore SSL errors. If you want to use a self-signed certificate you can add it to the trust store of the operating system.” Samsung Tizen TVs don’t give you a friendly way to install a custom root CA, so the self-signed route is essentially a dead end on the TV. Source: gitmemories
So basically, if an operating system REFUSES POINT BLANK to allow users to trust self-signed certificates or to trust a CA, then any Jellyfin app will not be able to connect to StartOS. Much like Jellyfin doesn’t want to degrade their software to satisfy a hardware manufacturer’s laziness or stupidity, Start9 dismissed adding http interfaces in the OS because it’s insecure.
You might be forced into a bit of a hack here, as another user I interacted with has been, in that they’re need to register a domain name and run everything through that.
Thanks for taking the time to do a deep dive on this. This is at a high level where I landed as well after doing a less thorough search.
It’s unfortunate that this seems to be the reality of the matter.
I’ll see if it’s worth the hassle of going the domain name route.
I’d just wish it would work as advertised (on JF’s end) as this I think would be definitely a feature people would want from a sovereign home server.
In reality it isn’t the Jellyfin team’s fault that they don’t want to degrade their software to add anything to ignore SSL warnings, or add new functionality to trust root CAs inside their software only. They’re right that this should happen at system level, but the providers of these systems (Samsung, LG, Roku, Amazon etc) think you should just shut up and subscribe to Netflix.