[ Lidarr ] [ 0.5.0.583 ] Looks and smells like Sonarr but made for music

[QNAP_Stephane]

it is running if you are in FW 4.3.x

[QNAP_Stephane]

updated

[Coolsaber57]

Hmm, I can't seem to get Lidarr to do any import - the search just fails for everything. I can't import or Add New. Anyone have these issues?

I installed this version from the QNAP Club repository.

[QNAP_Stephane]

updated

[crutchley]

Issue after doing both a dirty and clean installation:

Screenshot 2018-09-19 10.38.37.png

(Should add: thank you so much for all you do Stephane-- setting my whole stack back up on a NAS has been silk-smooth.)

[QNAP_Stephane]

thanks for your words

but i cannot reproduced on a clean install on x86_64 (TS-253PRO FW 4.3.4 0830)
all is starting fine on my side

[crutchley]

Thanks. It was something cached somewhere, was loading a mix of old and new versions. Now I wonder if it was browser-side, because changing the port fixed it.

Thanks again!

[omneo]

Hi, I have been have the following message when attempting to search, ever since installing Lidarr a few months back "failed to load search results, please try again".

I have successfully linked nzb and indexers...

any help will be appreciated! (ps, i have search the forum and external sites with no luck!)
thanks

Health
No issues with your configuration
Disk Space
Location Free Space Total Space
/mnt/HDA_ROOT 368.1 MB 493.5 MB
25.4%
/share/CACHEDEV2_DATA 842.4 GB 3.5 TB
76.7%
/mnt/ext 56.2 MB 417 MB
86.5%
/share/CACHEDEV1_DATA 3.1 TB 3.5 TB
13.6%
About

Version
0.4.0.524
Mono Version
4.6.2
DB Migration
20
AppData directory
/share/CACHEDEV1_DATA/.qpkg/Lidarr/lidarr/.config/Lidarr
Startup directory
/share/CACHEDEV1_DATA/.qpkg/Lidarr/lidarr
Mode
Consolw

[jeaust]

I have installed Lidarr and am now trying to update it. It sees the nightly updates (after it initially failed to find any, this was fixed by installing QPerl viewtopic.php?t=109760 and CACert viewtopic.php?t=117049)

Now, it's saying the config directory is in the wrong location:

Update process failed: Your Lidarr configuration '/share/CACHEDEV1_DATA/.qpkg/Lidarr/lidarr/.config/Lidarr' is being stored in application folder '/share/CACHEDEV1_DATA/.qpkg/Lidarr/lidarr' which will cause data lost during the upgrade. Please remove any symlinks or redirects before trying again.

I have checked Sonarr on this system and its AppData directory is located at /share/CACHEDEV1_DATA/SONARR_CONFIG

Can the QPKG be recreated with a similar location, so that the updater doesn't fail? Is there a way I can fix this myself?

[QNAP_Stephane]

I can move it to upper directory, by modifing HOME flag

may be try 0.4.0.255 i publish on repo... cant see new update at this time on Github

[jeaust]

Hi Stephane,

thank you for your quick reaction. I have downloaded and installed the 0.4.0.525 QPKG (maybe update this topic title?), but it still says 0.4.0.524 in Lidarr.

I uninstalled Lidarr, manually removed the folder via SSH to be sure and even rebooted the NAS. Installed the 'new' .525 version, noticed internal version is still .524. Changed updates to Nightly and was able to update!

Awesome, thanks for the help! Now on 0.4.0.566, Nov 11 2018.


EDIT: folder location has not changed.

[QNAP_Stephane]

normal .525 is just internal qpkg version not the Lidarr real version
566 is not available in download on github that why i didnt update core

location change to /opt/Lidarr instead of /opt/Lidarr /lidarr

[Skeptical.me]

@QNAP_Stephane I have Lidarr 0.5.0.583 installed, but when I click to open Lidarr in the QTS App Store it just opens another tab of the QTS GUI and not Lidarr GUI. Has anyone else experienced this?

[QNAP_Stephane]

it runs on port 8686 ... may be you use this port on your NAS for QTS then it conflicts

[Skeptical.me]

it runs on port 8686 ... may be you use this port on your NAS for QTS then it conflicts

Thanks for the reply, Stephane.

NAS = https://192.168.1.230:6879/cgi-bin/

I've uninstalled and re-installed. Its still doing the same thing, strange.

Edit: the system port was 8686 and the ssl secure port is 6879 ... problem solved. Thanks!