Comment

Comment on Nginx Jellyfin, both Docker containers

You’re trying to run before you can walk. Run a “hello world” HTTP container, no cloudflare or proxy, and make sure you can reach it. But test it with your phone on mobile data, or downforeveryoneorjustme.com, because it probably won’t work on the LAN without NAT loopback/hairpinning.

Also, don’t put jellyfin on the internet anyway, it’s not designed for it. If you want external access, use a VPN.

source

Sort:hotnew top

LazerDickMcCheese@sh.itjust.works ⁨3⁩ ⁨hours⁩ ago
Thank you, that’s really solid advice. It turns out my efforts may have been misguided anyway. I think I was under the impression that “internet exposure” and “Cloudflare tunnel” had similar setups

source
LazerDickMcCheese@sh.itjust.works ⁨21⁩ ⁨hours⁩ ago
The whole reason I bought the domain is because I was told to stop using Tailscale for this purpose. I’m so confused…

source
- CommanderShepard@lemmy.world ⁨14⁩ ⁨hours⁩ ago
  You can use Tailscale and a personal domain. Run Tailscale on the same machine as your reverse proxy. Then point DNS records to the machine’s Tailscale IP. Now you can access any services from any machine connected to your Tailscale with a valid HTTPS certificate
  
  source
- frongt@lemmy.zip ⁨20⁩ ⁨hours⁩ ago
  Well, those do different things. Expose the VPN, connect via your domain name.
  
  source