mirror/Lidarr
1
0
Fork 0
mirror of https://github.com/lidarr/Lidarr synced 2025-01-02 21:15:05 +00:00
Code Issues Releases Wiki Activity

Updated Health Checks (markdown)

ta264 2020-05-19 17:44:50 +01:00
parent 8dad91660a
commit bfc9591c8d
1 changed files with 23 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
Health-Checks.md

@ -8,6 +8,13 @@ These health checks are periodically performed performed by Lidarr and on certai
Lidarr 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.
#### Update to .NET Core version ####
Newer versions of Lidarr 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.
This should only happen on linux hosts. To remedy, download the correct build for your architecture: [x64](https://services.lidarr.audio/v1/update/nightly/updatefile?os=linux&runtime=netcore&arch=x64) or [arm64](https://services.lidarr.audio/v1/update/aphrodite/updatefile?os=linux&runtime=netcore&arch=arm64) or [arm](https://services.lidarr.audio/v1/update/aphrodite/updatefile?os=linux&runtime=netcore&arch=arm).
Delete your existing binaries and replace with the contents of the `.tar.gz` you just downloaded. Update your startup script to call `Lidarr` instead of `mono --debug Lidarr.exe`
#### fpcalc missing
Lidarr can use chromaprint audio fingerprinting to identify tracks. This depends on an external binary, which is distributed with Lidarr for Windows and macOS but must be provided independently on Linux.
@ -48,6 +55,22 @@ This means Lidarr 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 Lidarr and copy the current contents of the ```~/.config/Lidarr``` directory to preserve your database.
#### 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 versions > 0.7.1.1381 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for Lidarr:
```
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
### Download Clients ###
#### No download client is available ####