Skip to content

All the Arrs

Under Settings -> Movies / TV / Music, you'll find the configuration sections for each of the following:

  • Sonarr
  • Radarr
  • Lidarr

Each one does a different thing, but they're all based on the same codebase - so their configurations are similar.
As an example address, assume we use a service behind a reverse proxy, with each service being accessible at the following addresses:
Sonarr: https://app.example.com/sonarr
Lidarr: https://app.example.com/lidarr
Radarr: https://app.example.com/radarr

Configuring Connections

There are a number of options that the *arr suites use. These are almost all required for it to work.
They should be filled in in the following order:

  1. Enable.
    Toggle this to "on".
  2. Hostname/IP
    The IP address or hostname your Sonarr/Radarr/Lidarr is running on.
  3. Port
    Whatever port your instance is on. If you're behind an SSL proxy, this is likely 443, and SSL should be enabled.
  4. SSL
    Unless you have SSL enabled in your *arr, leave this off.
  5. API Key
    Whatever your API key is for whichever particular *arr you're trying to configure. This varies from site to site, we don't know what your API key is.
  6. Base URL
    Mostly only relevant if you've got a reverse proxy in play and have subdirectory proxies (i.e. domain.example.com/sonarr would have a baseurl of sonarr).
  7. Qualities/Profiles
    You will need to hit the button to load these from your *arr, and select what quality profile you want requests from Ombi to use in the dropdowns once they've been retrieved.
    Admins get a prompt to override these when making requests, and they can have different ones set per-user if you so choose. Here is where the default selection is.
  8. Folders/Root Folders
    These also need to be loaded from the relevant *arr. Hit the button, then once they've been retrieved you'll need to select them from the relevant dropdowns.
    Admins get a prompt to override these when making requests, and they can have different ones set per-user if you so choose. Here is where the default selection is.
  9. Tags (optional) This allows you to define a tag to be attached to anything added to *arr for quick identification in their lists.
  10. Sonarr
    1. Languages This is mostly to account for things like Anime vs TV, but it does need setting. Load them with the button, select from the dropdown.
    2. Enable Season Folders (Sonarr)
      This is just for Sonarr, and we recommend this being "On" for keeping files organised nicely.
  11. Radarr
    1. Minimum Availability Defines when your Radarr should look for this particular item. Setting this correctly can help reduce the chances of fakes and bad copies.
  12. Lidarr
    1. Album Folder
      Tells Lidarr to use individual folders for albums. This helps keep folders tidy.
  13. Submit
    Hit the button to save settings. If at any point one of the "Load" buttons didn't work, use the "Test Connectivity" button to see what message you get - it helps to confirm if the *arr is not responding at all, or is not authenticating (bad host/port vs bad API key).

Specific Settings

Below here are details for each setting specifically. The above should get your going - the below is for troubleshooting or advanced configs.
Coming soon to the docs: configuring multiple instances of Radarr.

Enabled

This switch tells Ombi whether to use this service or not. Don't run the service? Don't enable it.

Scan for Availability

This option tells Ombi to use the Arrs to check for availability (instead of a media server).
If you have set up a Plex/Emby/Jellyfin connection in Ombi, then Ombi will use that to detect what is available (and this should be disabled).
We recommend using the media server rather than this option - it's mainly for people who use things like XBMC and local players.

Add the user as a tag

This will add the username as a tag to requested content in the relevant *arr, allowing you to find them easily.

Hostname

This is the address you use to connect to the service. If it's running on the same machine as Ombi, localhost usually works.
If you're running the services (and Ombi itself) in docker containers, you could use the container IP.
If the services are on multiple machines, IP addresses tend to be useful here.
If, however, you use the service behind a reverse proxy, then the 'hostname' field is the bit from before the 'baseurl'.
In the examples above, this would be app.example.com.

Port

If you're not using a reverse proxy, this is whatever port you use to access the service (it's the number after the second ":" in the address bar). In the case of Sonarr, the default is 8989.
If you're using a reverse proxy without* SSL, the port will be 80 (pro-tip: don't do that).
If you're running _with SSL, the port will be 443.

SSL

If you're running a reverse proxy with SSL, and are going through that address rather than the direct internal address, this needs to be enabled. Otherwise, leave it off.

API key

This is the API key for each relevant service.
You can get this by looking under Settings -> General in each one.

Base URL

If you use a reverse proxy and have a baseurl configured in any of the services, you'll need to fill this in.
This tends to be the thing you put in after the hostname to access the service - in the example above for Lidarr, this field would need to have /lidarr added to it.

Quality Profiles

Depending on the service, you may have this appear several times.
There will be a button to 'get' these from the service. Click it, wait, and select one.
If it doesn't work, save the settings and "Test Connectivity". You may not be able to communicate with the service yet.

Root Folders

Depending on the service, you may have this appear several times. There will be a button to 'get' these from the service. Click it, wait, and select one.
If it doesn't work, save the settings and "Test Connectivity". You may not be able to communicate with the service yet.

Tag

This allows you to define a tag to be attached to anything added to *arr for quick identification in their lists.
In some instances Ombi will refuse to let you save settings without something in this field. We suggest opening the relevant Arr and tagging something with a default option (like 'request') to be able to use.

Submit

This button is used to save and activate your new settings.
This will not work if you have not filled in every option for the relevant service (folders, qualities, languages, seasons, albums, availability, tag).

Sonarr / Radarr

Default Minimum Availability

This tells Ombi what it should add movies to Radarr as - should it wait until they're available on disc to look for them, in theatres, announced...?
To try to avoid picking up fakes, Physical / Web is your best option.

Language Profile

There will be a button to 'get' these from the service. Click it, wait, and select one.
If it doesn't work, save the settings and "Test Connectivity". You may not be able to communicate with the service yet.

Default Root Folders

When setting up Sonarr/Radarr in Ombi, the option to "Load Folders" allows you to define what 'root folder' requested content should be put into by the relevant arr.
If you are using 'atomic' mapping (i.e. direct media location in a containerised arr), you will still need to define a root folder in it in order for you to be able to use Ombi.
Note, in some older versions of Sonarr this was not an issue as it would supply a default location if the API was queried, but this behaviour seems to have been removed.

Lidarr Specific

Metadata Profile

Lidarr uses these to say what it should pull in by an artist (compilations, mixtapes, albums, singles...).
Again, 'get' the options from the service and select one.

Album Folder

This tells Ombi that Lidarr wants things organised into individual subfolders per album. Usually, this should be ticked.

Radarr Specific

Radarr 4K

This option only appears when Movie4KRequests is turned on.

This is where you configure a second (additional) copy of Radarr for Ombi to send requests to, with its own root paths and quality profiles.
This is designed for people to be able to request a movie in multiple resolutions at once (usually SD or HD along with 4K), but could be set up to do SD and HD or any combination you want.
Note that Ombi is unaware of the resolution of the item in Plex/Emby/Jellyfin - it uses the media ID for matching to see if it's available. As a result, if someone requests 4K and HD, Ombi will say the content is available when either resolution is available, not both.

Sonarr Specific

Enable Season Folders

This tells Ombi that Sonarr wants things organised into Season subfolders. Usually, this should be ticked.

V3

If you still have this option, update your Ombi instance.
Sonarr made V3 their "stable" branch a while ago, and we now use the V3 API by default (in preparation for the V4 API).

Advanced

Any setting behind advanced is not recommended to be altered, unless you know what you are doing.

When a movie/series/album gets requested and approved, it will be added as unmonitored to the Arrs.
This means it will not auto download.