Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About MarkusMcNugen

  • Rank
  • Birthday 09/28/1988


  • Gender
  • Location
    MI, USA

Recent Profile Visitors

442 profile views
  1. 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
  2. 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 runs into this issue here is the fix. For new installs I set the default qBittorrent.conf file to default the locale to en to avert this issue. The bug has officially been reported to qBittorrent here.
  3. 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 that some UDP packets are getting dropped (wifi reception is not that good?). https://airvpn.org/topic/14094-weird-log-entries/ It won't happen if you use "--tcp" but there might be some speed loss." https://github.com/jotyGill/openpyn-nordvpn/issues/107
  4. @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 default on new installs New installs will have CSRF protection disabled in the options by default. This is the setting that breaks basic reverse proxy configs from working and stopped the WebUI link from Unraids menu from working. This option can be enabled at any time via the WebUI or qBittorrent.conf config file. If you updated this docker, this feature will not be disabled by default. If you want it disabled then you can edit it via the WebUI qBittorrent preferences in the WebUI section, or add "WebUI\CSRFProtection=false" to your qBittorrent.conf config file. HTTPS I purposely did not generate any certs and apply them for HTTPS for qBittorrent's WebUI. I assumed that most people would be running this behind a reverse proxy like letsencrypt or Nginx that would provide the TLS encryption necessary to secure the connection coming in from the outside. I also assumed that if you were savvy enough to set something like that up, you probably had the means to generate your own certificate and key to paste into the qBittorrent preferences via the WebUI to enable it. If this feature is requested by multiple people I will add it and possibly set it as the default. SFTP I am open to suggestions on how to make this docker more user-friendly and to simplify the installation and configuration process. If anyone has any ideas, voice them. I specifically made this because I couldnt find any good SFTP dockers made for Unraid. Willing to create a develop branch for testing changes and have people test if any improvements or suggestions are provided.
  5. 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.
  6. 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 from the WebUI or by editing the qbittorrent.conf config file and adding "WebUI\CSRFProtection=false" to it. This also fixes the WebUI not working when trying to open from the Unraid menu. This is a feature they is in development for the WebUI. I'm not so much a developer as a hobbyist. I know some Python, PHP, Bash, C#, Visual Basic and a few others. I can work my way around code to understand how it works but I dont do much with contributing to actual projects. My degree is in computer networking, unfortunately not programming. Check your messages, PMed you! Also in the message I sent to you! Yeah, can't believe I did that... lol. It's alright, I switched VPN providers and have a different username and password anyways. On top of that my account is locked down and I use the max connections from my provider at all times. Yep, indeed they have. Fixed it now, but not really worried about it. Haha, yeah, pretty stupid mess up on my part... Sorry for the sabbatical guys. I have returned!!!
  7. Please attach your ovpn file (You can remove the keys from the file before posting)
  8. 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 container and add the variables to the config yourself. You can see the template here.
  9. 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: https://github.com/qbittorrent/qBittorrent/issues/7641
  10. 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
  11. 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.
  12. 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.
  13. 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 tcp -m tcp --sport 8080 -j ACCEPT -A INPUT -s -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 -d -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 -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
  14. 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.