GibsonXXI

Jandrop, can you please clarify what the 'Core File API Plugin' mentioned in the Android app refers to, please? I can find no such named plugin in the community apps part of the main unRAID UI, so I'm a bit confused whether you're actually referring to unRAID's own API system or something external. Also, some setup instructions / guide on app setup procedure would undoubtedly be a welcome addition. Looking good so far though, many thanks for this. Dan / Gib.

It turns out the 'appdata' folder created with the first version of Listenarr I installed (i.e: before Xmas) was the root cause for the error posted in the log. I forgot to remove the appdata folder last night when removing & reinstalling it. I went through and completely removed the app and all related templates and appdata folders, and reinstalled it again (30 mins ago at the time of writing). It's now working fine, have to set it up, enable authentication via the config.json, as it appears that this is disabled by default. Your post last night that you had it working on your system, JPDVM2014, clued me in to where I may have been going wrong, so thank you for that. Now to set it up. Should also do Kapowarr too, but I'm waiting for the developer to add Usenet support before I invest any great amount of time in that one. Enjoy your coffee. 😉 Dan / Gib.

I'm still getting the same issue, but I am trying to embed it within Binhex's DelugeVPN container for networking. I'll have to remove the port allocation from that add-on and try starting it in bridge mode, separately, and see what happens then. I've run out of time tonight though, so I'll look at it when I get home from work tomorrow. The error I posted in my first post is also still occurring, and I think the problematic '.npm' folder it complains about has something to do with the Web UI. Actually had this installed since before Xmas, but disabled because I didn't have time to set it up, so put it on the back-burner. Dan / Gib.

Of course not, it's not a core code change, forgot this fact. Thanks for the clarification. Dan / Gib.

I've got CA Auto-update plugin set to daily (1am). Not been sent any prompt to update Listenarr. When is the CA repo likely to see and reflect your changes? I was hoping to get this set up before the end of the weekend, ideally (Sorry if this sounds pushy). Dan / Gib.

Thanks JPDVM2014. You might also want to add a default folder mapping for the 'Download' folder as well. I can't speak for others who use the 'arr' apps, but I have a dedicated share for Downloaded files which is separate to the share on which the media library resides. Adding such a mapping manually isn't difficult, but might save some time for the less container-savvy users who might want to use the Listenarr docker image you provided. 🙂 Dan / Gib.

There's something wrong with the 'Listenarr' docker image. Installed with defaults (set path to existing Audiobooks library) but the WebUI never starts / is inaccessible. Checked the logs for the container and this pops up in the log: npm error syscall mkdir npm error path /.npm npm error errno EACCES npm error npm error Your cache folder contains root-owned files, due to a bug in npm error previous versions of npm which has since been addressed. npm error npm error To permanently fix this problem, please run: npm error sudo chown -R 99:100 "/.npm" npm error Log files were not written due to an error writing to the directory: /.npm/_logs npm error You can rerun the command with --loglevel=verbose to see the logs in your terminal The Daemon appears to be running when monitoring the logs, but no WebUI on port 5000. Dan / Gib. EDIT: Apparently, the Listenarr app now uses port 4545 and NOT port 5000 (version update / change) so the docker image template will need to be updated to reflect this.

You can't update Docker apps internally like that. You'll have to be patient, and wait for Binhex to push out an updated container release. Dan / Gib.

Sorry, I don't (and won't) install / use Chrome. It only seems to be an issue on a vanilla (unconfigured) install. After setting it up, the issue no longer arises (for me).

The WebUI link from unRAID doesn't work for me on Firefox either. It will open a new tab, using just the server IP address and port, but no redirection ever takes place. You get the XML script / page output on screen (as others have mentioned). Manually adding the '/web/index.html' string onto the end of the url in the address bar fixes the problem, and the setup web-page appears as expected. It's definitely something amiss with this version of Plex, as the Linuxserver.io version does not suffer from this issue for me, on exactly the same setup.