Comment

qjkxbmwvz@startrek.website ⁨1⁩ ⁨week⁩ ago

Another fun trick you can play is to use a private IP on your public DNS records. This is useful for Jellyfin on Chromecast for instance — it uses 8.8.8.8 for DNS lookup (and ignores your router settings), so it wants a fully qualified domain name. But it has no problem accessing local hosts, so long as it’s from 8.8.8.8’s record.

source

Sort:hotnew top

sugar_in_your_tea@sh.itjust.works ⁨1⁩ ⁨week⁩ ago
I suppose, but then you’re kind of screwed if you want to access Jellyfin outside of your network. I suppose you could use a VPN, but it’s probably easier to just not use the Chromecast (or just accept that it’s going to hit the WAN regardless).

source
- qjkxbmwvz@startrek.website ⁨1⁩ ⁨week⁩ ago
  Yeah I don’t expose Jellyfin over the Internet, so it doesn’t matter for me, and wouldn’t work at all over WAN (unless VPN’d to home network).
  
  Also, it’s all reverse proxied, and there’s nothing preventing having two Jellyfin hostnames, e.g., jf-local.mydomain.com and jf-public.mydomain.com.
  
  source
  - sugar_in_your_tea@sh.itjust.works ⁨1⁩ ⁨week⁩ ago
    Then you’re all clear.
    
    I personally want my Jellyfin to be on the WAN, and I have certain devices on my internal network VPN’d to my VPS, which exposes the services I want to access remotely. But if you don’t need that, using the local addr in your DNS config totally works. Getting TLS certs will be complicated, but you don’t need that anyway if everything is local or over a VPN.
    
    source
    qjkxbmwvz@startrek.website ⁨1⁩ ⁨week⁩ ago
    
    Getting TLS certs will be complicated
    
    I just use Let’s Encrypt with a wildcard domain — same certs for public and private facing domains. I’m sure this isn’t best practice, but it’s mostly just for me so I’m not too worried :)
    
    source