The Jellyfin streaming has been designed with HTTP so I don't think it will benefit from a TCP proxy. Plus as you've noticed with TCP you lose the ability to route by domain name.
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
TCP streams don't have any concept of hostname.
I would test it both ways and see if there's actually a measurable difference. I have Jellyfin behind Traefik and I don't have issues.
Also, Jellyfin docs do have a page on using nginx: https://jellyfin.org/docs/general/networking/nginx