I followed YouTube videos and all my domain points to is “server not found.” My domain is through Cloudflare. My server’s ports have been opened at the router.
Proxy Host Settings: Domain name: newly.registered.domain Scheme: http (I’ve tried https too) Forward hostname/IP: local.server.ip.v4 Forward port: jelly_port Access list: Publicly accessible SSL: *.newly.registered.domain
I’d love to share my certificate info, but I don’t see a way to do that…but I set up the DNS thingy with a Cloudflare API token. I remember typing in my server’s public IP here too. Took many tries, but it finally accepted the settings as valid.
So what am I missing to get a reverse proxy? I thought it was supposed to work after all of that.
I’ve been trying to get this going for so long that it just feels like I’m beating my head against the wall until it randomly works, ya know?
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 https://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.
Check with your internet provider if they use CG-NAT.
That setting on their end had contributed to me going bald coz I was scratching my head so much…
Basically search for your provider+cgnat
Did you open ports in docket for 80, 443 for nginx and a port for jellyfin (in docker compose under services add these but with tabs not spaces ports: - 443:443)
Do you have ufw or a firewall running? This might be blocking the ports for jellyfin and/or nginx.
It might be easier to create a bridge network called proxy (docker network create proxy) then in docker compose add the following under services networks: - proxy
And at the bottom of the compose file
networks: proxy: external: true
Then in your nginx setting redirect to jellyfin:8096 (service name in docker compose: internal port jellyfin uses I.e. right hand side of ports mapping. Are you using straight nginx or nginx proxy manager (might be worth using this).
Can you access jellyfin locally on your network (http://internal-ip-of-server:8096/ on a browser)?
Has your DNS been setup to point to the correct ip your router is on? Are you behind a dynamic IP or cgnat? If cgnat, you have to use cloudflare tunnels. If ddns look into cloudflared docker image.
Does your router forward those ports to the correct internal ip of your server? Have you fixed the internal IP of the server machine?
Don’t share your certificate details but you can share your docker compose with personal information redacted or replaced
It’s probably not a good idea to publish jellyfin to the internet. Look into tailscale or cloudflare tunnel with login security, or wireguard.
This isn’t a solution to your issue, but a suggestion:
Since you are already using Cloudflare for your domain name, and I assume they gave you some nameservers to use, why not explore the Cloudflare Tunnels/ZeroTrust? Cloudflare Tunnels don’t care if you are behind a dynamic IP, or cgnat. Cloudflare is unconcerned with what ports you open on your router/firewall. You don’t even have to adjust your UFW firewall settings. Cloudflare punches through all that with a tunnel in to your server and tunnel out to the internet.
Admittedly, it did take me a couple tries to get everything worked out, but once I did, it’s easy peasy from there. If you decide this route, I’d be more than happy to clean up some of my notes and share them with you. Might help…might not. LOL
Does it work locally?
