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!

  • 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.