Freedomfries

Am having exactly the same issue. From Binhex Krusader I'm looking at the permissions for the /config folder you are referring to, and it does not seem to allow any writing. What's more concerning is that there isn't any data at all, which leads me to believe the docker app is installed somewhere else???

Kept troubleshooting some more this morning and I did something which I hadn't tried before, I deleted the test torrents that errored out earlier and added new ones. Now those work just fine!!! I never assumed that something on the torrent could have gotten stuck, and apparently my latest config is working normally but I wasn't able to confirm that since I kept trying to restart the errored torrents. Big thanks to wgstarks and binhex. I hope this thread can help others get set up properly.

Inside Qbittorrent's settings, my downloads are set to: The directory looks to be mapped properly. Only other thing I fiddled with is the polling time and the disk cache settings under advanced. I added a bit more memory and set the refresh interval to 2000ms, the disk queue size to 1024kb, oh, and the max active torrents to 6. I wouldn't expect these to cause a problem.

I suspected that as well. I did configure the output directories the same as I did when I tested Deluge. I think the issue might be something else. Maybe I'm experiencing the same problem as ados.

Had time to do more poking around tonight. I was able to get Deluge with my openVPN settings to work, download a torrent and was able to verify that my IP is tunneled through the VPN. This removes some potential external culprits. Still unable to get Qbitorrent to download. I tried multiple openVPN config files, I deleted the docker and reinstalled it, no dice. Torrents just sit at 0 kb/sec bandwidth with the "errored" status. I added a tracker torrent to test with an external website that the client is connected, and it is, with the VPN's IP. So my client is visible from the torrent network. I can see peers and seeds on the torrents added. I just can't figure out my torrents cannot pick up download speed.... There are no suspicious messages in supervisord... Any suggestions would be greatly appreciated.

I followed your directions and added the VPN config file to the directory, and re-enabled the VPN mode, and I can start the docker. I can access the WEB UI, and I even was able to add a torrent download as a test. It's been on active for a while, but there's no bandwidth usage up or down. I have no indication that a connection to seeders is being made. It's a Ubuntu distro, so I would expect it to start downloading right away. To troubleshoot, I disabled the VPN component, and it still fails to download, so I don't think it's VPN related. Also, how can I test that I have a proper VPN tunnel established?

I wouldn't know for sure. My uneducated guess is from reading the description of the docker. It "uses IP tables to prevent IP leakage when the tunnel is down". Could this be it, or some sort of kill bit? I do NOT have the VPN config properly set up, since I expected this would be a secondary step. Maybe the docker shuts down once it fails to establish a VPN tunnel? Total conjecture here. EDIT: So I just disabled the VPN component by setting the flag to "NO". I can now run the docker just fine. It seems my guess was correct. Or at least the issue has to do with VPN configuration. Thank you for alerting me to this. My next steps are to 1- switch the web GUI to another port to avoid conflicts, though at the moment I'm not running any other dockers. I'm guessing this can all be accomplished in the docker settings 2- I dowloaded a vpn config file from my provider, and need to properly set up tunneling. Pretty sure I'm going to struggle with this one, so any pointers are welcome! Do you use an OpenVPN compatible service?

This is the command: docker run -d --name='binhex-qbittorrentvpn' --net='bridge' --privileged=true -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="OKTONAS" -e HOST_CONTAINERNAME="binhex-qbittorrentvpn" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='redacted' -e 'VPN_PASS'='redacted' -e 'VPN_PROV'='custom' -e 'VPN_CLIENT'='openvpn' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='no' -e 'WEBUI_PORT'='8080' -e 'LAN_NETWORK'='192.168.1.0/24' -e 'NAME_SERVERS'='84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1' -e 'VPN_INPUT_PORTS'='' -e 'VPN_OUTPUT_PORTS'='' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8080]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/qbittorrent-icon.png' -p '6881:6881/tcp' -p '6881:6881/udp' -p '8080:8080/tcp' -p '8118:8118/tcp' -v '/mnt/user/Torrent_Downloads':'/data':'rw' -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn' bd1ae2466cddb55b263864532b6e083104430838898c184f1c4fdf7aac30003a ----------------------------------------------------------- I have no other dockers running at the moment.

Hi all, I've been running Unraid for a year now with no issues. Currently on 6.11.5. Yesterday I decided to give binhex-qbittorrentvpn a try so I dowloaded the docker and attempted to configure it. I'm pretty noobish and can't even get the docker to run once it is installed. So here's my first problem. Clicking start on the docker, I can hear something loading and the cursor shows spinning wheel, but then it just stays stopped. Looking at my syslog, all I see is this: Feb 7 12:34:02 OKTONAS kernel: docker0: port 2(veth972c9b2) entered blocking state Feb 7 12:34:02 OKTONAS kernel: docker0: port 2(veth972c9b2) entered disabled state Feb 7 12:34:02 OKTONAS kernel: device veth972c9b2 entered promiscuous mode Feb 7 12:34:05 OKTONAS kernel: eth0: renamed from vethfc70d21 Feb 7 12:34:05 OKTONAS kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth972c9b2: link becomes ready Feb 7 12:34:05 OKTONAS kernel: docker0: port 2(veth972c9b2) entered blocking state Feb 7 12:34:05 OKTONAS kernel: docker0: port 2(veth972c9b2) entered forwarding state Feb 7 12:34:06 OKTONAS kernel: docker0: port 2(veth972c9b2) entered disabled state Feb 7 12:34:06 OKTONAS kernel: vethfc70d21: renamed from eth0 Feb 7 12:34:07 OKTONAS kernel: docker0: port 2(veth972c9b2) entered disabled state Feb 7 12:34:07 OKTONAS kernel: device veth972c9b2 left promiscuous mode Feb 7 12:34:07 OKTONAS kernel: docker0: port 2(veth972c9b2) entered disabled state I obviously have no clue what's missing, I would expect to at least be able to start the docker. Thanks in advance for your suggestions.

While browsing my server logs to investigate an unscheduled reboot of my server, I found log entries related to an "AVAHI daemon" : Aug 20 04:09:45 OKTONAS root: Starting Avahi mDNS/DNS-SD Daemon: /usr/sbin/avahi-daemon -D Aug 20 04:09:45 OKTONAS avahi-daemon[3909]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214). Aug 20 04:09:45 OKTONAS avahi-daemon[3909]: Successfully dropped root privileges. And it goes on about joinin mDNS multicast group and "successfully connecting to Avahi daemon"... I'm just curious as to what these are pertaining to, and how they relate to my pretty plain vanilla UNRAID configuration. Thanks for any tips.

I have the Serviio docker installed and running to serve as a music server, and it's been running well so far. The one thing I notice is my disk array will stay spinning up as long as the docker is active. I'm assuming the server activity is what keeps the array spun up. I haven't set a use of my cache disk for my share where my music is. Does anyone know if setting the share to use my ssd cache will result in Serviio to start serving data off the cache disk instead? I guess this would be the same for any media server docker... Thanks for your input.

Well it's pretty quiet in here. I recommend ppl who have Serviio specific questions to head to their forums where there is more activity.

Well, no one chimed in on this post yet, but I'll share what I did to mitigate this, in case someone else has to deal with it. First, I recommend reading the SAMBA manual for configuration suggestions. You can find it here: https://wiki.samba.org/index.php/User_Documentation Since my server is standalone, I originally thought it would help to enable "local master election" in the workgroup settings. This is what is causing the interval polling. The server isn't finding ITSELF. I haven't found a proper configuration with Local Master enabled that doesn't return this behavior, so I simply disabled it. I also added the extra configuration of enabling a WINS server, however, and pointing and set my local windows machines' IPv4 settings to use it, and turned on netBIOS. Since then, it seems my computers are always showing in my network environment, and browsing shares seems more responsive.

This is accompanied by " Unable to sync the browse lists in this workgroup". I'm guessing I'm missing something in my SMB configuration. My home network only comprises 2 other desktop windows PC's and a couple laptops. I'm not sure what I'm missing. Is a WINS server to be set up on one of my Windows boxes? Thanks for any suggestions.

Understood thank you. How do you find a file corruption report using BTRFS? I would expect to be able to restore a corrupted file from the parity volume, since you can restore it if the drive fails... but I guess you need a backup. Interesting.