Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Jellyfin
  3. Cannot start jellyfin after upgrading jellyfin / cloudron

Cannot start jellyfin after upgrading jellyfin / cloudron

Scheduled Pinned Locked Moved Solved Jellyfin
2 Posts 1 Posters 384 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R Offline
      R Offline
      random_eric
      App Dev
      wrote on last edited by random_eric
      #1

      I tried upgrading to jellyfin v1.3.6/10.8.6 but it fails to start.
      In the logs I see this,

      Oct 29 18:10:58 /app/pkg/start.sh: line 26: CLOUDRON_LDAP_SERVER: unbound variable
      

      I tried reverting it back down to 1.3.5, but I still get the same issue. I'm on cloudron 7.3.2

      Then, I tried just adding this to the start.sh file,

      env | grep CLOUDRON
      

      and I don't see any of the CLOUDRON_LDAP_* vaariables defined. I double checked that the ldap addons is defined in the cloudronmanifest.json

      What can I do to fix it?

      1 Reply Last reply
      0
      • R Offline
        R Offline
        random_eric
        App Dev
        wrote on last edited by
        #2

        I messed up. I'm updating my custom my apps through my CI and I misconfigured it. I pushed an app that did not use ldap on to jellyfin and when I reverted back to proper jellyfin, it forget that it had ldap. I just edited the evars for the container and now it works.

        I'll just keep an eye on it for the next update.

        1 Reply Last reply
        2
        • nebulonN nebulon marked this topic as a question on
        • nebulonN nebulon has marked this topic as solved on
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • Bookmarks
          • Search