+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+---- Forum: Networking & Access (https://forum.jellyfin.org/f-networking-access)
+---- Thread: SOLVED: Reverse Proxy with Caddy (/t-solved-reverse-proxy-with-caddy)
Pages:
1
2
Reverse Proxy with Caddy - wenzelja - 2024-11-26
Trying to setup reverse proxy with DuckDNS and Caddy per https://jellyfin.org/docs/general/quick-start/windows, but I'm running into trouble. I get the error in the attached screenshot when running "caddy respond --body test --listen :80" (screenshot "...181102").
When I run "caddy run," I get the second screenshot ("...181400"). Is something in my computer config causing this, or is my ISP blocking ports 80 and 443?
RE: Reverse Proxy with Caddy - wenzelja - 2024-11-26
P.S. if I go to the sub-domain I created in the guide or even the public IP address I get this page in the screenshot attached.
RE: Reverse Proxy with Caddy - wenzelja - 2024-11-26
I guess I forgot to mention that I am running Jellyfin on Windows 11, no docker or VM, and I had already set a static internal IP when I initially setup the server.
I’ve also checked on my ISP’s website and though they do block a few troublemaker ports, they don’t advertise blocking 80 or 443.
RE: Reverse Proxy with Caddy - wenzelja - 2024-11-26
I think I figured it out but didn't get a chance to work on it last night. Apparently, Windows Defender firewall blocks all ports as default so you have to create a rule to allow 80 and 443 through. I'll work on that tonight and see where that gets me.
I guess it's a good thing I figured this out, I feel like I'm talking to myself in this post... And that's dangerous!
RE: Reverse Proxy with Caddy - TheDreadPirate - 2024-11-26
Do you have IIS running? Not sure how else you would get the screenshot from your second post.
RE: Reverse Proxy with Caddy - pxr5 - 2024-11-26
In the OP > second picture, there is something definitely wrong with your caddy file to get that message. The caddy file is picky with spaces and tabs, so make sure they are spot on. In fact use the info in the error and run 'Caddt fmt --overwrite' Caddyfile.
RE: Reverse Proxy with Caddy - wenzelja - 2024-11-26
(2024-11-26, 01:57 PM)TheDreadPirate Wrote: Do you have IIS running? Not sure how else you would get the screenshot from your second post.@TheDreadPirate
I don't know that I do. Do you know how i could tell that, and would i need to turn it off or disable IIS?
(2024-11-26, 02:05 PM)pxr5 Wrote: In the OP > second picture, there is something definitely wrong with your caddy file to get that message. The caddy file is picky with spaces and tabs, so make sure they are spot on. In fact use the info in the error and run 'Caddt fmt --overwrite' Caddyfile.@pxr5
I just looked at the errors again and I hadn't noticed the formatting error yesterday. When I get a chance today, I'll run the Caddy fmt --overwrite and see if that helps.
I setup my caddyfile with the following:
[my domain].duckdns.org
reverse_proxy 192.168.1.31:8096
Did I miss a character or spacing or something?
The Jellyfin guide shows this for the caddyfile:
<your (sub)domain here>
reverse_proxy 127.0.0.1:8096
Should I have included the <> around my domain, i.e. <[my domain].duckdns.org>? I used 192.168.1.31 in the reverse_proxy line as that is my static internal address. Should I have used the 127.0.0.1 instead?
RE: Reverse Proxy with Caddy - wenzelja - 2024-11-27
Update: I added the exception for ports 80, 443, and 2019 and re-formatted the caddy file, but I still get the same error as in my OP, 2nd screenshot, minus the formatting error.
@TheDreadPirate,
Help me Obi-Wan, you’re my only hope!
RE: Reverse Proxy with Caddy - wenzelja - 2024-11-27
So this is what I'm getting now.
RE: Reverse Proxy with Caddy - wenzelja - 2024-11-27
THis is what I get when I run the listening test