For Sonarr v4 specific FAQ entries - Please see the v4 FAQ here
- Sonarr does not regularly search for episode files that are missing or have not met their quality goals. Instead, it fairly frequently queries your indexers and trackers for all the newly posted episodes/newly uploaded releases, then compares that with its list of episodes that are missing or need to be upgraded. Any matches are downloaded. This lets Sonarr cover a library of any size with just 24-100 queries per day (RSS interval of 15-60 minutes). If you understand this, you will realize that it only covers the future though.
- So how do you deal with the present and past? When you're adding a show, you will need to set the correct path, profile and monitoring status then use the Start search for missing checkbox. If the show has had no episodes and hasn't been released yet, you do not need to initiate a search.
- Put another way, Sonarr will only find releases that are newly uploaded to your indexers. It will not actively try to find releases uploaded in the past.
- If you've already added the show, but now you want to search for it, you have a few choices. You can go to the show's page and use the search button, which will do a search and then automatically pick episode(s). You can search individual episodes or seasons automatically or manually. Or you can go to the Wanted tab and search from there.
- If Sonarr has been offline for an extended period of time, Sonarr will attempt to page back to find the last release it processed in an attempt to avoid missing a release. As long as your indexer supports paging and it hasn't been too long Sonarr will be able to process the releases it would have missed and avoid you needing to perform a search for the missed episodes.
Active searching (via the indexer's API) is only done in the below situations. Note that the same rules as normal apply: series + episode must be monitored and episodes without an airdate are skipped
- Triggered Automatic or Manual Search
- User or API triggered search. Typically executed by clicking the Automatic or Manual Search buttons on a specific episode, season, or series.
- Adding a show using the Add and Search button
- Using Wanted => Missing or Wanted => Cutoff Unmet to do one or more searches
- Recent Episodes
- New episodes from TVDb in Skyhook that aired in the last 14 days or within 1 day into the future (to cover those episodes that may release a bit early) will be automatically searched for those episodes after the series folder is rescanned (to catch things imported outside of Sonarr)
- Absolute Numbering Episodes with absolute numbers added to TVDb in Skyhook that aired in the last 14 days or within 1 day into thr future
Generally Quality Trumps All. If you wish to have Quality not be the main priority - you can merge your qualities together. See TRaSH's Guide
- Quality
- Custom Format Score
- Protocol (as configured in the relevant Delay Profile)
- Episode Count*
- Episode Number
- Indexer Priority
- Seeds/Peers (If Torrent)
- Age (If Usenet)
- Size
REPACKS and PROPERs are v2 of Qualities and thus rank above a non-repack of the same quality. Set Media Management => File Management Download Proper & Repacks
to "Do Not Prefer" and use TRaSH's Repack/Proper Custom Format with a positive score as suggested by TRaSH's Guides
* Use Custom Formats and TRaSH Guide's season pack custom format with a score greater than zero to prefer season packs.
- Shut Sonarr down
- Run serviceuninstall.exe that's in the Sonarr directory
- Run Sonarr.exe as an administrator once to give it proper permissions and open the firewall. Once complete, then you can close it and run it normally.
- (Optional) Drop a shortcut to Sonarr.exe in the startup folder to auto-start on boot.
- Go to System => Backup in the Sonarr UI
- Click the Backup button
- Download the zip after the backup is created for safekeeping
- Find the location of the AppData directory for Sonarr
- Stop Sonarr - This will prevent the database from being corrupted
- Copy the contents to a safe location
Restoring to an OS that uses different paths will not work (Windows to Linux, Linux to Windows, Windows to OS X or OS X to Windows), moving between OS X and Linux may work, since both use paths containing /
instead of \
that Windows uses, but is not supported. You'll need to manually edit all paths in the database or use Toolbarr.
- Re-install Sonarr (if applicable / not already installed)
- Run Sonarr
- Navigate to System => Backup
- Select Restore Backup
- Select Choose File
- Select your backup zip file
- Select Restore
- Re-install Sonarr (if applicable / not already installed)
- Find the location of the AppData directory for Sonarr
- Stop Sonarr
- Delete the contents of the AppData directory (Including the .db-wal/.db-journal files if they exist)
- Restore from your backup
- Start Sonarr
- As long as the paths are the same, everything will pick up where it left off
CAUTION: Restoring on a Synology requires knowledge of Linux and Root SSH access to the Synology Device.
- Re-install Sonarr (if applicable / not already installed)
- Find the location of the AppData directory for Sonarr
- Stop Sonarr
- Connect to the Synology NAS through SSH and log in as root
On some installations, the user is different than the below commands: chown -R sc-Sonarr:Sonarr *
- Execute the following commands:
rm -r /usr/local/Sonarr/var/.config/Sonarr/Sonarr.db
cp -f /tmp/Sonarr_backup/* /usr/local/Sonarr/var/.config/Sonarr/
- Update permissions on the files:
cd /usr/local/Sonarr/var/.config/Sonarr/
chown -R Sonarr:users *
chmod -R 0644 *
Authentication is now mandatory in v4 of Sonarr and the AuthenticationMethod
type None
is no longer valid - please see this v4 FAQ - Forced Authentication
To disable authentication (to reset your forgotten username or password) you will need need to edit config.xml
which will be inside the Sonarr Appdata Directory
- Stop Sonarr
- Open config.xml in a text editor
- Find the authentication method line will be
<AuthenticationMethod>Basic</AuthenticationMethod>
or <AuthenticationMethod>Forms</AuthenticationMethod>
(Be sure that you do not have two AuthenticationMethod entries in your file)
- Change the
AuthenticationMethod
line to <AuthenticationMethod>External</AuthenticationMethod>
(If you are running an old v3 version, the correct value is None
instead of External
)
- Restart Sonarr
- Sonarr will now be accessible without a password, you should go the
Settings: General
in the UI and set your username and password
This is expected. With a setup that supports hardlinks, double space will not be used. Below is how the Torrent Process works.
- Sonarr will send a download request to your client, and associate it with a label or category name that you have configured in the download client settings. Examples: movies, tv, series, music, etc.
- Sonarr will monitor your download clients active downloads that use that category name. This monitoring occurs via your download client's API.
- Completed files are left in their original location to allow you to seed the file (ratio or time can be adjusted in the download client or from within under the specific download client). When files are imported to your media folder will hardlinkthe file if supported by your setup or copy if not hard links are not supported.
- If the "Completed Download Handling - Remove Completed" option is enabled in Sonarr's settings, Sonarr will delete the original file and torrent from your download client, but only if the download client reports that seeding is complete and torrent is stopped (i.e. paused). See TRaSH's Download Client Guides for how to configure your download client optimally.
Hard links are enabled by default. A hard link will not use any additional disk space. The file system and mounts must be the same for your completed download directory and your media library. If the hard link creation fails or your setup does not support hard links then it will fall back and copy the file.
Sonarr consists of two main branches of code, main
and develop
.
main
is released periodically, when the develop
branch is stable
develop
is for pre-release testing and people willing to live on the edge. When a feature is marked as in develop
it will only be available to users running the develop
branch, once it has been move to live (in main
) it is officially released.
-
There are two parts to the episode count, one being the number of episodes (Episode Count) and the other being the number of episodes with files (Episode File Count), each one uses slightly different logic to give you the overall progress for a series or season.
- Episode Count => Episode has already aired AND is monitored OR - Episode has a file
- Episode File Count => Episode has a file
-
If a series has 10 episodes that have all aired and you do not have any files for them you would have 0/10 episodes, if you unmonitored all the episodes in that series you would have 0/0 and if you got all the episodes for that series, regardless of if the episodes are monitored or not, you would have 10/10 episodes.
- By default Sonarr doesn't listen to requests from all systems (when not run as administrator), it will only listen on localhost, this is due to how the Web Server Sonarr uses integrates with Windows (this also applies for current alternatives). If Sonarr is run as an administrator it will correctly register itself with Windows as well as open the Firewall port so it can be accessed from other systems on your network. Running as admin only needs to happen once (if you change the port it will need to be re-run).
- Sonarr refreshes series and episode information in addition to rescanning the disk for files every 12 hours. This might seem aggressive, but is a very important process. The data refresh from our TVDb proxy is important, because new episode information is synced down, air dates, number of episodes, status (continuing/ended). Even shows that aren't airing are being updated with new information.
- The disk scan is less important, but is used to check for new files that weren't sorted by Sonarr and detect deleted files.
- The most time consuming portion is the information refresh (assuming reasonable disk access speed), larger shows take longer due to the number of episodes to process.
- No you cannot disable the task nor should you through any SQL hackery. The refresh series task queries the upstream Skyhook proxy and checks to see if the metadata for each series (ids, episodes, summaries, etc.) has updated compared to what is currently in Sonarr. If necessary, it will then update the applicable movies.
- A common complaint is the Refresh task causes heavy I/O usage.
- The main setting is "Rescan Series Folder after Refresh". If your disk I/O usage spikes during a Refresh then you may want to change the Rescan setting to
Manual
.
- Do not change this to
Never
unless all changes to your library (new movies, upgrades, deletions etc) are done through Sonarr.
- If you delete movie files manually or via Plex or another third party program, do not set this to
Never
.
- The other setting that can be changed is "Analyze video files" which is advised to be enabled if you use tdarr or otherwise externally modify your files. If you do not you can safely disable "Analyze video files" to reduce some I/O.
It is not possible to disable this task. If this task is running for long enough that you feel it's the problem, something else is going on that needs to be solved instead of stopping this task.
- This number shows the count of episodes in your download client's queue and the last 60 items in its history that have not yet been imported. If the number is blue it is operating normally and should import episodes when they complete. Yellow means there is a warning on one of the episodes. Red means there has been an error. In the case of yellow (warning) and red (error), you will need to look at the queue under Activity to see what the issue is (hover over the icon to get more details).
- You need to remove the item from your download client's queue or history to remove them from Sonarr's queue.
-
Series Type impacts how Sonarr searches for series. A series type is based on how the series is released on one's indexers and is not necessarily the true 'type' of the series.
-
Most shows should be Standard
. For daily shows which are typically released with a date, Daily
should be used. Finally, there is anime where using Anime
is usually right, but sometimes Standard
can work better, so try the other one if you're having issues.
-
Please note that if the series type is set to anime and if none of your enabled indexers have any anime categories configured then it effectively skips the indexer and may appear that it is not searching.
-
Please note that the Anime type does not have any concept of Season Packs or Seasons and will cause each episode individually to be searched.
-
Please note that not all indexers support season/episode (standard) searches.
-
Series types can be modified from Mass Editor or from Edit
when viewing a series. Note that the series type is selectable at import.
-
If Anime Series Type is used - it is possible to also have your indexer searched with the standard type as well.
- Anime - Episodes released using an absolute episode number
- Daily - Episodes released daily or less frequently that use year-month-day (2017-05-25)
- Standard - Episodes released with SxxEyy pattern
Below are some example release names for each show type. The specific differentiating piece is noted in bold.
If Anime Series Type is used - it is possible to also have your indexer searched with the standard type as well.
Logs will show Searching indexers for [The Witcher : 2021-12-20]
- Some.Daily.Show.2021.03.04.1080p.HDTV.x264-DARKSPORT
- A.Daily.Show.with.Some.Guy.2021.03.03.1080p.CC.WEB-DL.AAC2.0.x264-null
- DailyShow.2021.03.08.720p.HDTV.x264-NTb
¶ Standard
Logs will show Searching indexers for [The Witcher : S01E09]
- The.Show.S20E03.Episode.Title.Part.3.1080p.HULU.WEB-DL.DDP5.1.H.264-NTb
- Another.Show.S03E08.1080p.WEB.H264-GGEZ
- GreatShow.S17E02.1080p.HDTV.x264-DARKFLiX
Logs will show Searching indexers for [The Witcher : S01E09 (09)]
- Anime.Origins.E04.File.4_.Monkey.WEB-DL.H.264.1080p.AAC2.0.AC3.5.1.Srt.EngCC-Pikanet128.1272903A
- [Coalgirls] Human X Monkey 148 (1920x1080 Blu-ray FLAC) [63B8AC67]
- [KaiDubs] Series x Title (2011) - 142 [1080p] [English Dub] [CC] [AS-DL] [A24AB2E5]
The same process applies for moving/changing Series paths as well
If you have adjusted your Series Name format after Sonarr has already created some Series folders, Sonarr will not automatically rename existing folders. In order to trigger a rename of these folders the following steps should be taken:
- Series
- Click on "Select Series"
- Select what series need their folder renamed
- Click on "Edit"
- Change Root Folder to the same Root Folder that the series currently exist in
- Select "Yes, move the files"
If you are using Plex or Emby, this will trigger re-detection of intros, thumbnails, chapters, and preview metadata.
- Go to Settings and then the General tab and show advanced settings (use the toggle by the save button).
- Under the Updates section change the branch name to
main
or develop
- Save
This will not install the bits from that branch immediately, it will happen during the next update.
- main - - (Default/Stable): This has been tested by users on nightly (
develop
) branch and it's not known to have any major issues. This branch should be used by the majority of users. On GitHub, this is the main
branch.
- develop - - (Beta/Unstable) : This is the bleeding edge. It is released as soon as code is committed and passes all automated tests. This build may have not been used by us or other users yet. There is no guarantee that it will even run in some cases. This branch is only recommended for advanced users. Issues and self investigation are expected in this branch. Use this branch only if you know what you are doing and are willing to get your hands dirty to recover a failed update. This version is updated immediately.
Warning: You may not be able to go back to main
after switching to this branch. On GitHub, this is the develop
branch.
v3 non-docker installs cannot be upgraded directly to v4 and require installing Sonarr v4
- Note: If your install is through Docker append
:release
, :latest
, :nightly
, or :develop
to the end of your container tag depending on who makes your builds.
- Go to System and then the Updates tab
- Newer versions that are not yet installed will have an update button next to them, clicking that button will install the update.
v3 cannot be updated to beta v4 and requires manually installing. Refer to the v4 Beta Announcement
- Repull your tag and update your container
¶ Can I switch from develop
back to main
?
You can (almost) always increase your risk.
main
can go to develop
- See below or otherwise check with the development team to see if you can switch from
develop
to main
for your given build.
- Failure to follow these instructions may result in your Sonarr becoming unusable or throwing errors. You have been warned. If the below errors are encountered then you are using a newer database with an older *Arr version which is not supported. Upgrade *Arr to the version you were previously on or newer.
- Example Error Messages:
Error parsing column 45 (Language=31 - Int64)
The DataMapper was unable to load the following field: 'Languages' value
ID does not match a known language Parameter name: id
- Other similar database errors around missing columns or tables.
¶ How does Sonarr handle scene numbering issues (American Dad!, etc)?
¶ How Sonarr handles scene numbering issues
- Sonarr relies on TheXEM, a community driven site that lets users create mappings of shows that the scene (the people that post the files) and TheTVDb (which typically follows the network's numbering). There are a number of shows on there already, but it is easy to add another and typically the changes are accepted within a couple days (if they're correct). TheXEM is used to correct differences in episode numbering (disagreement whether an episode is a special or not) as well as season number differences, such as episodes being released as S10E01, but TheTVDb listing that same episode as S2017E01.
- XEM typically fixes the issues when release groups' (colloquially known as 'the scene') numbering does not match TVDb numbering so Sonarr doesn't work. Well enter XEM which creates a map for Sonarr to look at.
- Releases double episodes in a single file since that is how they air but TVDb marks each episode individually.
- Release groups use a year for the season S2010 and TVDb uses S01.
- XEM works in most cases and keeps it running smooth without you ever knowing. However as with most things, there will always be a problematic exceptions and in this case there is a list of them.
Certain indexers or release groups may follow TVDb rather than Scene
(i.e. XEM).
If this is observed, please submit them via the scene mapping form.
This by no means is an all inclusive list of shows that have known issues with scene mapping; however, these are some common ones.
- This is an incomplete list of the known shows and how/why they're problematic:
- American Dad
- Due to network season changes, American Dad is typically off by 1 season between releases and TVDb. Refer to the XEM map for details
- American Dad is currently on S19 based on TVDb or S18 based on Scene at the time of this writing. So searching in Sonarr for Season 19 will only return Season 18 results because of the XEM map.
- If you have an indexer / release groups with Season 19 episodes, please submit them via the scene mapping form and ensure they are not already requested
- Paw Patrol
- Double episode files vs single episode TVDb but also not all episodes are doubles so the map can get added wrong pointing to which ones are singles vs doubles
- Pokémon
- On TheXem, Pokemon is tracking dubbed episodes. So if you want subbed episodes, you may be out of luck. If certain release groups are following TVDb and not XEM mapping, please submit them via the scene mapping form and ensure they are not already requested
- La Casa de Papel / Money Heist
- Kamen Rider
- The anthology entry (TVDb ID 74096) should be used in Sonarr for automation
as this show has both an anthology entry (collecting all seasons) and the individual seasons listed as separate entries on TVDb. Due to the anthology entry having individual season name mappings on TheXEM it is not possible to add the individual season entries to Sonarr without manually downloading and importing releases.
- Bleach: Thousand-Year Blood War
- The newest season of Bleach: Thousand-Year Blood War is being released with a variety of different naming schemes making it difficult to automate and potentially overwriting some of your existing episodes. It can only be automated if your release group is either:
- Releasing the episodes as S17Exx numbering, or
- Releasing them with the correct Season 2 series title (found here https://thexem.info/xem/show/5476) and have began this new arc at absolute episode number 1.
- Great Asian Railway Journeys
- Great Asian Railway Journeys was first aired as 20 smaller episodes, but was later re-aired as 10 long episodes. These longer combined episodes were added as Specials, and should be named accordingly. (S00E01, etc, ...)
- Horizon
- A show that sporadically airs episodes since 1964. This makes mapping particularly difficult, as you can see on TheXEM. Those interested can find the original discussion on the Sonarr discord here.
- Kaleidoscope (2023)
- Kaleidoscope (2023) was released on Netflix as a non-linear show meaning that every user got a different order when watching the series. This causes an issue for Sonarr as release groups have different episode orders for the show. In order to prevent incorrect mapping of episodes Sonarr will not automatically grab episodes and you will need to grab and import the episodes manually. You can match them based on episode title, or by previewing the first few seconds and seeing the episode 'color' matching the title.
Some examples of other shows that commonly have issues, most of which may be resolved by TheXEM mappings are: Arrested Development, Kitchen Nightmares (US), Mythbusters, Pawn Stars.
There can be multiple reasons why Sonarr is not able to find or import episodes for a particular series, and there are two methods for "correcting" these failures.
- Sonarr tries to search first using TVDBid or IMDBid, if your indexer supports those kinds of searches. If there are no results, or you have no indexers which support ID-based searches, Sonarr falls back to searching text-based titles.
- Sonarr does not use aliases nor translations (i.e. any foreign language titles) from TVDb.
- The text-based search must match exactly. This includes the year, if a year is required (listed on TVDB with a year after the series title).
- The text-based search is only for the English translation of the series title from TVDB. Other languages are not searched.
- The site https://thexem.info is used to correct scene/episode mappings, and also to add aliases to be searched for series or season names. Note that this is primarily for Anime only. Please check this site for corrections if you have a mismatch between season/episode results and the ones you expect. There is a #xem channel on Discord to talk about changes to the site. Xem is the only way to fix Japanese Anime aliases. Additonal information on XEM's usage can be found in the faq entry How Sonarr Handles scenen numbering issues
- The Scene Mapping Table is what is primarily to be used for series aliases for non-Anime series only. This table is manual. Please search first to be sure your request has not been made, and provide a release name example with your request. This is the current list of previous requests for your review. This is the form for requesting new mappings. Requests to this table are added manually by devs, and can take up to 2 weeks to take effect. Please remember that all aliases must be searched by all Sonarr users for every episode/season search, which can dramatically increase search times and API hits.
- We are aware that some series are just plain difficult. You may also wish to review the FAQ Entry for Problematic Shows and Release Group vs. TVDb numbering issues.
- TVDb has a 1-3 hour cache on their API.
- TVDb's API then needs to populate through their CDN cache which takes up to an hour.
- Sonarr's Skyhook has a much smaller few hour cache on top of that.
- Additionally, Sonarr only runs the Refresh Series task every 12 hours. This task can be manually ran from System => Tasks; "Update All" from the Series Index, or manually ran for a specific series on that series's page.
- Therefore for a change on TVDb to get into Sonarr automatically it will typically take between 3 and 19 hours (3 + 1 + 3 + 12)
- Episode titles in English are the only titles synced. If there is no English translation, then the episode title will be TBA.
- If you know a TVDb update was made more than 24 hours ago, and you have refreshed the series in Sonarr, then please come discuss on our Discord.
- In the event that TheTVDb is unavailable Sonarr is unable to get search results and you will be unable to add any new series by searching. You may be able to add a new series by the TVDbID if you know what it is, the UI explains how to add it by an ID.
- Sonarr cannot add any series that does not have an English language title. If you try to add a series via TVDb ID that does not have an English title. If no English title exists for that series on TheTVDb it will need to be added and then one will need to wait for TVDb's cache to clear.
- The show must be a TV Series, and not a movie. It must also exist on TVDb. If it is on IMDB, TMDB, or anywhere else, but not on TVDb you cannot add the show.
- The series must exist on TVDb
- Certain series may actually be considered continuations are and seasons in their primary series.
- Sonarr cannot add any series that does not have an English language title. If you try to add a series via TVDb ID that does not have an English title then the series will not be found. If no English title exists for that series on TheTVDb it will need to be added (if available).
- Check the URL / series - Sonarr does not support movies; use Radarr for movies
- There are two primary causes of this error that are listed below.
- This error often occurs when two series are named with the same title on TheTVDB, if this is the case the second series should have the year appended to the series title.
- To rectify this, wait for someone to eventually (maybe) update TVDb or update TVDb yourself. Once corrected and once approved by TVDb's moderators, due to TVDb's API issues, once updated you'll need to wait 30+ hours before the corrected title can be used in Sonarr.
- It will also happen with two similarly named series that may only differ by punctuation, if this is the case please report this on the Sonarr Discord.
- Joe's Show (2022)
- Joes Show (2022)
- The episode(s) on TVDb do not have an absolute number assigned. Update the series on TVDb if required and then wait the 36-48 hours for the update to clear TVDb's internal cache and load into Sonarr
- Within Sonarr, Episode Air Date and Times shown in the browser are based of the client's time/timezone, all times are sent from Sonarr to the browser as UTC times (ISO-8601 formatted to be exact)
- TVDb dictates - with exceptions for streaming services - that the airtime and date is based on the Primary Airing Network's local time in the country's most popular city. See TVDb's FAQ entry for details
- Episode Air Dates and Air Time on TVDb is converted to UTC and uses Sonarr's Timezone that is mapped in Skyhook by the Sonarr team for the Network TVDb has for the series.
- In the rare case a network is not mapped then the time in TVDb will be assumed to be US EST (UTC-5).
- If the airtime does not seem to align when converting from the airtime Network's local timezone to your browser's timezone then it is likely the network needs to be mapped in Skyhook. Contact the development team on Discord for support with updating the Network's timezone.
- Library Import shows "Existing" or you get an error of "Path is configured for an existing series"
- This occurs when trying to add a series or edit an existing series's path that already is assigned to a different series.
- Likely this was caused by not correcting a mismatched series when the user imported their library.
- Locate and correct the movie that is already assigned to that series's path.
- Series Index
- Table View
- Options => Add path as a column
- Sort and find the movie at the noted problematic path.
- Alternatively, delete the series using the existing path from Sonarr
- It's the easy-privacy blocklist. They basically block any url with /api/log? in it. Look over the list and tell me if you think that blocking all the urls in that list is a sensible idea, there are dozens of urls in there that potentially break sites. You selected that in your adblocker. Easy solution is to whitelist the domain Sonarr is running on. But I still recommend checking the list.
- If you experience any weird UI issues like the Library page not listing anything or a certain view or sort not working, try viewing in a Chrome Incognito Window or Firefox Private Window. If it works fine there, clear your browser cache and cookies for your specific ip/domain. For more information, see the Clear Cache Cookies and Local Storage wiki article.
- Sonarr was unable to read your config file on start-up as it became corrupted somehow. In order to get Sonarr back online, you will need to delete
.xml
in your AppData Folder once deleted start Sonarr and it will start on the default port (8989), you should now re-configure any settings you configured on the General Settings page.
¶ Invalid Certificate and other HTTPS or SSL issues
- If you're on non-Windows, most likely your mono's certificates are out of date and need to be synced. See the section about mono ssl in the installation article for details
- Your download client stopped working and you're getting an error like
Localhost is an invalid certificate
?
- Sonarr now validates SSL certificates. If there is no SSL certificate set in the download client, or you're using a self-signed https certificate without the CA certificate added to your local certificate store, then Sonarr will refuse to connect. Free properly signed certificates are available from let's encrypt.
- If your download client and Sonarr are on the same machine there is no reason to use HTTPS, so the easiest solution is to disable SSL for the connection. Most would agree it's not required on a local network either. It is possible to disable certificate validation in advanced settings if you want to keep an insecure SSL setup.
Depending on your OS, there are multiple possible ways.
- In
Settings
=> General
on some OS'es, there is a checkbox to launch the browser on startup.
- When invoking Sonarr, you can add
-nobrowser
(*nix) or /nobrowser
(Windows) to the arguments.
- Stop Sonarr and edit the config.xml file, and change
<LaunchBrowser>True</LaunchBrowser>
to <LaunchBrowser>False</LaunchBrowser>
.
¶ VPNs, Jackett, and the *ARRs
- Unless you're in a repressive country like China, Australia or South Africa, your torrent client is typically the only thing that needs to be behind a VPN. If you're in a repressive country noted above it is likely your connection to your trackers needs to be VPN'd as well - in other words Jackett behind a VPN or Prowlarr using an Indexer Proxy. Other *Arr apps not connecting to trackers should not be behind a VPN.. Because the VPN endpoint is shared by many users, you can and will experience rate limiting, DDOS protection, and ip bans from various services each software uses.
- In other words, putting the *Arrs (Lidarr, Prowlarr, Radarr, Readarr, and Lidarr) behind a VPN can and will make the applications unusable in some cases due to the services not being accessible.
To be clear it is not a matter if VPNs will cause issues with the *Arrs, but when: image providers will block you and cloudflare is in front of most of *Arr servers (updates, metadata, etc.) and liable to block you too
- Many private trackers will ban you for using or accessing them (i.e. using Jackett or Prowlarr) via a VPN.
- If a VPN is required and Docker is used it is recommended to use Hotio or Binhex's Download Client + VPN Containers.
- If a VPN is required and Docker is not used your VPN client must support split tunneling so only the required (Download Client) apps are behind the VPN.
- Many issues with accessing trackers can be resolved by using Google or Cloudflare's DNS servers in lieu of your ISP's DNS servers.
- In some cases (i.e. UK ISPs) you may need to put your torrent download client behind a VPN and Jackett/Prowlarr as follows:
- put Jackett behind the VPN and ensure split tunneling allows local access
- for Prowlarr configure your vpn client to provide a proxy and add the proxy in Settings => Indexers. Give the proxy a tag and any indexers that need to use it the same tag.
- If absolutely required and if your vpn does not provide a way to create a proxy you may put Prowlarr behind the VPN and ensure split tunneling allows local access.
- These messages are completely normal and come from the RSS feeds that Sonarr checks to see if there are episodes you do want, usually these only appear in debug/trace logging, but in the event of an problem processing an item you may see a warning or error. It is safe to ignore the warnings/errors as well since they are for shows you do not want, in the event it is for a show you want, open up a support thread on the forums.
- When a torrent that is still seeding is imported, it is copied or hard linked (if enabled and possible) so that the torrent client can continue seeding. In an ideal setup, the torrent download folder and the library folder will be on the same file system and look like it (Docker and network shares make this easy to get wrong), which makes hard links possible and minimizes wasted space.
- In addition, you can configure your seed time/ratio goals in Sonarr or your download client, setup your download client to pause or stop when they're met and enable Remove under Completed and Failed Download Handler. That way, torrents that finish seeding will be removed from the download client by Sonarr.
- This is simple, please see this link for more information here
[]
¶ Help, my Mac says Sonarr.app is damaged and cannot be opened
Database corruption occurring when upgrading to v4 means your existing v3 database is corrupt. v4 does not create database corruption. Downgrading to v3 or staying on v3 does not and will never fix the underlying corruption. Sonarr v3 is end of life and unsupported
- Errors of
Error creating log database
indicate issues with logs.db
- This can quickly be resolved by renaming or removing the database. The logs database contains unimportant information regarding commands history and update install history, and Info, Warn, and Error entries
- Errors of
Error creating main database
or generic database disk image is malformed
with no specified database indicate issues with sonarr.db
- Continue with the steps noted below
- This means your SQLite database that stores most of the information for Sonarr is corrupt. Your options are to try (a) backup(s), try recovering the existing database, try recovering the backup(s), or if all else fails starting over with a fresh new database.
- This error may show if the database file is not writable by the user/group *Arr is running as. Permissions being the cause will likely only be an issue for new installs, migrated installs to a new server, if you recently modified your appdata directory permissions, or if you changed the user and group *Arr run as.
- Your best and first option is to try restoring from a backup
- You can also try recovering your database. This is typically the only option for when this issue occurs after an update. Try the sqlite3
.recover
command
- Another possible cause of you getting an error with your Database is that you're placing your database on a network drive (nfs or smb or something else not local). SQLite is designed for situations where the data and application coexist on the same machine. Thus your *Arr AppData Folder (/config mount for docker) MUST be on local storage. SQLite and network drives not play nice together and will cause a malformed database eventually.
- If you are using mergerFS you need to remove
direct_io
as SQLite uses mmap which isn’t supported by direct_io
as explained in the mergerFS docs here
¶ I use Sonarr on a Mac and it suddenly stopped working. What happened?
- Most likely this is due to a MacOS bug which caused one of the Sonarr databases to be corrupted.
- Follow these steps to resolve
- Then attempt to launch Sonarr and see if it works. If it does not work, you will need further support. Post in our reddit or hop on discord for help.
- For all OSes ensure the user/group you're running *Arr as has read and write access to the mounted drive.
- For Linux ensure:
- If you're using an NFS mount ensure
nolock
is enabled for your mount.
- If you're using an SMB mount ensure
nobrl
is enabled for your mount.
- For Windows: In short: the user *Arr is running as (if service) or under (if tray app) cannot access the file path on the remote server. This can be for various reasons, but the most common is *Arr is running as a service, which causes the issues described below.
- Run Sonarr's service as another user that has access to that share
- Open the Administrative Tools > Services window on your Windows server.
- Stop the Sonarr service.
- Open the Properties > Log On dialog.
- Change the service user account to the target user account.
- Change your paths to UNC paths (
\\server\share
)
- Run Sonarr.exe via the Startup Folder
-
Using mapped network drives generally doesn't work very well, especially when Sonarr is configured to run as a service. The better way to set shares up is using UNC paths. So instead of X:\TV
use \\Server\TV
.
-
A key point to remember is that Sonarr gets path information from the downloader, so you will also need to setup NZBGet, SABNzbd or any other downloader to use UNC paths too.
Run
chmod +x /Applications/Sonarr.app/Contents/MacOS/Sonarr
- You were likely passing arguments in your connection...that is not supported.
- To correct this:
- Change your argument to be your path
- Make sure the shebang in your script maps to your pwsh path (if you do not have a shebang definition in there, add it)
- Make sure the pwsh script is executable
First, make sure you read and understand the section above called "How does Sonarr find episodes? Second, make sure at least one of your indexers has the episode you were expecting to be grabbed.
- Click the 'Manual Search' icon next to the episode listing in Sonarr. Are there any results? If no, then either Sonarr is having trouble communicating with your indexers, or your indexers do not have the episode, or the episode is improperly named/categorized on the indexer.
- If there are results from step 1, check next to them for red exclamation point icon. Hover over the icon to see why that release is not a candidate for automatic downloads. If every result has the icon, then no automatic download will occur.
- If there is at least one valid manual search result from step 2, then an automatic download should have happened. If it didn't, the most likely reason is a temporary communication problem preventing an RSS Sync from your indexer. It is recommended to have several indexers set up for best results.
- If there is no manual result from a show, but you can find it when you browse your indexer's website - This can be caused by a number of reasons, for example the release is not properly tagged on your indexer causing it to not be returned to sonarr in an automatic search. This troubleshooting entry provides some tips on how to determine the cause. Having several indexers active can help solve this by providing more sources to the same content.
- On TVDb, when episode names are unknown they'll be titled TBA and there is a cache on the TVDb API. The Episode Title Required setting in Sonarr controls import behavior when the title is TBA, but after 48 hours from series airing the release will be imported even if the title is still TBA. There is also no automatic follow up renaming of TBA titled files. Note that the TBA timer is calculated from the episode airdate and time, not from when you've grabbed it or the upload time.
- Details on TVDb and Skyhook's cache can be found in the FAQ TVDb is updated why isn't Sonarr?
-
The Jackett /all
endpoint is convenient, but that is its only benefit. Everything else is potential problems, so adding each tracker individually is required. Alternatively, you may wish to check out the Jackett & NZBHydra2 alternative Prowlarr
-
February 5 2022 Update: *Arr Support has been discontinued for the jackett \all
endpoint. Jackett /all endpoint is no longer supported (e.g. warnings will occur) as of v3.0.6.1457 due to the fact it only causes issues.
-
The Jackett /all endpoint is convenient, but that is its only benefit. Everything else is potential problems, so adding each tracker individually is now required.
-
Even Jackett's Devs says it should be avoided and should not be used.
-
Using the /all endpoint has no advantages, only disadvantages:
- you lose control over indexer specific settings (categories, search modes, etc.)
- mixing search modes (IMDB, query, etc.) might cause low-quality results
- indexer specific categories (>= 100000) cannot be used.
- slow indexers will slow down the overall result
- total results are limited to 1000
- if one of the trackers in /all returns an error, *Arr will disable it and now you do not get any results.
- Add each tracker in Jackett manually as an indexer in *Arr
- Check out Prowlarr which can sync indexers to *Arr and from the Lidarr/Radarr/Readarr development team.
- Check out NZBHydra2 which can sync indexers to *Arr. But do not use their single aggregate endpoint and use
multi
if sync will be used.
- Most torrent clients doesn't come with the automatic handling of compressed archives like their usenet counterparts. We recommend unpackerr.
- Sonarr will need to move files away from where the downloader puts them into the final location, so this means that Sonarr will need to read/write to both the source and the destination directory and files.
- On Linux, where best practices have services running as their own user, this will probably mean using a shared group and setting folder permissions to
775
and files to 664
both in your downloader and Sonarr. In umask notation, that would be 002
.