Hi y’all, thanks for the help with my question yesterday. I did a bit of homework, and I think I’ve got things figured out. Here’s my revised plan:

  1. configure a cron job to update DuckDNS with my IP address every 5 minutes

  2. use ufw to block all incoming traffic, except to ports 80 and 443, to allow incoming traffic to reach Caddy

  3. configure the Caddyfile to direct traffic from my DuckDNS subdomain to Jellyfin’s port

Does this seem right this time? Am I missing anything, or unnecessarily adding steps? Thanks in advance, I’ll get the hang of all this someday!

  • dogs0n@sh.itjust.worksEnglish
    101·
    1 day ago

    It’s honestly just a matter of how much risk you are comfortable with for using jellyfin on the open internet.

    (If i remember correctly:) The unauthenticated routes thing can only be used for streaming your content without a login (if you can guess the contents ids on your server I believe).

    In my opinion, it’s not worth the hassle of using a vpn because I don’t think this risk is worth mitigating with one.

    But everyone has their own personal risk assesment of course.

    P.s. Easier than a VPN, at least for logging in other users, would be to use some type of proxy authentication like Authelia. I believe jellyfin has a plugin you can use. It can be complicated to setup, but it’s an option. I believe it should protect all routes exposed by jellyfin so that solves the unauthenticated streaming issue. (I still dont think this is necessary but more choice for the risk-adverse!).

    https://github.com/authelia/authelia

    • frongt@lemmy.zipEnglish
      21·
      1 day ago

      Yes, those are the known vulnerabilities. We don’t know how many unknown vulnerabilities could be discovered in the future.

      • Auli@lemmy.caEnglish
        1·
        4 hours ago

        And are these the ones they let people see what media I have or are there any serious ones?

      • dogs0n@sh.itjust.worksEnglish
        4·
        22 hours ago

        Unfortunately no software exists that is fully perfect in this regard (any program could have multiple bugs just waiting to be found), but jellyfin being open source puts it in a better situation for finding vulnerabilities sooner.

      • ITGuyLevi@programming.devEnglish
        2·
        22 hours ago

        At least we are more likely to hear about them than we would for PMS. Quickest way to find vulnerabilities is to have as many eyes as possible on it, if you only let the 20 devs you employ look a lot can be missed. Just my opinion though.