MarkusMcNugen

Thanks, but unfortunately that is not the log I needed. I need the qBittorrent log that is stored in /mnt/cache/appdata/qbittorrentvpn/qBittorrent/data/logs

I guess that's good to know about the ovpn file. It sounds like your VPN provider didnt give you a very well formatted file or one formatted for Windows usage. The WebUI port is hardcoded, what you are changing in the container config is the open port from the container not an environmental variable I can read and replace the default with when its ran. Although that is a good idea and will be making that change this weekend. The warning you are seeing is most likely this one which is an option you can include in your ovpn file: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this You may also see this since the credentials.conf file is writable from the host: WARNING: file 'credentials.conf' is group or others accessible It would be helpful if you would provide the qbittorrent log file in /config/qBittorrent/data/log so I can see if there is some errors being thrown about. I just recreated the container with a new config location and everything and cant seem to reproduce any errors myself. I may make this container more automated as you suggested. I'll include a USERNAME and PASSWORD variable and save them in a conf file for the user and apply the "auth-user-pass" option in the ovpn config automatically, should be similar enough to binhex's containers. As for Sonarr/Radarr, I use both of them with this container with no problems.

Squid got it right if you meant the qBittorrentvpn WebUI credentials. They are posted on the Github and Dockerhub descriptions. They are worth a read if you want to understand how the container fully works. You can change the admin credentials to anything you like, or disable authentication entirely for the local network. Totally up to you! Thanks Squid! I didnt realize I wasnt getting email notifications from the unRAID forums. Im glad I checked back a few days ago so I could help some users and remedy that situation.

The iptables script included in the container was forked from binhex's sabnzbd docker container. You are more than welcome to verify this one for yourself. Below shows the iptables list from within the container. 1195 = OpenVPN port 8080 = WebUI port 8999 = Incoming connections port root@9be145563d9e:/# iptables -S -P INPUT DROP -P FORWARD ACCEPT -P OUTPUT DROP -A INPUT -i tun0 -j ACCEPT -A INPUT -s 192.168.2.0/24 -d 192.168.2.0/24 -j ACCEPT -A INPUT -i eth0 -p udp -m udp --sport 1195 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 8080 -j ACCEPT -A INPUT -s 192.168.2.0/24 -i eth0 -p tcp -m tcp --dport 8999 -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 192.168.2.0/24 -d 192.168.2.0/24 -j ACCEPT -A OUTPUT -o eth0 -p udp -m udp --dport 1195 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 8080 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT -A OUTPUT -d 192.168.2.0/24 -o eth0 -p tcp -m tcp --sport 8999 -j ACCEPT -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT -A OUTPUT -o lo -j ACCEPT I dont see anything in the log you provided that shows an error or why it wouldnt load. It should load up as long as you arent using the WebUI button from unRAID. qBittorrent throws a redirect header error when the WebUI is launched from the unRAID menus. Instead try loading the IP address and port directly in a browser address bar. Its a qBittorrent issue for security purposes, nothing I can do about it. The github and dockerhub descriptions explain this. I've updated the unRAID docker template to reflect this in the container description as well. If it still won't load, send me the log file in /config/qBittorrent/data/logs and I'll take a look for errors. You need to save your credentials in a file in the same directory as your .ovpn file seperated by a new line. Example: jdoe jdoepass Then put this in your .ovpn file at the top: Example: (Using credentials.conf as an example) auth-user-pass credentials.conf

Added OpenConnect VPN Server

Somebody correct me if I'm wrong, but you can't really add dependencies to a running container and have it be persistent across reboots. You would need to clone the github repo and modify the Dockerfile to add the dependency via a RUN command either directly in the Dockerfile itself or via a bash/shell script that gets copied to the container. Then build and run the container.

Welcome to MarkusMcNugens docker repo support topic! I'll be adding more docker containers over time, and will provide support for the containers below. qBittorrentvpn Overview: Docker container which runs the latest headless qBittorrent client with WebUI while connecting to OpenVPN with iptables killswitch to prevent IP leakage when the tunnel goes down. Reason: I put this container together because I couldn't find a qBittorrent docker that supported dropping in your own ovpn files like Binhex's containers do. All of them had prebuilt configuration files which aren't as user-friendly when your VPN provider isn't included. Tags: latest/bionic Base Image: Ubuntu 20.04/Ubuntu 18.04 Size: 300MB/403MB Application: https://www.qbittorrent.org/ Application Version: qBittorrent 4.3.3 Docker Hub: https://hub.docker.com/r/markusmcnugen/qbittorrentvpn/ Github: https://github.com/MarkusMcNugen/docker-qBittorrentvpn Note: Default WebUI credentials can be found on the Github and Docker Hub descriptions. Note 2: qBittorrent will throw a WebUI: Invalid Host header, port mismatch error if you use port forwarding with bridge networking due to security features to prevent DNS rebinding attacks. If you need to run qBittorrent on different ports, instead edit the WEBUI_PORT_ENV and/or INCOMING_PORT_ENV variables AND the exposed ports to change the native ports qBittorrent uses. OpenConnect VPN Overview: OpenConnect VPN server is an SSL VPN server that is secure, small, fast and configurable. It implements the OpenConnect SSL VPN protocol and has also (currently experimental) compatibility with clients using the AnyConnect SSL VPN protocol. The OpenConnect protocol provides a dual TCP/UDP VPN channel and uses the standard IETF security protocols to secure it. The OpenConnect client is multi-platform and available here. Alternatively, you can try connecting using the official Cisco AnyConnect client (Confirmed working on Android). The Dockerfile was written to always download and compile the latest release of OpenConnect VPN server when built. Reason: You can never have too many kinds of VPN servers! I forked ocserv from TommyLau and updated it to the latest version of Alpine and OpenConnect Server. I made the container have persistence for configuration files, drop in your own certs if you'd like or have the container make them for you, and advanced configuration for power users that know what they are doing, and numerous other enhancements. Base: Alpine 3.13 Size: 63.6MB Application: https://ocserv.gitlab.io/www/index.html Application Version: OpenConnect Server 1.1.2 Docker Hub: https://hub.docker.com/r/markusmcnugen/openconnect/ Github: https://github.com/MarkusMcNugen/docker-openconnect SFTP Overview: Easy to use SFTP (SSH File Transfer Protocol) server with OpenSSH and Fail2ban installed for extra hardening against brute force attacks. Forked from atmoz/sftp. Reason: I was using atmoz/sftp as an sftp docker container exposed to the internet for some friends to access and realized there was no banning mechanism included. I was getting hammered by brute force attacks so I forked his github repo and modified the image to include fail2ban, made some entrypoint modifications so files can be easily added/edited/viewed from the /config volume. Base: phusion/baseimage:master-amd64 Size: 357MB Application: https://www.openssh.com/ Application Version: Latest when docker was built on 03/22/2021 Docker Hub: https://hub.docker.com/r/markusmcnugen/sftp/ Github: https://github.com/MarkusMcNugen/docker-sftp Note: Please read the Github or Docker Hub descriptions. While this container is easy to use, it does require some small configuration. Note 2: NOT affected by the recent CVE-2021-3449 vulnerability with OpenSSL. This container runs OpenSSL 1.1.1f. Only versions 1.1.1h-1.1.1j were vulnerable per Ars Technica CrushFTP 10 Overview: Share your files securely with FTP, Implicit FTPS, SFTP, HTTP, or HTTPS using CrushFTP Reason: I couldn't find a good CrushFTP 10 container from a quick search of dockerhub or Unraid community apps. Tags: latest/ubuntu Base Image: Alpine 3.12/Ubuntu 20.04 Size: 234MB/641MB Application: https://www.crushftp.com Application Version: CrushFTP 10.1 Docker Hub: https://hub.docker.com/r/markusmcnugen/crushftp Github: https://github.com/MarkusMcNugen/docker-CrushFTP