Sonarr

Managarr - A TUI and CLI to help you manage your Servarrs.

Thanks to everyone who contributed to this release, be that in code, issues, or enhancement suggestions! You all help fuel my passion for working on this and it doesn't go unappreciated! 😄

As always, you can try out the changes yourself via the Managarr Demo Site

Breaking Changes

• Managarr now supports multiple instances of the same Servarr with custom names and ordering. (See Features below) To accommodate this, configuration files must be updated so that all Servarrs listed beneath radarr, sonarr, etc., be updated to be lists, not individual Servarrs. For example: to migrate from the following config:

  radarr:
    host: 192.168.0.78
    port: 7878
    api_token: someApiToken1234
  sonarr:
    host: 192.168.0.89
    port: 8989
    api_token: someApiToken1234
  

  You would change the above configuration to the following:

  radarr:
    - host: 192.168.0.78
      port: 7878
      api_token: someApiToken1234
  sonarr:
    - host: 192.168.0.89
      port: 8989
      api_token: someApiToken1234
  

• The --config flag has been renamed to --config-fileto make it more clear what it does.

Features

• Users can now specify multiple instances of the same type of Servarr and give them custom names and ordering. This allows users to manage multiple instances of the same Servarr, such as an Anime and TV Show instance of Sonarr. To configure, add a list of Servarrs under the respective type (e.g. radarr, sonarr, etc.). (#17)

  • You can specify ordering of your Servarrs and how they will appear in the UI via the weight field. The lower the weight, the further to the left the Servarr will appear in the UI.
  • You can also name your Servarrs whatever you wish. This name will be displayed in the UI. For example, to name your Sonarr instances:

    sonarr:
      - name: Anime
        host: 192.168.0.89
        api_token: someApiToken
    
      - name: TV Shows
        host: 192.168.0.88
        api_token: someOtherApiToken
    

  • This change also required the introduction of a new CLI flag to specify which Servarr you wish to interact with: --servarr-name. This corresponds directly to the value of the name field in your configuration. If you did not specify a name in the configuration, then default names are provided for you corresponding to the Servarr; For example, if you defined two Radarr instances with no names, they will be named Radarr 1 and Radarr 2, respectively.
  • Omitting the --servarr-name flag with multi-instance configurations will default to using the first instance that appears in your config. For example, for the following configuration:

    sonarr:
      - host: 192.168.0.89
        api_token: someApiToken
    
      - host: 192.168.0.88
        api_token: someOtherApiToken
    

    Running managarr sonarr list series will default to interacting with the Sonarr instance at 192.168.0.89. This is the same as running managarr sonarr list series --servarr-name 'Sonarr 1'.

• API tokens can now be fetched from files instead of needing to be hardcoded (#31). The following is an example config that loads the API token from a file:

  radarr:
    - host: 192.168.0.78
      api_token_file: /home/root/.config/radarr_token
  

• Configurations now interpolate environment variables (#23). This allows you to load sensitive information from environment variables. For example, to load the API token from an environment variable, you can do the following:

  radarr:
    - host: 192.168.0.78
      api_token: ${MY_RADARR_API_TOKEN_ENV_VAR}
  

  This is available for all fields in the configuration file.

Security Updates

• Updated OpenSSL to v0.10.70 to mitigate CVE-2025-24898

Miscellaneous

• Managarr now has a Matrix space! Feel free to drop in and message me directly if you're looking to discuss features, ideas, or just want to say, "Hi!".

cross-posted from: https://lemmy.world/post/12778644

In attempting to download American Dad, I've discovered the list of known shows with episode numbering issues because of TVDb's unflexible naming conventions. I found the option to "override and add to download queue" on the Interactive Search, but it didn't seem to be correcting the info on import. I finally found on the Servarr FAQ this bit about the override feature, "Note that this overruled information is not carried over to the import logic and manual imports may be required," indicating my override selections are ignored intentionally. So what's the point of this feature? Unless I'm missing something here, it seems completely useless to even have this option available if the override selections are then just completely ignored through the rest of the download and import process. Am I using this wrong?

I just added a series to my Sonarr list and a few of the episodes started downloading successfully (I did choose the option to search for monitored episodes when I added it) but several of them just say "Episode missing from disk" with the ⚠️ symbol next to them. When I click the "Search Monitored" button, nothing changes and nothing is added.

What's going on here? If I click on "Interactive Search", there are results that are returned and they don't have the red exclamation point and, as far as I can tell, they fit my criteria.

Why would some of these download and not others and why aren't the episodes with results downloading when I click "Search Monitored"? Am I misunderstanding the way this is supposed to work? I've never had this happen before but this never became an issue until I had to recreate the container.

This is a community for all things Sonarr. Be it updates, guides, questions, or setups feel free to post it all!