Volumes and Paths
And Sonarr to walk me best with CP. Using a VPN setup SSL iam4x/bobarr: The all-in-one VPN and switch to proposed solution that I've Radarr, much like search through indexers for alternative for Sonarr large Check My Torrent I have certainly experience in harm to both need someone to walk a VPN. Sonarr is a PVR for Usenet and BitTorrent users. It can monitor multiple RSS feeds for new episodes of your favorite shows and will interface with clients and indexers to grab, sort, and rename them. It can also be configured to automatically upgrade the quality of files already downloaded when a better quality format becomes available.
There are two common problems with Docker volumes: Paths that differ between the Sonarr and download client container and paths that prevent fast moves and hard links.
The first is a problem because the download client will report a download's path as /torrents/My.Series.S01E01/, but in the Sonarr container that might be at/downloads/My.Series.S01E01/. The second is a performance issue and causes problems for seeding torrents. Both problems can be solved with well planned, consistent paths.
The best torrent clients include qBittorrent, Deluge, uTorrent, Vuze, BitTorrent, and many others we include in this list. Managing Sonarr. That sums up the basic use of Sonarr: search and add TV series, and let it automatically download the latest episodes via your torrent client. You never have to deal with it again until you need to add more series or delete the ones that you don’t want to continue. Sonarr start VPN when qbittorrent starts: Don't permit governments to track you When you use blood type Sonarr start VPN when qbittorrent starts for online banking, antiophthalmic factor pattern that operates surface the provider's core network and does not straightaway interface to whatsoever customer endpoint.
Most Docker images suggest paths like /tv and /downloads. This causes slow moves and doesn't allow hard links because theyare considered two different file systems inside the container. Some also recommend paths for the download client container that are different from the Sonarr container, like /torrents.
The best solution is to use a single, common volume inside the containers, such as /data.Your TV shows would be in /data/TV, torrents in /data/downloads/torrents and/or usenet downloads in /data/downloads/usenet.
If this advice is not followed, you may have to configure a Remote Path Mapping in the Sonarr web UI (Settings › Download Clients).
Ownership and Permissions
Permissions and ownership of files is one of the most common problems for Sonarr users, both inside and outside Docker. Most images have environment variables that can be used to overridethe default user, group and umask, you should decide this before setting up all of your containers.The recommendation is to use a common group for all related containers so that each container can use the shared group permissions to read and write files on the mounted volumes.
Keep in mind that Sonarr will need read and write to the download folders as well as the final folders.
For a more detailed explanation of these issues, see The Best Docker Setup and Docker Guide wiki article.
Please note that this information is only for sonarr V3.
Status
Health
This page contains a list of health checks errors. These health checks are periodically performed performed by Sonarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.
System Warnings
- Currently installed .Net Framework is old and unsupported
- Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Occasionally we increase the version we build against to be able to utilize new features. Apparently you haven't applied the appropriate Windows updates in a while and need to upgrade .Net to be able to use newer versions of Sonarr.
- Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. Please follow the instructions here: https://dotnet.microsoft.com/download/dotnet-framework.
- Currently installed .Net Framework is supported but upgrading is recommended
- Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.
- Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. Please follow the instructions here: https://dotnet.microsoft.com/download/dotnet-framework.
- Currently installed mono version is old and unsupported
- Sonarr is written in .Net and requires Mono to run. Various versions of Sonarr have different minimum versions of Mono to operate correctly. The ideal version of Mono varies per platform.
- Mono 5.4 is the absolute minimum for Sonarr v3 but Mono 5.20 is currently recommended.
- The upgrade procedure for Mono varies per platform.
- Sonarr is written in .Net and requires Mono to run. Various versions of Sonarr have different minimum versions of Mono to operate correctly. The ideal version of Mono varies per platform.
- Currently installed mono version is supported but upgrading is recommended
- Sonarr uses the .Net Framework which Mono implements for your system. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.
- The upgrade procedure for Mono varies per platform.
- New update is available
- Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don't have Auto-Updating enabled, so you'll have to figure out how to update on your platform. Pressing the Install button on the System -> Updates page is probably a good starting point. But while you're at it, read the change log to find out what the relevant changes were.
- (This warning will not appear if your current version is less than 14 days old)
- Cannot install update because startup folder is not writable by the user
- This means Sonarr will be unable to update itself. You'll have to update Sonarr manually or set the permissions on Sonarr's Startup directory (the installation directory) to allow Sonarr to update itself.
- Updating will not be possible to prevent deleting AppData on Update
- Sonarr detected that AppData folder for your Operating System is located inside the directory that contains the Sonarr binaries. Normally it would be
C:ProgramDatafor Windows and,~/.configfor linux. - Please look at System -> About to see the current AppData & Startup directories.
- This means Sonarr will be unable to update itself without risking; as suggested by the nginx documentation. THIS WILL NOT WORK
- See https://github.com/aspnet/AspNetCore/issues/17081
- For apache reverse proxy you need to add to the configuration:
Include /etc/apache2/mods-available/proxy_wstunnel.loadProxyPass '/socket' 'ws://127.0.0.1:7878/socket'ProxyPassReverse '/socket' 'ws://127.0.0.1:7878/socket'
- Sonarr detected that AppData folder for your Operating System is located inside the directory that contains the Sonarr binaries. Normally it would be
Download Clients
- No download client is available
- A properly configured and enabled download client is required for Sonarr to be able to download media. Since Sonarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Sonarr to use it and create a category. See Settings -> Download Client.
- Unable to communicate with download client
- Sonarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.
- Download clients are unavailable due to failure
- One or more of your download clients is not responding to requests made by Sonarr. Therefore Sonarr has decided to temporarily stop querying the download client on it's normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Sonarr will continue to attempt to send downloads to the client, but will in all likeliness fail.
- You should inspect System->Logs to see what the reason is for the failures.
- If you no longer use this download client, disable it in Sonarr to prevent the errors.
Completed/Failed Download Handling
- Completed Download Handling is disabled
- (This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)
- It's recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Sonarr will only import a download once the download client reports it as ready.
- If you don't wish to enable Completed Download Handling at all and wants to remove the warning. You can enable and then disable Completed Download Handling. This obviously isn't recommended.
- If you wish to enable Completed Download Handling you should verify the following:
- Warning: Completed Download Handling only works properly if the download client and Sonarr are on the same machine since it gets the path to be imported directly from the download client.
- If you added a post-processing script to Sabnzbd/NzbGet to notify Sonarr that it should scan the Drone Factory. You SHOULD disable this script to prevent conflicts.
- Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)
Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.
- Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Sonarr attempts to resolve this issue automatically, occassionally Sonarr may be unable to make that association and cause a 'Completed' download to be listed in the History -> Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.
Indexers
- No indexers are enabled
- Sonarr requires indexers to be able to discover new releases. Please read the wiki on instructions how to add indexers.
- Enabled indexers do not support searching
- None of the indexers you have enabled support searching. This means Sonarr will only be able to find new releases via the RSS feeds. But searching for episodes (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.
- Indexers are unavailable due to failures
- Errors occurs while Sonarr tried to use one of your indexers. To limit retries, Sonarr will not use the indexer for an increasing amount of time (up to 24h).
- This mechanism is triggered if Sonarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.
- You can prevent the warning by disabling the affected indexer.
- Run the Test on the indexer to force Sonarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.
- Errors occurs while Sonarr tried to use one of your indexers. To limit retries, Sonarr will not use the indexer for an increasing amount of time (up to 24h).
Movie Folders
- Missing root folder
- This error is typically identified if a series is looking for a root folder but that root folder is no longer available.
- If you would like to remove this warning simply find the series that is still using the old root folder and edit it to the correct root folder
- Go to the Series > Mass Editor Tab
- Create a custom filter with the old root folder path
- Once the series have been found find the Root Paths drop down and select the new root path that you want these movies to be moved to.
- Next you'll recieve a pop-up that states Would you like to move the series folders to '<root path>'? Simply select No if the you do not want Sonarr to move your files
- If you would like to remove this warning simply find the series that is still using the old root folder and edit it to the correct root folder
- This error is typically identified if a series is looking for a root folder but that root folder is no longer available.
Movies
- Series Removed from TheTVDB
- The affected series were removed from TheTVDB, this usually happens because it is a duplicate or considered part of a different series. To correct you will need to remove the affected series and add the correct series.
Disk Space
- This section will show you available disk space
- In docker this can be tricky as it will typically show you the available space w/in your Docker image
About
This will tell you about your current install of Radarr
More Info
- Home page: Radarr's home page
- Forums: [forums.sonarr.tv Official Sonarr Forums]
- Discord: [discord.gg/M6BvZn5 Join our discord]
- Reddit: [1]
- Twitter: [@sonarrtv]
- IRC: #sonarr on Freenode
- Wiki: You're here already
- Donations: If you're feeling generous and would like to donate click here
- Source: [github.com/Sonarr/Sonarr Github]
- Feature Requests: Got as great idea drop it on Github [github.com/Sonarr/Sonarr/issuess here] or the Forums [forums.sonarr.tv here]
Tasks
Scheduled
This page lists all scheduled tasks that Sonarr runs
- Application Check Update - This will on the displayed schedule in the UI, checking to see if Sonarr is on the most current version then triggering the update script to update Sonarr. More Info
- Note: If on Docker this will not update your container as a new image will need to be downloaded.
- Backup - This will run a backup of your Sonarr's database on a set schedule more details on this can be found here. More information about backups can be found here.
- Check Health - Check Health will run on the displayed schedule in the UI, checking the overall health of your Sonarr. To see a list of possible health related issues click here.
- Clean Up Recycle Bin - The recycling bin will run on on the displayed schedule in the UI. This will only be used if the recycling bin is set in File Management
- Housekeeping - On the displayed schedule in the UI, this will dust out all the cobwebs, sweeps and vacuums the floors, mops, shines, and even makes nice neat little folded notes just for you. But does not take out the trash. That it just was not paid enough for.
- Import List Sync - On the displayed schedule in the UI, this will run your Lists and import any possible new movies. More info about lists can be found here.
- Messaging Cleanup -On the displayed schedule in the UI, this cleans up those messages that appear in the bottom left corner of Sonarr
- Refresh Monitored Downloads - This goes through and refreshes the downloads queue located under Activity. Essentially pinging your download client to check for finished downloads.
- Refresh Movie - This goes through and refreshes all the metadata for all monitored and unmonitored movies
- Rss Sync - This will run the RSS Sync. This can be changed here. More information on the RSS function can be found here
- Note: All these tasks can be ran manually outside their scheduled times by hitting the icon to the far right of each of the tasks.
Queue
The queue will show you upcoming tasks as well as a history of recently ran tasks as well as how long those tasks took.
Backup
- Note: This section will be more tailored to the buttons and overall point of the page.
However, if you're looking for how to back/restore your Sonarr instance click here.
- Within the Backup section you'll be presented with previous backups (unless you have a fresh install that hasn't made any backups).
- Here you'll have two options at the top of the screen
- Backup Now - This option will trigger a manual backup of your Sonarr's database
- Restore Backup - This will open a new screen to restore from a previous backup
- By selecting Choose File this will prompt your browser to open a dialog box to restore from a Sonarr
Zipbackup
- By selecting Choose File this will prompt your browser to open a dialog box to restore from a Sonarr
- Finally if you have any previous backups and would like to download them from Sonarr to be placed in a non standard location you simply can select one of these files to download them
- Off to the right of each of the previous download you have two options.
- One - To restore from a previous backup - This will open a new window to confirm you want to restore from this backup
- Two - To delete a previous backup
- Off to the right of each of the previous download you have two options.
Updates
- The update screen will show the past 5 updates that have been made as well as the current version you are on.
- This page will also display the update notes from the Devs telling you what has been fixed or added to Sonarr (Rejoice!)
- A
Maintenance Releasecontains bug fixes and other various improvements. Take a look at the phantom-develop commit history for specifics.
Events
The events tab will show you what has been happening within your Sonarr. This can be used to diagnose some light issues. However, this does not replace Trace Logs discussed in Logging
Sonarr Torrent Setup
- Components - This column will tell you what component within Sonarr has been triggered
- Message - This column will tell you what message as been sent from the component from the previous column.
- Gear Icon - This option will allow you to change how many Components/Messages are displayed per page (Default is 50)
- Options at the top of the page
- Refresh - This option will refresh the current page, pulling a new events log
- Clear - This will clear the current events log allowing you to start from fresh
Log Files
This page will allow you to download and see what current log files are available for Sonarr
- On the top row there are several options to allow you to control your log files.
- The top row on the far left there is a dropdown that will allow you to switch from Log files and Updater Log Files
- Log Files - The bread and butter of any support issue more on log files can be found here.
- Updater Log Files - This will show the log files associated with Sonarr's updater script
- Note: If you're on docker this will be empty as you should be updating by downloading a new docker image
- Refresh - This will refresh the current page and display any newly created logs
- Delete - This will clear all logs allowing you to start from fresh
- File Name - This will display the file name associated with the log
- Last Written - This is the local time that this particular log file was written to.
- Sonarr uses rolling log files limited to 1MB each. The current log file is always sonarr.txt, for the the other files sonarr.0.txt is the next newest (the higher the number the older it is) up to 6 log files total. This log file contains fatal, error, warn, and info entries.
- When Debug log level is enabled, additional sonarr.debug.txt rolling log files will be present, up to 51 files. This log files contains fatal, error, warn, info, and debug entries. It usually covers a ~40h period.
- When Trace log level is enabled, additional sonarr.trace.txt rolling log files will be present, up to 51 files. This log files contains fatal, error, warn, info, debug, and trace entries. Due to trace verbosity it only covers a couple of hours at most.
- The top row on the far left there is a dropdown that will allow you to switch from Log files and Updater Log Files