a_n_d_y

1. Yes 2. If Disk1 is part of the array, it will constantly be writing to the Parity drive. You might look into the Unassigned Devices plugin to add a disk outside of the array (you'll need another spare disk for this) and then move your completed download to the array. 3. Edit the docker, then click "Add another Path, Port, Variable, Label or Device" Change Config Type to "Path" Enter a Container Path, ex. /new_download_location Enter a Host Path, ex. /mnt/Disk1/Downloads Click save The path /new_download_location will show up inside of the container and it points to /mnt/Disk1/Downloads. Go into the qBittorent webui, Tools > Options > Downloads. Change Default Save Path to /new_download_location.

Edit the docker container and put this into the repository field: binhex/arch-qbittorrentvpn:4.1.9-1-01 You can roll back to any release. Go to the Github page for the docker container and replace the text after the colon with the release number: binhex/arch-qbittorrentvpn:[release_number] If you want the latest release once an update that resolves these issues is available, change to: binhex/arch-qbittorrentvpn:latest

If the docker is running, but the gui is not accessible, give this a try. Edit the container, change to Advance View and in the Extra Parameters, enter this: -e HOMEBRIDGE_CONFIG_UI=1 I don't think you actually need the variables HOMEBRIDGE_VERSION, CONFIG_UI_VERSION, HOMEBRIDGE_CONFIG_UI, HOMEBRIDGE_CONFIG_UI_PORT if you do the above. They don't seem to do anything after the initial installation.

That stinks. Working over here fine. Might try removing the docker and image and then reinstalling with all the setting as is. Since the Config UI is just a plugin, if you have a running another Homebridge docker, could try just re-installing that plugin manually inside the docker container. Would be nice if someone was able to just port over OZNU's docker to be more Unraid compatible.

OK I think I figured it out. Config UI X installs as a Homebridge plugin. It defaults to port 8080. You should update config.json manually for the port of the UI and then it should work.

I happen to be using Network Type as Host instead of Bridge. You can either change it to Host or you'll have to pass the appropriate ports to the docker container (Homebridge service, GUI, possibly other stuff...) I believe that should do it.

I'm not 100% sure since I have not had to debug anything. In the UI if you click on the docker icon (top right) > Settings, there are some options to Debug and run in Insecure. Looks like DEBUG=Alexa* is just filter? Might be something you could ask OZNU about.

I can't directly help you with your question above. However, if you want to make using and managing Homebridge painless, including installing plugins, you should consider using the OZNU Homebridge docker. It has Homebridge Config UI X included: https://www.npmjs.com/package/homebridge-config-ui-x Community Apps > Search for "homebridge" > click "Click Here To Get More Results from DockerHub" Install oznu/homebridge Changes to Make: Repository: oznu/homebridge:latest Variables: /homebridge = homebridge appdata folder, ex. /mnt/cache/appdata/homebridge Enable UI: Add these variables HOMEBRIDGE_CONFIG_UI, set to 1 to enable HOMEBRIDGE_CONFIG_UI_PORT, set to 8080 or whatever port you want Then you can access the UI at the configured port above.

Anyone with experience running Node JS in docker? I tried using the official docker, but its not running. Not sure where to go from here.

Would you mind posting your settings.json and a screen shot of your docker configurations? Maybe we can spot the problem.

I'm really sorry, I mistyped above with this statement about your JSON file: If its "download-dir": "/downloads" then use "/downloads" as your Host Path. I meant "/downloads" should be your Container path, not Host Path! My bad. Anyways, if you're using this in Transmission now: "download-dir": "/downloads/complete","download-queue-enabled": true, "incomplete-dir": "/downloads/incomplete","incomplete-dir-enabled": true, Its looking for a folder "downloads" (with a lower case "d") in the docker container: /downloads --> /mnt/user/downloads/ If you already have a downloads share created named "Downloads" with a capital "D", then use this for Transmission (you should also have "Downloads" referenced in Sonarr): /downloads --> /mnt/user/Downloads/ When you set it as this: /downloads --> /mnt/user/downloads/ It created the share "downloads" with a lower case "d" Make the changes above to reference "Downloads" with a capital "D" and then delete the "downloads" share with the lower case "d" If you're using Windows to find the share on the network, I don't think it can distinguish between "Downloads" and "downloads". I think that should do it!

Just to be clear, you did not have a Downloads share already created? I would check the export settings of the share to make sure your SMB is exported.

If this is any help, from what I can remember I did this to setup: JSON "download-dir": "/downloads/complete", "download-queue-enabled": true, "incomplete-dir": "/downloads/incomplete", "incomplete-dir-enabled": true, "umask": 2, In /mnt/cache/Downloads/ I let Transmission create the "complete" and "incomplete" (torrent.part files) folders. Transmission /downloads --> /mnt/cache/Downloads/ Sonarr /downloads --> /mnt/user/Downloads/

Just verifying, what is your "download-dir" path in your settings.json file? If its "download-dir": "/downloads" then use "/downloads" as your Host Path. If your downloads folder is on your cache drive, ex. "/mnt/cache/Downloads" , try using "cache" in the path vs "user" We'll get this figured out!

Are you able to better explain the problem? Just a little hard for me to follow. I'd like to help if possible.

IIRC, rpc-whitelist needs to be changed in the Docker container and not in settings.json. Setting it there will overwrite what is in settings.json. Other settings can be directly updated in settings.json. Just make sure the docker container is stopped, edit settings.json (might need to change permissions on that file first), and then restart the docker. Its a little finicky getting everything up, but once it is, its solid.

That did the trick, thank you.

How do I install an earlier version of this docker? 0.38.4 is giving me trouble.

I had similar problems, but adding the additional variables required resolved it: https://lime-technology.com/forum/index.php?topic=48899.msg534306#msg534306

I have the latest and greatest as of 30 minutes ago. My bad, I should've dug back further in the support pages. Didn't realize additional variables needed to be manually added. I guess I thought they'd show up with the update. Anyways, working fine! Thank you!

I upgraded to the latest and greatest and having problems. The docker container says its running, but I can't access the web UI with PIA VPN enabled. Works fine with it disabled tho. What do you think? ErrorWarningSystemArrayLogin usermod: no changes [info] Env var PUID defined as 99 [info] Env var PGID defined as 100 [info] Permissions already set for /config [info] Starting Supervisor... 2017-01-29 12:25:08,584 CRIT Set uid to user 0 2017-01-29 12:25:08,584 INFO Included extra file "/etc/supervisor/conf.d/transmission.conf" during parsing 2017-01-29 12:25:08,586 INFO supervisord started with pid 16 2017-01-29 12:25:09,588 INFO spawned: 'checkproc-script' with pid 19 2017-01-29 12:25:09,589 INFO spawned: 'start-script' with pid 20 2017-01-29 12:25:09,589 INFO spawned: 'transmission-script' with pid 21 2017-01-29 12:25:09,590 INFO spawned: 'privoxy-script' with pid 22 2017-01-29 12:25:09,594 DEBG 'transmission-script' stdout output: [info] VPN is enabled, checking VPN tunnel local ip is valid 2017-01-29 12:25:09,594 INFO success: checkproc-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-01-29 12:25:09,594 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-01-29 12:25:09,594 INFO success: transmission-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-01-29 12:25:09,594 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-01-29 12:25:09,594 DEBG 'start-script' stdout output: [info] VPN is enabled, beginning configuration of VPN 2017-01-29 12:25:09,596 DEBG 'privoxy-script' stdout output: [info] Privoxy set to disabled 2017-01-29 12:25:09,597 DEBG fd 24 closed, stopped monitoring <POutputDispatcher at 47465293154064 for <Subprocess at 47465293107640 with name privoxy-script in state RUNNING> (stderr)> 2017-01-29 12:25:09,597 DEBG fd 20 closed, stopped monitoring <POutputDispatcher at 47465292105776 for <Subprocess at 47465293107640 with name privoxy-script in state RUNNING> (stdout)> 2017-01-29 12:25:09,597 INFO exited: privoxy-script (exit status 0; expected) 2017-01-29 12:25:09,597 DEBG received SIGCLD indicating a child quit 2017-01-29 12:25:09,602 DEBG 'start-script' stdout output: [info] VPN default certs defined, copying to /config/openvpn/... 2017-01-29 12:25:09,603 DEBG 'start-script' stdout output: [info] VPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn 2017-01-29 12:25:09,604 DEBG 'start-script' stdout output: [warn] VPN provider remote port incorrect, overriding to 1198 2017-01-29 12:25:09,626 DEBG 'start-script' stderr output: mknod: /dev/net/: File exists 2017-01-29 12:25:09,628 DEBG 'start-script' stdout output: [info] Default route for container is 172.17.0.1 2017-01-29 12:25:09,630 DEBG 'start-script' stdout output: [info] Adding 192.168.1.0/24 as route via docker eth0 2017-01-29 12:25:09,630 DEBG 'start-script' stdout output: [info] ip route defined as follows... -------------------- 2017-01-29 12:25:09,631 DEBG 'start-script' stdout output: default via 172.17.0.1 dev eth0 172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.2 192.168.1.0/24 via 172.17.0.1 dev eth0 2017-01-29 12:25:09,631 DEBG 'start-script' stdout output: -------------------- 2017-01-29 12:25:09,632 DEBG 'start-script' stdout output: [info] iptable_mangle module not supported, attempting to load... 2017-01-29 12:25:09,633 DEBG 'start-script' stderr output: modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/4.4.30-unRAID 2017-01-29 12:25:09,633 DEBG 'start-script' stdout output: [warn] iptable_mangle module not supported, you will not be able to connect to Deluge webui or Privoxy outside of your LAN 2017-01-29 12:25:09,644 DEBG 'start-script' stdout output: [info] iptables defined as follows... -------------------- 2017-01-29 12:25:09,644 DEBG 'start-script' stdout output: -P INPUT DROP -P FORWARD ACCEPT -P OUTPUT DROP -A INPUT -i tun0 -j ACCEPT -A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A INPUT -i eth0 -p udp -m udp --sport 1198 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 9091 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 9091 -j ACCEPT -A INPUT -p udp -m udp --sport 53 -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT -A INPUT -i lo -j ACCEPT -A OUTPUT -o tun0 -j ACCEPT -A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A OUTPUT -o eth0 -p udp -m udp --dport 1198 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 9091 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 9091 -j ACCEPT -A OUTPUT -p udp -m udp --dport 53 -j ACCEPT -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT -A OUTPUT -o lo -j ACCEPT 2017-01-29 12:25:09,644 DEBG 'start-script' stdout output: -------------------- 2017-01-29 12:25:09,644 DEBG 'start-script' stdout output: [info] Starting OpenVPN... 2017-01-29 12:25:09,652 DEBG 'start-script' stdout output: [info] OpenVPN started

Yeah none of the US ones will work. I use Toronto Canada and its fast for me.

You probably need to change the umask value in the settings.json file. I changed mine from the default 18 to 2. Stop Transmission You might need to chmod the settings.json file Open, edit, save Restart Transmission

I didn't know that, thanks. I added my lan 192.168.1.* and docker 172.17.42.* to the white list and Sonarr connected.

I had the same problem and I think I had to change Whitelist to *.*.*.* in the docker container advance view so it wouldn't block other applications.