• Content Count

  • Joined

Community Reputation

4 Neutral

About MarkusMcNugen

  • Rank
  • Birthday 09/28/1988


  • Gender
  • Location
    MI, USA

Recent Profile Visitors

1094 profile views
  1. I will see if I can do this over the weekend. I usually just build from dockerhub with auto triggers and call it good but I have a VM I use for building as well.
  2. Nope, with the way docker and VPNs work it has to be privileged mode due to the host sharing the kernel space with the docker.
  3. Not sure how you have this setup, but it looks to me like you have the wrong LAN_NETWORK defined. ip route command seems to show as the connected LAN network. You have it set to
  4. I recently updated the docker manually to force qBittorrent to v4.1.4 since it's been released. I ran into an issue where the Web UI wasn't defaulting to english like it was suppose to if it's blank in the config so the WebUI was showing up as mostly blank. This can be easily fixed by setting the language in the WebUI settings or by editing "/config/qBittorrent/config/qBittorrent.conf", or from the Unraid host "/mnt/cache/appdata/qbittorrentvpn/qBittorrent/config/qBittorrent.conf", and setting "General\Locale=en" in the file. This is definitely a qBittorrent issue, but if anyone ru
  5. I dont think there is much I can do about the temp folder, that sounds like a qbittorrent issue. As for the unmounting issue, that sounds like an Unraid/Docker issue. I dont think there is much that can be done from my end to detect and stop that issue. If it occurs again you may try opening a troubleshooting topic on here and posting your logs. Sorry about this guys, must have left my personal config for the ports in the default config. It's been fixed now. Possibly related? "This is beyond the scope of openpyn but looks like it's likely
  6. @Everyone qBittorrentvpn WebUI and ConnectionPort overwrite issue resolved I have fixed the stupid issue with the broken WebUI and Connection port environmental variables not setting correctly in the config file. (In fact, everyone should check the qBittorrent.conf config file and delete any extra WebUI and ConnectionPort lines that may have been added to it... my bash script was left in a broken state, forgot to sync the changes to github, that would echo the line into the config every time instead of replacing the correct line...) CSRF protection disabled by defaul
  7. Hello everyone, I am back! I'm sorry to all you guys I left hanging over the summer. I left some things in a broken state by mistake (Didnt sync my last changes to github like a flucking idiot...) Decided to take a sabbatical and spend time with my two kids over the summer. Now that it's starting to get colder outside I have returned and will continue to maintain these dockers.
  8. Hi Kuusou, First, I screwed up my script before taking the summer off to spend with my family. The WebUI and Connection port environmental variables were not being applied correctly to overwrite the default config. This has been fixed. Second, qBittorrent had a feature to block cross site request forgery which blocked proxies (unless they were configured properly to not send the referrer IP in the header. They finally added an option to disable this feature, which I have now enabled by default with new installs of this docker. If you update the docker, you can disable it yourself fro
  9. Please attach your ovpn file (You can remove the keys from the file before posting)
  10. Container and template have been updated. You can now provide the VPN username and password to environmental variables and it will create the credentials.conf file and configure your ovpn config file automatically. You can also edit the WEBUI_PORT_ENV and INCOMING_PORT_ENV variables (Youll need to change the exposed ports as well) to modify the ports qBittorrent uses without having to do port forwarding and getting the DNS rebinding issue. If you already have the container installed you may need to delete and recreate it to get the new template applied, or just simply update the co
  11. Hi Whauk, Thank you for providing that log. qBittorrent implements a security feature against DNS rebinding which seems to be messing with Bridge/HOST configurations and port forwarding done by Docker. Im about to update the container to allow people to change the official qBittorrent ports with environmental variables. Source:
  12. 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
  13. 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
  14. 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.
  15. 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 -d -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