• 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 Troubleshooting Networking & Access SOLVED: Accessing Jellyfin in Docker Compose using Native Caddy and DuckDNS. Can't open ports

     
    • 0 Vote(s) - 0 Average

    SOLVED: Accessing Jellyfin in Docker Compose using Native Caddy and DuckDNS. Can't open ports

    Accessing Jellyfin in Docker Compose using Native Caddy and DuckDNS. Can't open ports
    jellykrabbypatty
    Offline

    Junior Member

    Posts: 15
    Threads: 5
    Joined: 2025 Mar
    Reputation: 0
    Country:United States
    #1
    2025-09-26, 08:32 PM
    Hello, can someone help me with this reverse proxy through caddy? 

    With the help of Microsoft Copilot, I was able to have my computer: 

        Jellyfin is running locally and working. (Docker Compose yml file)

        Caddy is installed natively (not in Docker) and configured to reverse proxy Jellyfin.

        DuckDNS domain (subdomain.duckdns.org) is set up and pointing to your public IP.

        Docker Compose was used initially but is no longer needed for Caddy.

        UFW firewall is now active and allows ports 80 and 443.

    However: 

        Caddy is trying to get a TLS certificate from Let’s Encrypt.

        Let’s Encrypt uses port 443 to verify your domain.

        Port 443 is not open to the outside world — this is the blocker.

    What I’ve Already Done

        Verified DuckDNS is resolving correctly.

        Set up port forwarding in your Netgear router for ports 80 and 443.

        Enabled UFW and allowed those ports.

        Restarted Caddy and checked logs — it’s attempting the TLS challenge.


    Does anyone have any ideas? I don't think it would be smart to say what ISP I am using. But I am using a Netgear Mesh router with 1 satellite, and have port forwarding rules for 80 to 80 with my host IP as well as 443. I read online my ISP does not block using ports. I am using their fiber modem. 

    I am at a loss.

    Let me know if there is any more information I can provide.  Confounded-face
    Go to solution
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    Messages In This Thread
    Accessing Jellyfin in Docker Compose using Native Caddy and DuckDNS. Can't open ports - by jellykrabbypatty - 2025-09-26, 08:32 PM
    RE: Accessing Jellyfin in Docker Compose using Native Caddy and DuckDNS. Can't open ports - by pxr5 - 2025-09-26, 09:07 PM
    RE: Accessing Jellyfin in Docker Compose using Native Caddy and DuckDNS. Can't open ports - by jellykrabbypatty - 2025-09-26, 10:47 PM
    RE: Accessing Jellyfin in Docker Compose using Native Caddy and DuckDNS. Can't open ports - by jellykrabbypatty - 2025-09-26, 11:58 PM
    RE: Accessing Jellyfin in Docker Compose using Native Caddy and DuckDNS. Can't open ports - by pxr5 - 2025-09-27, 03:40 PM
    RE: Accessing Jellyfin in Docker Compose using Native Caddy and DuckDNS. Can't open ports - by jellykrabbypatty - 2025-09-27, 04:23 PM
    RE: Accessing Jellyfin in Docker Compose using Native Caddy and DuckDNS. Can't open ports - by jellykrabbypatty - 2025-09-27, 05:05 PM
    RE: Accessing Jellyfin in Docker Compose using Native Caddy and DuckDNS. Can't open ports - by pxr5 - 10 hours ago

    • 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