• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support General Questions I need help understanding port 80 security

     
    • 0 Vote(s) - 0 Average

    I need help understanding port 80 security

    I've got a Jellyfin server set up and working but have security concerns.
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 461
    Country:United States
    #2
    2024-03-25, 07:39 PM (This post was last modified: 2024-03-25, 07:40 PM by TheDreadPirate. Edited 1 time in total.)
    (2024-03-25, 06:12 PM)NotReadyForThisJelly Wrote: Except for the following two questions:
    In my router, I've forwarded port 80 (http) and port 443 (https) to Caddy.
    Question 1: What keeps someone from connecting to Caddy through port 80 on an unsecured connection? In my mind this would create this situation: Public Port 80 --> http data accessible anywhere --> reverse proxy --> http data only accessible internally --> jellyfin
    Won't the Caddy reverse proxy be sending publicly available unencrypted potentially vulnerable Jellyfin information?


    According to Caddy's docs, it automatically redirects http requests on 80 to https requests on 443 when https is active.

    https://caddyserver.com/docs/automatic-https#overview

    So that shouldn't be a concern.

    (2024-03-25, 06:12 PM)NotReadyForThisJelly Wrote: Question 2: Is there a problem with closing port 80?
    Since I only want to allow secure connections anyway, after I finished setup I went back into my router and deleted the rule forwarding port 80, and only left port 443 open. I checked this with a port checker tool to make sure it had taken effect, and then I used an offsite computer to connect to Jellyfin and it still functioned correctly using my duckdns domain, defaulting to https://mydomain.duckdns.org.
    Since it's working I'm tempted to leave it closed but I suspect that this might eventually cause issues with my LetsEncrypt certificate, but I'm a neophite when it comes to needing https certificates so I just have no idea.

    Thank you for any insights you can provide,

    The "challenge" during the cert request/renewal process has to occur on port 80.  No way around that.  If you close port 80 you would have to remember to open it before your 90 day cert expires, renew your cert, then close it again. Repeat 80-90 days later.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    « Next Oldest | Next Newest »

    Users browsing this thread:


    Messages In This Thread
    I need help understanding port 80 security - by NotReadyForThisJelly - 2024-03-25, 06:12 PM
    RE: I need help understanding port 80 security - by TheDreadPirate - 2024-03-25, 07:39 PM
    RE: I need help understanding port 80 security - by NotReadyForThisJelly - 2024-03-25, 07:58 PM

    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode