Forty Two

The name of the container is: binhex-qbittorrentvpn. I've edited that in the file, same as it is for other containers that are on Swag and are working. It is on the same network created specially for Swag. I use Cloudflare for DNS. There is no special setting for each container. There is a wildcard setting. The error I get is: 502 Bad Gateway, with a "Not secure" note.

Could somebody help me out? I've been trying to get binhex-qbittorrent to run with swag. I used the regular qbittorent subdomain conf file, and swapped the container name and port. The Subdomain(s): variable field for the container contains "qbittorrent" File attached. binhex-qbittorrent.subdomain.conf

That was easy enough to verify, and it indeed solved the problem. For reference, the field LAN_NETWORK should state: IP networks, comma separated, without spaces. THANKS!

I've been accessing it through wireguard remotely. All other containers work as expected.

Thanks. I'll replace that pass. Slipped my mind when I posted the second time. I edited in a minute, but nevertheless. I've attached the file, since it's too long. I hope I edited all the passwords out of it. supervisord.log

Thanks, I am indeed running UnRaid. I've run into similar difficulties with Deluge, and decided to switch, as Qbittorrent has a better gui anyway. Here is how that looks now: docker run -d --name='binhex-qbittorrentvpn' --net='swagproxy' --ip='172.18.0.55' --privileged=true -e TZ="Europe/Budapest" -e HOST_OS="Unraid" -e HOST_HOSTNAME="MARVIN" -e HOST_CONTAINERNAME="binhex-qbittorrentvpn" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='XXXXXXXX' -e 'VPN_PASS'='XXXXXXXX' -e 'VPN_PROV'='custom' -e 'VPN_CLIENT'='openvpn' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'WEBUI_PORT'='8116' -e 'LAN_NETWORK'='192.168.42.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:8116]/' -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 '8118:8118/tcp' -p '8116:8116/tcp' -v '/mnt/user/appdata/data':'/data':'rw' -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn' 6ae71aedc744cddfe750d687c842587862458728cdc225513e1f367db68c8af5 The command finished successfully! Still no access to the UI. The browser says "This site can’t be reached"

Thanks! I don't have that option in the gui? How would I go about changing that setting?

I too have trouble accessing the GUI. The VPN worked, but it stopped in the meantime. Here is the config for the container: docker run -d --name='binhex-qbittorrentvpn' --net='swagproxy' --ip='172.18.0.55' --privileged=true -e TZ="Europe/Budapest" -e HOST_OS="Unraid" -e HOST_HOSTNAME="MARVIN" -e HOST_CONTAINERNAME="binhex-qbittorrentvpn" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='XXXXXX' -e 'VPN_PASS'='XXXXXX' -e 'VPN_PROV'='custom' -e 'VPN_CLIENT'='openvpn' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'WEBUI_PORT'='8116' -e 'LAN_NETWORK'='192.168.42.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:8116]/' -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 '8116:8080/tcp' -p '8118:8118/tcp' -v '/mnt/user/appdata/data':'/data':'rw' -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn' 472b97658a6912de72f09983597e5e10396a903086b61288959d8968f13fdb86 If anybody has ideas, let me know.

Hi all, I'm running the backup appdata plugin. The scan suggests to switch to the KluthR version, because the original has been deprecated. I've checked, and I am running the KluthR version. Any suggestions?

Not to argue with CCIE laureates, but I do have some network experience, and this sounds like "it's not a bug, it's a feature".

It currently works for me, and that without the solution oulitined here: Hope that you solve this.

Hi, I've been getting periodic 403 errors with this container. Rebooting seems to help for a couple of weeks. Any ideas?

Thanks!

Hi all, I have regular magnetic hard drives in the array and nvme in the cache. It would make sense to adjust nvme warning and critical temperatures to a higher setting, but when I go to main > cache (or cache 2) > SMART settings, and change the temperature, it reverts to default for the array. This happens if I set it with the array off or on line. Any suggestions?

It will, if the processor has an iGPU.

I'll get it working, and the whole setup looks great. I really appreciate the amount of work you've put into this. Just a little bit disappointed that I have to start over.

I just got 1.3 to work in full. Very little works in 1.4, at least for me. Just for example this is the code to get fan dials to work on my system: SELECT last("fan_input") FROM "sensors" WHERE ("feature" =~ /fan./) AND $timeFilter GROUP BY time($__interval), "feature" Set ALIAS BY to: $tag_feature

Here: https://forums.gentoo.org/viewtopic-t-1107956-start-0.html Somebody would really need to thoroughly rewrite the auto fan script though.

WS C246 PRO does not have IPMI. WS C246M PRO does. Anyway, I have solved the problem. Add, to boot/syslinux/syslinux.cfg append line: acpi_enforce_resources=lax So that it looks like: default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label Unraid OS menu default kernel /bzimage append initrd=/bzroot acpi_enforce_resources=lax label Unraid OS GUI Mode kernel /bzimage append initrd=/bzroot,/bzroot-gui acpi_enforce_resources=lax label Unraid OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label Unraid OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest Adding modprobe nct6775 to the go file is still a good idea.

I can't get the nct6775 controller to display fan speeds. Tried: modprobe -v force-id:0x290 sensors-detect detects it as a nct6796d Any help?

A couple of notes: The drive cooling is indeed a slight problem. I have made some mods and added two slim side fans. I plugged the cage coolers into the two cage plugs, as instructed by the manufacturer. I'll see how the temperatures go. I might make some other modifications. I can't get the case fans to register with the Dynamix System Temperature plugin. I've tried adding modprobe nct6775 to the go file. It might be due to some BIOS setting? The USB kept getting unmounted from the internal USB port. This might have been due to the fact that I it has been exported as a share. Anyway, I turned off the export setting and moved the USB to the back panel. This seems to have solved the issue.

I chose the pro version because it has two m.2 connectors, so I can mirror the cache.

I can only find the /SE version on ASUS's website for the micro ATX (C246M). Can you send me the link for the /SE version for the full ATX one?

On the switch, maybe, a CRS305-1G-4S+IN down the line. Although I don't really think I would need one in my usage scenario. Thanks for the CS380 tips. Throwing in a couple of Noctua fans etc is not a problem.