Access your Jellyfin anywhere with Caddy

[VP Lex]

You used your router internal ip not your external ip trying using the ip from here. https://ipchicken.com

In every tutorial it is given 127.0.0.1. If we had to give public ip, then why are those tutorials even exist?

[TheDreadPirate]

Your DuckDNS domain routes external traffic to Caddy. Caddy then routes the request to Jellyfin. Specifying "reverse_proxy 127.0.0.1:8096" tells Caddy that the localhost is the host running Jellyfin. This only applies of Jellyfin and Caddy are on the same host.

[VP Lex]

Found the issue. I had to forward 80, 443 for both TCP and UDP. I did only TCP.

[Phlalom]

Hi,

First of all thank you for this guide, it is clear and easy to follow.

However, when I visit my domain in the browser (Firefox) I don't see my jellyfin instance; instead the browser sends me to to my_url.com/web/index.html where I get a blank white page. If I check the network console I can see I'm getting a 404. The address bar does show I've connected via https though.

Can anybody suggest where I start trouble shooting this issue?

Thanks

EDIT: Just to add, I have tried using Caddy to reverse proxy to other stuff running on my machine, like a react project running on port 3000- this works just fine, so seems as if the issue is with my jellyfin config somehow?

[34626]

Whats the text you added in the CaddyFile? I also use Caddy and it works flawless here.. Have you tried to validate it or upgrade? (Using Caddy over SSH here)

[OsulivanAB]

Appreciate the help! After following your advice, I successfully set up remote access to my server using a Duck DNS domain. Post-setup, I noticed a drastic drop in my home network's performance, even when the server wasn't in use, and there was no unusual activity logged on the Jellyfin logs.
I'm very new to networking, but I suspect the issue might be related to misrouted traffic via Caddy? I'm not sure Here's my setup:
- An old laptop runs Proxmox, hosting a TrueNas VM for storing movies and running Jellyfin in a jail.
- Caddy is configured in a separate jail for web access.
- Port forwarding is set to the Caddy IP for ports 80 and 443.
- Configured Caddy with:

Code:

caddy reverse-proxy --from <mydomain>.duckdns.org --to 192.168.<jellyfin>:8096

- Configured Caddyfile:

Code:

<mydomain>.duckdns.org
reverse proxy <internal ip>:8096

Despite the guide suggesting the use of a public IP, I opted for an internal IP since the domain already points to my public IP. This setup worked, enabling remote server access. But if I still should have used the public IP let me know.
The following day, my internet speed plummeted from around 700mbps to 60mbps. My Raspberry Pi which monitors the internet speeds periodically throughout the day noted this decline coincided with the setup completion.
Given no active server use was logged, I'm puzzled by the significant impact on my network's outgoing internet quality. Could simple port forwarding be the culprit?
I'm not sure why forwarding incoming web server ports would impact my other devices so bad.

[TheDreadPirate]

Setting up port forwarding should not have any impact on router performance. Unless you have some weird setup.

[bonnzifier]

Code:

whatever.duckdns.org {
reverse_proxy localhost:8096
tls {
    # replace with your duck token "<token>"
dns duckdns <token>
}
header {
# disable FLoC tracking
Permissions-Policy interest-cohort=()

# enable HSTS
Strict-Transport-Security max-age=31536000;

# disable clients from sniffing the media type
?X-Content-Type-Options nosniff

# clickjacking protection
?X-Frame-Options DENY

# keep referrer data off of HTTP connections
?Referrer-Policy no-referrer-when-downgrade

Content-Security-Policy "upgrade-insecure-requests"
}
}

[rygle]

I just use Tailscale. Much more secure. Easy.

https://forum.jellyfin.org/t-mega-revers...6#pid17556

[pxr5]

I hope the OP, Matt, will see this post as I think he's the creator/maintainer of caddy-dynamicdns.

I've been using Caddy v2 for quite a while now, but was using a little Windows app to automatically update my IP when needed. Until I read this post properly and discovered Caddy itself can be used for Dynamic DNS. I've managed to install both plugins successfully (caddy-dynamicdns and the dynu plugin), though I did have to register dynu on the Caddy Downloads. Anyway this is where I'm getting a bit stuck with Caddyfile entries. 

caddy-dynamicdns gives Minimal Example Config for the Caddyfile as:

Code:

{
        dynamic_dns {
                provider cloudflare {env.CLOUDFLARE_API_TOKEN}
                domains {
                        example.com
                }
        }
}

The Dynu example config for the Caddyfile is like this:

Code:

tls {
        dns dynu {env.DYNU_API_TOKEN} {
        own_domain {env.OWN_DYNU_DOMAIN}
        }
}

So which do I use? I've knocked up my own Caddyfile and it looks like this, using both examples above:

Code:

{
        dynamic_dns {
                provider dynu apiapiapiapi
                domains {
                        mydomain.exmaple.com
                }
        }
}

mydomain.exmaple.com {
        reverse_proxy 192.168.x.xx:8080
}

tls {
        dns dynu apiapiapiapi {
        own_domain mydomain.exmaple.com
        }
}

I just need some clarity about what exactly goes in the Caddyfile. Thanks.