Running multiple Sonarr or Radarr instances does not require a separate Recyclarr installation for every server. Recyclarr can be configured to manage multiple instances from a single setup by defining each application separately in the configuration. This is useful for users who maintain separate media libraries, use different servers, or run dedicated Sonarr and Radarr instances for different types of content.
Each instance needs its own connection details, including the application URL and API key. Recyclarr then uses those definitions to determine where synchronization should be applied. Keeping the instances clearly separated in the configuration also helps prevent settings intended for one server from being applied to another.
The main challenge is making sure every instance has the correct URL, API key, configuration section, and target profiles. Docker networking also needs attention when the applications run in separate containers.
Create Separate Instance Definitions
Each Sonarr or Radarr server should have its own instance definition in the Recyclarr configuration.
For example, you might have:
- One Sonarr instance for TV shows
- Another Sonarr instance for anime
- One Radarr instance for standard movies
- Another Radarr instance for 4K movies
Each server can have a different URL and API key.
A simplified structure can look like this:
sonarr:
tv:
base_url: http://sonarr-tv:8989
api_key: YOUR_TV_SONARR_API_KEY
anime:
base_url: http://sonarr-anime:8989
api_key: YOUR_ANIME_SONARR_API_KEY
The exact configuration structure should match the Recyclarr version you are using. The important concept is that each server has a distinct instance definition.
Use a Different API Key for Each Instance
Every Sonarr or Radarr installation has its own API key.
Do not assume that the API key from one instance can be reused for another. Copy the API key from the settings of each individual server and associate it with the corresponding Recyclarr instance.
For example:
api_key: SONARR_INSTANCE_ONE_KEY
and:
api_key: SONARR_INSTANCE_TWO_KEY
Using the wrong API key can result in authentication errors or cause you to troubleshoot the wrong server.
If an API key has been regenerated, update the corresponding Recyclarr configuration.
Give Each Instance a Clear Name
Use descriptive names for multiple instances.
Names such as:
sonarr-main
sonarr-anime
radarr-main
radarr-4k
are much easier to identify than generic names such as:
server1
server2
server3
Clear names become especially useful when reading synchronization logs.
You can immediately identify which server Recyclarr is processing without having to remember which URL belongs to which library.
Configure Multiple Sonarr Instances
Multiple Sonarr servers can be managed from the same Recyclarr installation.
For example, one server might handle standard television content while another manages anime.
The important part is keeping their connection and profile configuration separate.
A conceptual configuration may look like:
sonarr:
main:
base_url: http://sonarr-main:8989
api_key: MAIN_API_KEY
anime:
base_url: http://sonarr-anime:8989
api_key: ANIME_API_KEY
The exact fields and structure depend on your Recyclarr release, so use the configuration format supported by your installed version.
After adding both instances, verify that each URL points to the intended Sonarr server.
Configure Multiple Radarr Instances
The same approach applies to Radarr.
For example, you could have one Radarr instance for standard movies and another for 4K content.
A conceptual setup might look like:
radarr:
movies:
base_url: http://radarr-main:7878
api_key: MAIN_RADARR_API_KEY
movies4k:
base_url: http://radarr-4k:7878
api_key: FOUR_K_RADARR_API_KEY
Each instance should have its own API key and reachable URL.
Keep the configuration for each server separate so that quality profiles and custom formats can be managed according to the requirements of that particular library.
Use Different Quality Profiles When Needed
Multiple instances often exist because the libraries have different requirements.
For example, a standard movie server might use one quality profile while a 4K server uses another.
Do not assume that every profile should receive the same configuration.
Review the profiles available on each instance and configure Recyclarr according to the requirements of that server.
This prevents a configuration intended for one media library from being unnecessarily applied to another.
Manage Custom Formats Across Multiple Instances
Custom formats can also be synchronized across multiple Sonarr or Radarr instances.
However, the same custom format configuration may not be appropriate for every server.
A standard movie library and a 4K movie library may have different scoring requirements. Similarly, an anime Sonarr instance may use different release preferences from a general TV instance.
Decide which custom formats each instance should manage rather than duplicating every setting everywhere.
Keep Instance-Specific Settings Separate
A useful configuration strategy is to separate settings according to the server they control.
For example:
Sonarr Main
├── Quality Profiles
└── Custom Formats
Sonarr Anime
├── Quality Profiles
└── Custom Formats
Radarr Main
├── Quality Profiles
└── Custom Formats
Radarr 4K
├── Quality Profiles
└── Custom Formats
This makes the configuration easier to maintain and reduces the chance of applying the wrong settings.
Check Docker Networking
Docker users need to pay particular attention to networking.
Suppose your containers are named:
sonarr-main
sonarr-anime
radarr-main
radarr-4k
recyclarr
Recyclarr must be able to resolve and reach those container names through the appropriate Docker network.
For example:
base_url: http://sonarr-main:8989
may work if both containers share the required network.
Using:
base_url: http://localhost:8989
from inside Recyclarr may not work because localhost refers to the Recyclarr container itself.
Check the Docker Compose configuration and confirm that the relevant containers are connected to the same network when required.
Verify Every URL Individually
Do not assume that because one Sonarr or Radarr instance works, all instances are reachable.
Test each configured URL separately.
For example:
Sonarr Main → http://sonarr-main:8989
Sonarr Anime → http://sonarr-anime:8989
Radarr Main → http://radarr-main:7878
Radarr 4K → http://radarr-4k:7878
A typo in one hostname or port can affect only that instance while the others continue working normally.
This makes individual verification important when troubleshooting multiple-server configurations.
Verify Every API Key
Each instance should be checked independently.
If three servers synchronize correctly and one fails, compare the working and failing definitions.
The problem may simply be that the failing instance has:
- An outdated API key
- A copied key from another server
- An incomplete value
- An incorrect configuration reference
Updating only the affected instance is preferable to changing the entire Recyclarr configuration.
Check the Synchronization Output
Logs become increasingly important as the number of managed instances grows.
A synchronization run should provide enough information to determine which server is being processed and whether an error occurred.
Look for the instance name, connection status, profile processing, custom format operations, and errors.
If only one server fails, concentrate on that instance rather than rebuilding the entire configuration.
Run a Manual Sync While Testing
Manual synchronization is useful when adding a new Sonarr or Radarr instance.
Add the instance, verify its configuration, and run a manual sync.
Then check the target application.
This lets you confirm the new server works before relying on an automated schedule.
It also makes errors easier to identify because you can immediately correlate the command output with the changes in Sonarr or Radarr.
Check the Correct Sonarr or Radarr Instance
Multiple servers can make it surprisingly easy to check the wrong application.
If Recyclarr reports that a profile or custom format was updated, make sure you are looking at the corresponding server.
For example, changes made to a 4K Radarr instance will not appear in the standard Radarr instance.
Keep browser tabs, container names, and configuration names clearly identifiable when managing several installations.
Avoid Duplicate Instance Names
Each configured instance should have a unique and descriptive identifier.
Avoid ambiguous names such as:
server
server2
newserver
test
Instead, use names based on their purpose:
sonarr-tv
sonarr-anime
radarr-movies
radarr-4k
This makes troubleshooting and maintenance much easier.
Use Separate Configuration Files When Appropriate
A single configuration can be convenient for a small number of instances.
Larger setups may benefit from separating configurations logically, depending on how you manage Recyclarr.
Separate files can make it easier to maintain different environments or server groups, but they also introduce another layer to manage.
If you use multiple files, make sure Recyclarr is actually loading the files you expect.
A configuration stored on the host is not useful if the running container cannot access it.
Be Careful With Shared Settings
Sharing the same settings across multiple servers can reduce duplication, but not every server necessarily needs identical configuration.
For example, a standard Radarr installation might prioritize different release characteristics from a 4K installation.
Before applying a shared configuration, check whether the target instances have compatible quality profiles, custom formats, and media requirements.
Use shared configuration where the requirements are genuinely the same rather than simply because the servers use the same application.
Check Configuration After Adding an Instance
A new instance should be tested before adding more complexity.
Use this sequence:
- Add the new instance.
- Verify its URL.
- Verify its API key.
- Confirm network connectivity.
- Check the target profile.
- Run a manual synchronization.
- Review the logs.
- Confirm the expected changes in Sonarr or Radarr.
- Add scheduling after successful testing.
This makes it easier to identify exactly which step is responsible for a problem.
Troubleshoot One Instance at a Time
When multiple servers are configured, troubleshooting everything simultaneously can become difficult.
If one Sonarr instance fails while another works, use the working instance as a reference.
Compare:
- Base URL
- API key
- Docker network
- Container name
- Port
- Configuration structure
- Quality profile
- Recyclarr version
- Sonarr version
This comparison often reveals a small difference that explains the failure.
Common Problems With Multiple Instances
Several problems appear repeatedly in multi-instance setups.
Incorrect URL
The configured hostname or port does not point to the intended Sonarr or Radarr server.
Wrong API Key
The key belongs to another instance or has been regenerated.
Docker Network Issue
Recyclarr cannot resolve or reach one of the application containers.
Wrong Profile
The configuration targets a profile that does not exist on the selected instance.
Duplicate Configuration
The same settings are being applied to instances that require different configurations.
Wrong Server Checked
Recyclarr synchronized one instance while the user inspected another.
Configuration Path Problem
Recyclarr is loading a different configuration file from the one being edited.
Scheduling Problem
Manual synchronization works, but the automatic task does not execute correctly.
Frequently Asked Questions
Can Recyclarr manage multiple Sonarr instances?
Yes. Multiple Sonarr instances can be defined and managed from a Recyclarr setup, with each instance using its own connection details and configuration.
Can Recyclarr manage multiple Radarr instances?
Yes. Multiple Radarr servers can be configured, provided Recyclarr can reach each instance and has valid API credentials.
Does every Sonarr instance need its own API key?
Each Sonarr installation has its own API access credentials. Configure the appropriate API key for each instance rather than assuming one key applies to every server.
Can I use different settings for each Sonarr or Radarr instance?
Yes. Instance-specific configuration allows you to manage profiles, custom formats, and other supported settings according to the needs of each server.
Can Recyclarr manage Sonarr and Radarr at the same time?
Yes. A Recyclarr setup can be used to synchronize supported configuration across both Sonarr and Radarr instances.
Why does one instance sync while another does not?
Check the failing instance’s URL, API key, Docker network, configuration, profile names, and logs. A single incorrect value can affect one server without affecting the others.
Does Docker change how multiple instances should be configured?
Docker can affect the URLs Recyclarr uses to reach Sonarr and Radarr. Container hostnames and shared Docker networks may be required instead of localhost.
Should every Sonarr and Radarr instance use identical configurations?
Not necessarily. Different libraries can have different quality profiles, custom formats, and release requirements. Configure each instance according to its actual purpose.
Conclusion
Recyclarr can simplify configuration management across multiple Sonarr and Radarr installations by keeping each server defined separately within the synchronization setup. Every instance should have the correct URL, API key, network access, and target configuration.
Clear instance names make the setup easier to maintain, while separate profile and custom format settings help prevent unwanted changes between different media libraries. Docker users should also verify container networking because localhost does not normally refer to another container.
Test each new instance with a manual synchronization before relying on scheduled runs. If one server fails while others work, compare its connection details, API credentials, networking, and configuration against a working instance. This approach keeps multi-instance Recyclarr setups organized and makes troubleshooting considerably easier.