Can't Acess Lidarr WebUI

[gabe.dunn]

I have been setting up my TrueNAS core instance over the past week, and I have just gotten around to installing *arr apps. Sonarr was installed fine, Radarr wasn't as smooth (process was running, webui wasn't available), but once I edited the jail to enable `allow_mlock`, I was able to access the webui again.

I have now moved onto Lidarr, and for some reason I have come up across the same issue as with Radarr. When running `service lidarr status` it tells me that it is running, and I can see that it is running with htop.

I tried the same solution as with the Radarr plugin, enabling `allow_mlock`, but after restarting the jail I am still unable to access the webui. I'm not sure what to try next in order to get this working. Any suggestions would be great.

 

[FrankNAS]

version of lidarr?
version of TrueNAS?
output of "ps auxw | grep lidarr" ? in lidarr jail

 

[gabe.dunn]

version of lidarr?
version of TrueNAS?
output of "ps auxw | grep lidarr" ? in lidarr jail

All versions should be the latest, here they are:
lidarr: 0.8.1.2135
TrueNAS: TrueNAS-12.0-U7
Output:

Code:

lidarr 80837  0.0  0.9 232896 154264  -  SsJ  15:38   0:21.26 /usr/local/bin/mono --debug /usr/local/share/lidarr/bin/Lidarr.exe --nobrowser --d
root   97230  0.0  0.0  10984   2356  -  IJ   03:01   0:00.00 mail -E -s lidarr daily run output root
root   97432  0.0  0.0  10984   2352  -  IJ   03:01   0:00.00 mail -E -s lidarr daily security run output root
root   99243  0.0  0.0  11508   2840  0  S+J  03:10   0:00.00 grep lidarr

 

[FrankNAS]

it looks like `lidarr` still uses mono. so `allow_mlock` won't fix it.
it also looks like the daemon is not running correctly. There should be two `lidarr` processes one from daemon and the other from mono.

inside the lidarr jail:
`service lidarr stop`
if it says that lidarr is not running you will have to kill the mono process that is left over.
`/usr/local/bin/mono --debug /usr/local/share/lidarr/bin/Lidarr.exe --nobrowser --data=DATADIR`
where `DATADIR` is where you store your `lidarr` data

 

[gabe.dunn]

it looks like `lidarr` still uses mono. so `allow_mlock` won't fix it.
it also looks like the daemon is not running correctly. There should be two `lidarr` processes one from daemon and the other from mono.

inside the lidarr jail:
`service lidarr stop`
if it says that lidarr is not running you will have to kill the mono process that is left over.
`/usr/local/bin/mono --debug /usr/local/share/lidarr/bin/Lidarr.exe --nobrowser --data=DATADIR`
where `DATADIR` is where you store your `lidarr` data

I tried this, and it seemed to work fine from the output, but I wasn't able to access it. I tried running `curl localhost:8686` from within the jail and that looked like it was getting something, but still no luck from outside.

I then looked at the differences between the radarr/sonarr jails and the lidarr one, and it turns out that whoever maintains the plugin for lidarr hasn't included the proper configuration to do NAT port forwarding. I added an entry, with tcp, and port 8686 -> 8686, and restarted the jail. That was the only thing missing.

 

[FrankNAS]

well, community plugins are maintained by the community. You can submit a pull request to fix the issue :)

glad you got it figured out though!

 

[gabe.dunn]

well, community plugins are maintained by the community. You can submit a pull request to fix the issue :)

glad you got it figured out though!

Looks like I forgot to ask for the link to the repo in my previous post. I'd be happy to submit a PR, once I know where the repo is :)

 

[jmcguire525]

I tried this, and it seemed to work fine from the output, but I wasn't able to access it. I tried running `curl localhost:8686` from within the jail and that looked like it was getting something, but still no luck from outside.

I then looked at the differences between the radarr/sonarr jails and the lidarr one, and it turns out that whoever maintains the plugin for lidarr hasn't included the proper configuration to do NAT port forwarding. I added an entry, with tcp, and port 8686 -> 8686, and restarted the jail. That was the only thing missing.

Can you tell me how to add this? I seem to have the same issue but I'm not sure how to edit this.

 

[Pancackewaffle]

I tried this, and it seemed to work fine from the output, but I wasn't able to access it. I tried running `curl localhost:8686` from within the jail and that looked like it was getting something, but still no luck from outside.

I then looked at the differences between the radarr/sonarr jails and the lidarr one, and it turns out that whoever maintains the plugin for lidarr hasn't included the proper configuration to do NAT port forwarding. I added an entry, with tcp, and port 8686 -> 8686, and restarted the jail. That was the only thing missing.

I also am unsure how to add the tcp entry. Can you list the command for this?

 

[FindingFilene]

Hi everybody, I am also having a similar problem. In TrueNAS Core 13, I installed a Lidarr plugin, and I have no ability to access the web UI. Here's the following answers:

Code:

root@music:/usr/local/lidarr # ps -auxw | grep lidarr
lidarr 26109  0.0  0.0 12848 2196  -  SsJ  10:42   0:00.17 daemon: /usr/local/share/lidarr/bin/Lidarr[28407] (daemon)

and the grep for the Lidarr look in my logs--that's all.

Next, I can't use Curl to access the localhost at the port for the service, either.

Code:

root@music:/usr/local/lidarr # curl localhost:8686
curl: (7) Failed to connect to localhost port 8686 after 0 ms: Connection refused

Finally, I have no 'mono' in the list up above. In fact, it seems like Mono isn't even installed on this Lidarr version??

 

[FrankNAS]

Hi everybody, I am also having a similar problem. In TrueNAS Core 13, I installed a Lidarr plugin, and I have no ability to access the web UI. Here's the following answers:

Code:

root@music:/usr/local/lidarr # ps -auxw | grep lidarr
lidarr 26109  0.0  0.0 12848 2196  -  SsJ  10:42   0:00.17 daemon: /usr/local/share/lidarr/bin/Lidarr[28407] (daemon)

and the grep for the Lidarr look in my logs--that's all.

Next, I can't use Curl to access the localhost at the port for the service, either.

Code:

root@music:/usr/local/lidarr # curl localhost:8686
curl: (7) Failed to connect to localhost port 8686 after 0 ms: Connection refused

Finally, I have no 'mono' in the list up above. In fact, it seems like Mono isn't even installed on this Lidarr version??

Make sure you have allow.mlock=1 for that jail. Only Sonarr uses mono. All other *arr projects use dotNET

 

[carefulshout]

Can you tell me how to add this? I seem to have the same issue but I'm not sure how to edit this.

I also am unsure how to add the tcp entry. Can you list the command for this?

Hi everybody, I am also having a similar problem. In TrueNAS Core 13, I installed a Lidarr plugin, and I have no ability to access the web UI. Here's the following answers:

Code:

root@music:/usr/local/lidarr # ps -auxw | grep lidarr
lidarr 26109  0.0  0.0 12848 2196  -  SsJ  10:42   0:00.17 daemon: /usr/local/share/lidarr/bin/Lidarr[28407] (daemon)

and the grep for the Lidarr look in my logs--that's all.

Next, I can't use Curl to access the localhost at the port for the service, either.

Code:

root@music:/usr/local/lidarr # curl localhost:8686
curl: (7) Failed to connect to localhost port 8686 after 0 ms: Connection refused

Finally, I have no 'mono' in the list up above. In fact, it seems like Mono isn't even installed on this Lidarr version??

To all of you who are looking -

1. In the TrueNAS Jails GUI, you can stop the lidarr jail and enter the "Edit" menu.
2. From there select the "Network Properties" section. In there, you will find a checkbox at the bottom for "NAT Port Forwarding" - check this box and a prompt will show up to add a new rule.
3. Set your protocol as TCP, and both Jail and Host ports as 8686, or whatever you have configured for your installation (8686 is default, I believe.) You can set your host port as something else if you wish to use a different port for management.

Doing this and setting allow_mlock worked for me. Doesn't sound like allow_mlock is needed, but I just haven't bothered to toggle it off.

Hope this helps.

 

[physhstyx]

To all of you who are looking -

1. In the TrueNAS Jails GUI, you can stop the lidarr jail and enter the "Edit" menu.
2. From there select the "Network Properties" section. In there, you will find a checkbox at the bottom for "NAT Port Forwarding" - check this box and a prompt will show up to add a new rule.
3. Set your protocol as TCP, and both Jail and Host ports as 8686, or whatever you have configured for your installation (8686 is default, I believe.) You can set your host port as something else if you wish to use a different port for management.

Doing this and setting allow_mlock worked for me. Doesn't sound like allow_mlock is needed, but I just haven't bothered to toggle it off.

Hope this helps.

I have done everything as listed here and can confirm that the plugin is loading. The output of "ps auxw | grep lidarr" might help:

Code:

lidarr 25938 0.0 0.0 10852 2324 - IsJ 23:53 0:00.00 daemon:
/usr/local/share/lidarr/bin/Lidarr[28934] (daemon)
lidarr 28934 0.0 0.6 2781992 106272 - SJ 01:54 0:04.82
/usr/local/share/lidarr/bin/Lidarr --data=/usr/local/lidarr --nobrow
root 29550 0.0 0.0 11292 2796 4 R+J 02:23 0:00.00 grep lidarr

All of the TCP and port settings are in the jail and allow_mlock is confirmed, but I still cannot get the WebUI to load. Sonarr, Radarr, Prowlarr all load without any problem and are setup in similar manner. I cannot figure out why Lidarr alone will not load. I have tried fresh installs both through the plugin and manual jail creation and install. Same result each time. Any help would be appreciated!

 

[FrankNAS]

Does sockstat report what port and binding Lidarr is using? Are they what you expect them to be?

 

[physhstyx]

It does not, it shows Lidarr (not connected).

Code:

lidarr   Lidarr     37829 9  stream (not connected)
lidarr   Lidarr     37829 349 dgram -> /var/run/log

 

[FrankNAS]

It certainly looks like it has not started correctly, you can either try and fish the logs out and see what is going on or try and reinstall the plugin.

If you manually set the jail up double check that mlock is correctly enabled inside the jail:

Code:

sysctl -n security.bsd.unprivileged_mlock

it should return "1"

If it does then try reinstalling the package:

Code:

pkg install --force lidarr

After that, restart the service:

Code:

service lidarr restart

 

[physhstyx]

Thank you for the reply. It did return "1". I tried reinstalling the package, but still had the same issue. In the end I once again deleted the jail and manually created a new jail with an altered jail name. For some reason this jail worked without issue. Anytime I had tried deleting and re-creating using the old jail name it failed...so it seems something had been left behind that was messing up anything reusing the old jail name.