#Unraid sonarr install#
#Unraid sonarr full#
#Unraid sonarr password#

If you used jackett then its very straightforward and a simple google search for 'how to set up jackett in unraid' should do the trick.

#Unraid sonarr install#

Next you install Radarr/Sonnarr and add indexers however you chose. Its 8118 or something, not home cant remember off the top of my head. The port is the one in the delugevpn container that says for routing traffic. The http adress is the one in the top right corner of your unraid dashboard. In the settings there is a section for using a privoxy. Simply install jacket and load the web UI up when its done. Make sure you turn on the privoxy setting.įrom here you have the option to use Jackett as your source indexer. Follow spaceinvaders guide on setting it up. So ill share with you what i did and hopefully this helps.

You could do it with forms auth too, but you'd have to load in the machine key and re-create the ticket and claims payload of the cookie which is a bit of a pain, and as this is only meant to be a barrier in the unlikely case sonarr accidentally gets exposed directly to the internet, bypassing the proxy's own authentication.I looked for a good straight forward answer when i was doing this and there are so many ways to tackle the task.

#Unraid sonarr password#

if they pass that, sonarr sees them as already providing the username and password so don't get asked for it, so there's no double authentication needed. If the user hits sonarr through the proxy, they get authenticated against Vouch, and ultimately via oauth to my chosen authentication provider where I use a strong random password and my yubi key as a second authentication factor. So, if a user somehow, say I accidentally turn off my firewall and change the bind settings to bind sonarr to a public interface at the same time, hits sonarr directly, they get hit with the basic auth check and have to enter the (huge, randomly generated) username and password I set in the sonarr settings. (screenshotted radarr by mistake but it's the same for sonarr) - $auth is just the base64 encoded username:password combo I entered into sonarr's settings.īut only after the user has passed the proxy's own authentication using auth_request (in my case against vouch proxy) Then the proxy injects the basic auth header directly into the request: I have basic auth enabled in Radarr / Sonarr et al.

linuxserver: lscr.io/linuxserver/sonarr:develop.

#Unraid sonarr full#

In order to secure Sonarr from unauthorized users and to protect your private credentials Sonarr will now require authentication to be enabled when accessing the UI for the first time after installing or upgrading to v4Ī full list of changes is available on GitHub Download Links Windows (7 SP1 or newer) Language profiles have been replaced with Language support in Custom Formats, giving you more control on upgrading.Support for original language when available.Linux x86 and BSD are no longer supported.MediaInfo has been replaced with ffprobe.Custom Formats, replacing Preferred Words in Release Profiles.Thanks to everyone that contributed, especially Qstick and ta264 for helping port over a number of changes from Radarr. Some of the changes are considered breaking changes and as DB migrations are not backwards compatible. There are a number of major changes and even more minor changes. After months of development and over 100 commits Sonarr v4 is ready for beta testers.