+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: General Questions (https://forum.jellyfin.org/f-general-questions)
+--- Thread: Reverse proxy not working for new PC? (/t-reverse-proxy-not-working-for-new-pc)
Pages:
1
2
RE: Reverse proxy not working for new PC? - 4r5hw45twh - 2024-09-29
(2024-09-29, 12:04 AM)TheDreadPirate Wrote: Negatory. Subdomain CNAMEs can point to domain names. They can also be a completely different IPs.
"jellyfin" is a cname that points to my domain. So jellyfin.domain.tld would resolve to my public IP. This allows you to have multiple services listening on the same port since the reverse proxy would direct traffic to the proper destination based on the subdomain used. This also allows you to change how Cloudflare handles each subdomain. Whether DNS only or proxying. If you used subPATHs you wouldn't be able to do this. Like domain.tld/jellyfin.
Hmm. I decided to try and just use NGINX Proxy Manager (NPM) on Docker (JF is on my machine directly, not Docker).
On CF, I have my A domain record pointing to my server's public IP: https://i.imgur.com/9AE6YmP.png
I have NPM proxy host set for the same subdomain name like: https://i.imgur.com/4JfyBCH.png
I have a SSL (Let's Encrypt) thing setup on NPM. Ports are all forwarded fine.
Still can't connect outside the network. If I bypass NPM completely and just use proxied CF + tunnel to my local IP, it works fine outside the network, which looks like this: https://i.imgur.com/rg373Xk.png - CF creates the record automatically when the tunnel public hostname is created, shown here: https://i.imgur.com/f7slqwc.png
RE: Reverse proxy not working for new PC? - TheDreadPirate - 2024-09-29
The A record should be just your domain, no subdomain, and your public IP. You'd create a separate CNAME that is just the subdomain name and the target is your domain name.
Also, you should setup your clients to use Cloudflare for DNS to ensure that DNS updates are received immediately. Otherwise, changes to DNS for existing records not take 24-48 hours to propagate to your current DNS.
I'll send you a screenshot in a PM so there is less ambiguity when hiding our info from public.