lutiana

So I have a ton of audio books, in a folder structure like this: Last, First - Book 1 - mp3 - Book 2 etc The mp3s do not all have the correct ID3 tags, they are kid of all over the place, but fixing all of that is a project that would take some time as I have quite a few books. Can LazyLibrarian help me organize all of this? I am not talking about fixing the ID3 tags (though it would be cool if it could) rather just looking for a front end that can better help me navigate it all and get all the meta data on the books. Basically I am wondering if it can work like plex, point it at a folder, tell it what's in there and let it go and download all the meta data and add the (multiple) MP3s to the record.

Hello everyone, I am adding a cache drive to my array, just a single 500Gb NVME WD Red drive, no redundancy as I simply need it to speed up copies and have the mover seto to run once every 8 hours. The data that will flow through it is not critical, and if it gets lost due to failure it's not a big deal. That said, I am trying to understand why the app data is recommended to be on the cache drive? Fix common problems calls this out as a hard warning if it's set to not cache. I get that this would speed up docker performance, but in my situation that would essentially put all my app data at risk, since the cache drive is not redundant. Am I missing something about the cache preferred setting? Does the mover also copy that to the spinning disks when it runs? If not, then why not? Or am I lacking an understanding of how the docker stuff works? Is the unique docker data not at risk with the cache drive failing? Thanks for the help on this?

Awesome container, just found it and giving it a spin as a replacement for Plex. Some questions about the docker though, it looks like it only exposes the http port to the network, but none of the others. I am giving the container it's own IP and would like to use HTTPS to access it, but I am unclear on how I expose that port (8920) for clients to connect. I added it to the docker, but it does not show up and the connection is denied when I try to connect. I also want to open up the client discovery port (UDP 7359) so that my TVs and other such devices can find the server and make the setup easier. I edited the Docker, added the ports, matched their settings to the one already defined port and this did not work. So there is a step or something I am missing.

Interesting, this is news to me. I've never run into the issue before, though I don't reboot all that often, and yes it's unRAID. Can you point me to the "go" file you mention?

Got it! I went through the log much more thoroughly and found this: [info] Attempting to load iptable_mangle module... 2020-05-20 10:15:32,602 DEBG 'start-script' stderr output: modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/4.19.107-Unraid 2020-05-20 10:15:32,602 DEBG 'start-script' stdout output: [warn] Unable to load iptable_mangle module using modprobe, trying insmod... 2020-05-20 10:15:32,603 DEBG 'start-script' stderr output: insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory 2020-05-20 10:15:32,603 DEBG 'start-script' stdout output: [warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN [info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle' [info] Synology users: Please attempt to load the module by executing the following on your host: 'insmod /lib/modules/iptable_mangle.ko' Ran the /sbin/modprobe iptable_mangle command, and it is now working. What would have caused that module to unload? Or is it a requirement of the updated version of the docker that was not required before?

Would this cause the WebUI to time out? I just changed my unraid IP and I am trying to work out if my issue is this known issue or something else.

So how do I get settings and labels created/changed in rutorrent to persist? I am finding that anything changed in settings won't stick, and as soon as I remove the last torrent in a label that label then disappears and I have to recreate it.

I think the restart issue was definitely a type on my part. I re-typed it again, making sure it was right. Saved the file and not it has come up and my port checks out ok. I was using nano to edit it, so no idea how it got goofed up. Does rtorrent have a config check command like Apache and some others do?

After some reading, I went into rtorrent.rc file again and uncommented the line about incoming port range, and then set that to 7859. Saved and restarted the docker and now it won't come back up at all. network.port_range.set = 7859-7859 2020-01-23 11:06:43,760 DEBG 'watchdog-script' stdout output: [info] Removing any rTorrent session lock files left over from the previous run... 2020-01-23 11:06:43,762 DEBG 'watchdog-script' stdout output: [info] Attempting to start rTorrent... 2020-01-23 11:06:43,765 DEBG 'watchdog-script' stdout output: Script started, file is /home/nobody/typescript 2020-01-23 11:06:43,796 DEBG 'watchdog-script' stdout output: Script done, file is /home/nobody/typescript 2020-01-23 11:07:13,010 DEBG 'watchdog-script' stdout output: [warn] Wait for rTorrent process to start aborted, too many retries 2020-01-23 11:07:13,017 DEBG 'watchdog-script' stdout output: [info] Autodl-irssi not enabled, skipping startup [info] Initialising ruTorrent plugins (checking rTorrent is running)... And it just sits there indefinitely, not logging anything else.

First off, thank you binhex for these great dockers. I got mine setup pretty easily last night! I have everything working, but I am struggling with the port forward from AirVPN. I created a forward with them for port 7859 external to 7859 internal. I then edited the rtorrent.rc config file so that it has these lines set: dht.mode.set = on dht.port.set = 7859 Then in the GUI for ruTorrent, I went to settings -> Bittorrent and changed the port there to 7859. I then restarted the docker. The problem I am seeing is that the port check at the bottom of ruTorrent has the red exclamation and tells me that port 6881 is closed, and if I do a port check from AirVPN, it does not appear to work either. So I am unsure where else I need to change that port. Ok, unrelated to that I am curious if the deluge-VPN docker supports RSS feeds for downloading. Mostly because I am not a huge fan or rTorrent.

Thank you @T0a! I've been trying to get this to work for a while now, but your instructions were spot on. Everything is working nicely now.

Hi There, I am trying to get Emby working and I've managed to add and start the emby docker container. I can get to config page, but I cannot for the life of me work out how to add the media folders. I have tried using a standard unc (\\192.168.1.x\movies) and browsing to the "Network" option, but I keep getting an error popup at the bottom that says it can't connect. So how do I add the media? And in such a way that the kodi addon will work with it? Is there a howto somewhere that has all the steps on how to install the emby docker on unRAID and configure it?