I have been trying to use jellyfin locally but subtitles have issues some times depending on the show or format. Also recently my wife watched 2 episodes more than me so we needed to go back 2 episodes and only way to do that from the Up Next or Resume screens was to start a new search of the show and click into the season and then find the episode. In Plex that takes 2extra clicks to get to the season and find the episode. I get supporting open source but for my jellyfin only has 70% of the features I use weekly on Plex. Definitely supporting it and trying to use it but it’s not feature parity for me

Just did that, honestly didn’t know lifetime was always available, thought it was only during sales or certain times, should have gotten it years ago

I just upgraded to lifetime and also use jellyfin but right now it only does 80% of what Plex does in my workflow so gonna use it until I can’t anymore.

I’ve been testing out jellyfin for the last couple months but it doesn’t really fill the void of this specific feature that’s being locked behind a pay wall. If anyone has good recommendations for securely and reliably hosting jellyfin behind SSL and auth with email password resets where I don’t have to worry about it as much as Plex.

I use jellyfin locally but for a handful of remote clients I have I may well block off their access they’re not going to be able to figure out my hand spun services and wall of text.

Heres what I’m running:

authentication_backend:
  file:
    path: '/config/users_database.yml'
    watch: false
    search:
      email: false
      case_insensitive: false
    password:
      algorithm: 'sha2crypt'

access_control:
  ## Default policy can either be 'bypass', 'one_factor', 'two_factor' or 'deny'. It is the policy applied to any
  ## resource if there is no policy to be applied to the user.
  default_policy: 'deny'

  networks:
    - name: 'internal'
      networks:
        # - '10.10.0.0/16'
        - '192.168.1.0/24'
    - name: 'VPN'
      networks: '10.0.1.0/24'

  rules:
    ## Rules applied to everyone
    - domain: '*.mydomain.com'
      policy: 'one_factor'

session:
  ## The secret to encrypt the session data. This is only used with Redis / Redis Sentinel.
  ## Secret can also be set using a secret: https://www.authelia.com/c/secrets
  secret: 'insecure_session_secret'

  ## Cookies configures the list of allowed cookie domains for sessions to be created on.
  ## Undefined values will default to the values below.
  cookies:
  #   -
      ## The name of the session cookie.
    - name: 'authelia_session'

      ## The domain to protect.
      ## Note: the Authelia portal must also be in that domain.
      domain: 'mydomain.com'

      ## Required. The fully qualified URI of the portal to redirect users to on proxies that support redirections.
      ## Rules:
      ##   - MUST use the secure scheme 'https://'
      ##   - The above 'domain' option MUST either:
      ##      - Match the host portion of this URI.
      ##      - Match the suffix of the host portion when prefixed with '.'.
      authelia_url: 'https://auth.mydomain.com/'
storage:
  postgres:
    ....

identity_providers:
  oidc:
    ## Cross-Origin Resource Sharing (CORS) settings.
    cors:
      ## List of endpoints in addition to the metadata endpoints to permit cross-origin requests on.
      endpoints:
         - 'authorization'
         - 'token'
         - 'revocation'
         - 'introspection'
        #  - 'pushed-authorization-request'
        #  - 'userinfo'

      ## List of allowed origins.
      ## Any origin with https is permitted unless this option is configured or the
      ## allowed_origins_from_client_redirect_uris option is enabled.
      allowed_origins:
        - 'https://mydomain.com/'
        - 'https://grafana.mydomain.com/'
        - 'https://wiki.mydomain.com/'
        - 'https://foodz.mydomain.com/'

      ## Automatically adds the origin portion of all redirect URI's on all clients to the list of allowed_origins,
      ## provided they have the scheme http or https and do not have the hostname of localhost.
      allowed_origins_from_client_redirect_uris: true
    ## Clients is a list of known clients and their configuration.
    clients:
      - client_id: 'grafana'
        client_name: 'Grafana'
        client_secret: 'XXXXXX'
        public: false
        consent_mode: 'pre-configured'
        authorization_policy: 'one_factor'
        require_pkce: true
        pkce_challenge_method: 'S256'
        redirect_uris:
          - 'https://grafana.mydomain.com/login/generic_oauth'
        scopes:
          - 'openid'
          - 'profile'
          - 'groups'
          - 'email'
        userinfo_signed_response_alg: 'none'
        token_endpoint_auth_method: 'client_secret_basic'
      - client_id: 'wiki'
        client_name: 'Wiki'
        client_secret: 'XXXX'
        consent_mode: 'pre-configured'
        public: false
        authorization_policy: 'one_factor'
        require_pkce: true
        pkce_challenge_method: 'S256'
        redirect_uris:
          - 'https://wiki.mydomain.com/oidc/callback'
        scopes:
          - 'openid'
          - 'profile'
          - 'groups'
          - 'email'
        userinfo_signed_response_alg: 'none'
        token_endpoint_auth_method: 'client_secret_basic'
      ....

Then my users_database.yml looks like:

users:
  authelia:
    disabled: false
    displayname: "Test User"
    password: ""
    email: [email protected]
    groups:
      - admins
      - dev
  user001:
    disabled: false
    displayname: 'User 001'
    password: "$6$rounds=50000$XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
    email: [email protected]
    groups:
      - admins
      - users

Certainly, I’ll post it tomorrow

I used to run key cloak backed by LDAP. Few months ago moved to Authelia and after many hours of tinkering and setting up sites I haven’t had to touch it except to add a new URL or user.

I slightly disagree with the other commenter I didn’t find it easy or straightforward but once I finally found what worked for my setup its been great.

Imagine Authelia is the caddy of SSO. Powerful, intimidating but very efficient. Also all configs are in like 3 files and things aren’t going to change without FS access which only I the admin have.

Caddy can do the same and there is a steep learning curve but I switched about a year ago and only need to touch the config file when I add a host. Can even bring that config to a new server and it will stand up once it starts and picks up the config.

The same movie works on the roku Plex app with the embedded subtitles just fine.

Also findroid is an android app that has more features than the native app

Just tested and with Findroid on my phone, no subtitle options appeared at all, though it had 4 languages embedded. On my roku they showed up but as soon as I picked it it loaded until it said Error During Playback

Sounds like it’s mostly with embedded subs inside the media files already. Thats where all my subs are so I’m going to test soon but haven’t played anything on jellyfin needing subs in a while

I’ve been using plex for several years and setup jellyfin a few months ago to tinker with it. Playing videos works fine for me locally but I have some family out of state who have access and jellyfin doesn’t have a solution for that outside of me publicly sharing the URL and managing the passwords. Also a pain point for me is having multiple files of different quality for the same movie/episode, it always shows as two episodes that it will play back to back and seems to require a lot of manual work per show/movie to get it tracked as 1 piece of media with 2 files to choose from. Would love to ditch Plex eventually but for me and my family it just works without issue and they can manage their own remote login.

Github README says plugin support especially DeDRM is highest priority on the roadmap so not yet it seems but soon

Found my way to that from other mentions of OSMC and gonna order one of those in the coming weeks. Been looking for an alternative to my Roku Ultra for a while.

Edit: searching more I see Vero V forum posts from this year about things like Netflix and Amazon limiting streaming to 1080p or lower, and YouTube being a lethargic experience. Will save it and probably go the Nvidia shield route for now.

I just got an LG C3 and don’t have it connected to the network. I also turned off the fast input and power on and takes maybe 10 seconds to boot into the input. Not much longer than my blu ray player and receiver.

When I first started self hosting in 2018 I didn’t know about how PFsense handled themselves and got a netgate appliance and used it up until 2 years ago and it ran great. Not a bad recommendation by any means but also understand expectations and opinions shift.

I too use the singular container from imagegenius and point it at a DB and redis. Usually their upgrade paths mention several components but I’ve only ever used the one.

The way it is written was like only vault warden is self host able and usually VW is mentioned more in forums when the actual official stack that gets regular updates and security reviews is available to host so I always like to point that out so more people use it instead of the knock off though it does have it’s use cases.

I was responding to a comment about bitwarden being paid while vaultwarden is self hosted. I’ve been self hosting bitwarden for years and pay $20 a year for the subscription to do so and support them. Is the self hosted option not paid like the comment I replied to says?

https://bitwarden.com/help/install-on-premise-linux/