Sandbox

Radarr

• Update to .NET Core version
  • Newer versions of Radarr are targeted for .NET Core. We provide legacy mono builds for those platforms that cannot use .NET Core. You are running one of these legacy builds but your platform supports .NET Core.
  • Fixing Docker installs
    • Re-pull your container
  • Fixing Standalone installs
    • This should only happen on linux hosts. To remedy, download the correct build for your architecture:
      • x64
      • arm64
      • arm
    • Back-Up your existing configuration before the next step.
    • Delete your existing binaries and replace with the contents of the .tar.gz you just downloaded.
    • DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.
      YOU MUST DELETE THE OLD ONES FIRST.
      • Update your startup script to call Radarr instead of mono --debug Radarr.exe
    • If Radarr doesn’t start make sure you have the dependencies listed here installed.
• Mono version is less than 3.10, upgrade for improved stability
  • Radarr is written in .Net and requires Mono to run. Versions of 3.10 and above resolved various stability issues we experienced in the past and is considered the minimum supported version.
    
  • Mono version 4.x and higher are also available and provides a better experience on certain platforms.
  • See "Update to .NET Core version above"
• 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.
  • (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 Radarr will be unable to update itself. You’ll have to update Radarr manually or set the permissions on Radarr’s Startup directory (the installation directory) to allow Radarr to update itself.
• Updating will not be possible to prevent deleting AppData on Update
  • Radarr detected that AppData folder for your Operating System is located inside the directory that contains the Radarr binaries. Normally it would be C:\ProgramData for Windows and, ~/.config for linux.
  • Please look at System -> Info to see the current AppData & Startup directories.
  • This means Radarr will be unable to update itself without risking data-loss.
  • If you’re on linux, you’ll probably have to change the home directory for the user that is running Radarr and copy the current contents of the ~/.config/Radarr directory to preserve your database.
• Branch is for a previous version
  • The update branch setup in Settings/General is for a previous version of Radarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.
  • Note: Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within radarr’s settings), once we push a build to Github it will show up on “develop” release channel.
• Could not connect to signalR
  • signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.
  • The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for radarr:

  proxy_http_version 1.1;

  proxy_set_header Upgrade $http_upgrade;

  proxy_set_header Connection $http_connection;

  • Make sure you do not include proxy_set_header Connection "Upgrade"; 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.load

  ProxyPass "/socket" "ws://127.0.0.1:7878/socket"

  ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"