+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Off Topic (https://forum.jellyfin.org/f-off-topic)
+--- Forum: Self-hosting & Homelabs (https://forum.jellyfin.org/f-self-hosting-homelabs)
+--- Thread: Pretty URLs without forwarding port 443 (/t-pretty-urls-without-forwarding-port-443)
Pretty URLs without forwarding port 443 - donnnnnb - 2023-06-29
I have searched and searched, but I'm not finding a solution or posts that are very helpful.
I want my users to be able to enter one URL like jellyfin.mydomain.tld into either their web browser or TV/phone app without specifying the port number. The apps can do this, but not web browsers.
Cloudflare tunnels are not an option, it is against their TOS to serve video if you're not serving it from their Stream or R3 service. It is also against my ISP's TOS to expose well-known ports. My users aren't savvy enough to use a VPN, and it would be very difficult to get a VPN to work with something like a Roku.
My thought is to setup a separate host just for the Jellyfin Web client on a VPS or something, and point the default server to my home IP on port 8920. But I'm unsure if the Roku/Phone apps will pick up the actual server if I give them the web client address.
Second thought is to setup a rewrite rule in NGINX that serves web content from jellyfin.mydomain.tld, but rewrites the video stream URL's to home.mydomain.tld:8920. Not confident I can do this without breaking something, or if it would even work in practice.
Is there another option I am not considering?
RE: Pretty URLs without forwarding port 443 - TheDreadPirate - 2023-06-29
Just thinking out loud here, haven't tried this myself. If you have an Apache or NGINX reverse proxy, could you specify more than one listener that both forward to Jellyfin? One listening on 443 for web browsers and one listening on 8920 for app clients?
RE: Pretty URLs without forwarding port 443 - donnnnnb - 2023-06-29
That's a good idea, but I would still have to forward port 443 at home.
I'm starting think it might be too much trouble to do this all from my home IP. I'm going to go the VPS route and just proxy everything back to my home server using Wireguard.
Thanks for your reply.
RE: Pretty URLs without forwarding port 443 - Cooljoebob64 - 2023-06-29
Echoing the suggestion for reverse-proxy. I've got mine set up with Traefik 1.7, forwarding ports 80 and 443 (80 traffic redirects to 443/https on ingress) which is working for quite a few different services each with their own subdomain on the main home URL.
Oliver Hilsky has a good guide for getting everything set up; he doesn't set up Jellyfin specifically in this guide, but it works pretty well in the framework he provides. Link here: https://thesmarthomejourney.com/2021/11/08/traefik-1-reverse-proxy-setup/
RE: Pretty URLs without forwarding port 443 - Tim - 2023-06-30
(2023-06-29, 09:24 PM)donnnnnb Wrote: That's a good idea, but I would still have to forward port 443 at home.
I'm starting think it might be too much trouble to do this all from my home IP. I'm going to go the VPS route and just proxy everything back to my home server using Wireguard.
Thanks for your reply.
This is something that I do as well. It works really good. I use NGINX as proxy on a VPS and tunnel it over Wireguard to my Jellyfin server at home.