• 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 Podman Jellyfin - HTTPS access

     
    • 0 Vote(s) - 0 Average

    Podman Jellyfin - HTTPS access

    Podman Jellyfin - HTTPS access
    trekkie690
    Offline

    Junior Member

    Posts: 10
    Threads: 2
    Joined: 2023 Nov
    Reputation: 0
    Country:United States
    #1
    2023-11-11, 09:04 PM
    [*]Version: 10.8.12
    [*]Installation method/platform: Podman on Fedora 38 Linux
    [*]Container Version: docker.io/jellyfin/jellyfin:latest
    [*]Issue summary: HTTPS server configuration

    Starting my transition off of a VM of jellyfin, and moving to a container instance. Testing each of the key things i've learned after running Jellyfin for a bit. Finally got the container working with my RAID that i normally just connect through virtual interface on my VM (all this is one server so networks not really required). 

    Since that works i'm setting it up so TLS/SSL portion of the server with a self signed cert (works fine with my VM instance). I cannot connect to the server via TLS (port 8920) on the web interface. I get the connect connect error (firefox, edge, chrome all same issue) PR_CONNECT_RESET_ERROR. Which 99% certain means the container cannot setup the TLS part of the server. Really the questions are

    1) Is the container setup to use TLS/SSL or do i need to add this functionality?

    2) Is there more i have to do to setup the TLS/SSL for a podman container (environment variable, system resource) so that the HTTPS server side works?
    - the container can access and has permission to the cert. its in the correct format (works on VM at least)
    - the container can see it and states it can access it with the password i have set for it

    - Thanks
    TheDreadPirate
    Online

    Community Moderator

    Posts: 11,857
    Threads: 10
    Joined: 2023 Jun
    Reputation: 347
    Country:United States
    #2
    2023-11-11, 09:48 PM
    We strongly recommend that you use a reverse proxy to handle https. It is much more secure. Jellyfin's https implementation is jank.

    Most people with containerized setups use an Nginx container.
    Jellyfin 10.10.3 (Docker)
    Ubuntu 24.04 LTS 
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)
    [Image: GitHub%20Sponsors-grey?logo=github]
    trekkie690
    Offline

    Junior Member

    Posts: 10
    Threads: 2
    Joined: 2023 Nov
    Reputation: 0
    Country:United States
    #3
    2023-11-12, 03:29 PM
    So i plan on doing that. but first. Does the container version of jellyfin have a functional https server on it or are we forces to proxy?
    TheDreadPirate
    Online

    Community Moderator

    Posts: 11,857
    Threads: 10
    Joined: 2023 Jun
    Reputation: 347
    Country:United States
    #4
    2023-11-12, 06:22 PM
    It does, but its kind of jank both in the setup and actual implementation of https. Which is why we always recommend that a reverse proxy handle https.
    Jellyfin 10.10.3 (Docker)
    Ubuntu 24.04 LTS 
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)
    [Image: GitHub%20Sponsors-grey?logo=github]
    trekkie690
    Offline

    Junior Member

    Posts: 10
    Threads: 2
    Joined: 2023 Nov
    Reputation: 0
    Country:United States
    #5
    2023-11-24, 03:54 PM (This post was last modified: 2023-11-24, 03:57 PM by trekkie690. Edited 1 time in total.)
    Alright so figured it out. Basically i had to toggle a setting to enable it; even though i had it already enabled.

    Advanced Setting --> Networking --> Click Enable HTTPS (even if its already enabled) --> Scroll to "Remote Access Setting" and click (even if it's already clicked) "Allow remote connections to this server". --> Provide path to Certificate and Password under "HTTPS Settings"

    Once i basically disabled, then enabled it was functional. So janky for sure. Next is getting the reverse proxy to work with all the services (while watching my movies of course).
    « Next Oldest | Next Newest »

    Users browsing this thread:


    • 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