[Support] dyonr - qbittorrentvpn


Dyon

Recommended Posts

Welcome to my fourth Docker Container that I've ever created. qbittorrentvpn, a fork of MarkusMcNugen's qBittorrentvpn, but with WireGuard support!

 

qbittorrent-icon-128.png.95be4d6a2a9e436e57b356360412bdb1.png

 

Overview: Docker container which runs the latest qBittorrent-nox client while connecting to WireGuard or OpenVPN with iptables killswitch to prevent IP leakage when the tunnel goes down. This project is based of my DyonR/jackettvpn, which is based of MarkusMcNugen's qBittorrentvpn.

 

Base: Debian 10.5-slim

Automated Build: Not yet

Application: https://github.com/qBittorrent/qBittorrent

Docker Hub: https://hub.docker.com/r/dyonr/qbittorrentvpn/

GitHub: https://github.com/DyonR/docker-qbittorrentvpn

 

Because this project is quite similar to MarkusMcNugen's Project, I asked permission of him beforehand.

Edited by Dyon
  • Like 1
  • Thanks 2
Link to comment
12 minutes ago, Jerky_san said:

Installed it to try. After restarting though it showed it wasn't running even though the log showed it was. Attempting to start or the service even after disabling docker and re-enabling shows "server error" very strange..

Does 'Server Error' show when you try to start/stop the Docker? Or do you see this in the WebUI of qBittorrent?

If  it is the WebUI, could you also share the Docker log of the container and the /config/qBittorrent/data/logs.

PLEASE MAKE SURE YOUR IP IS HIDDEN FROM BOTH LOGS

 

Edited by Dyon
  • Thanks 1
Link to comment
Just now, Dyon said:

Does 'Server Error' show when you try to start/stop the Docker? Or do you see this in the WebUI of qBittorrent?

If  it is the WebUI, could you also share the Docker log of the container and the /config/qBittorrent/Logs.

PLEASE MAKE SURE YOUR IP IS HIDDEN FROM BOTH LOGS

 

Figured it out.. Had an old docker that also had 8080 allocated(thought it was set to stay stopped) but it wasn't and it was starting before qbit was. Btw so far the experience has been much better than deluge. Downloads are much faster so thanks a lot for putting out a wireguard docker.

  • Like 1
Link to comment
3 minutes ago, tola5 said:

other there have problem with upload  ether really not work or only upload few bite and stop ?

Do you have this problem with no vpn, WireGuard or OpenVPN? I personally have been using WireGuard for the past two days and I've uploaded more than 33GB already, which is normal for my speed. 

Link to comment
41 minutes ago, tola5 said:

WireGuard  do you change some settings ? it first time I try qbittorrent can I get you too take a pic off you settings perhaps ?

 

I haven't changed any settings myself, except disabling the temp-storage.  

Connection: TCP/µTP

Port 8999, use UPnP/NAT-PMP

Connection limits: 50/10/20/4

Bittorrent: DHT/PeX/Local Discovery

 

With how many DHT Nodes are you connected, shown at the bottom of the page.

Also; If you click on a torrent and go to the Peers section, do you see others?

And, what is the status of the trackers? Do they show as Working, Updating or Not working?

Link to comment
49 minutes ago, Dyon said:

I haven't changed any settings myself, except disabling the temp-storage.  

Connection: TCP/µTP

Port 8999, use UPnP/NAT-PMP

Connection limits: 50/10/20/4

Bittorrent: DHT/PeX/Local Discovery

 

With how many DHT Nodes are you connected, shown at the bottom of the page.

Also; If you click on a torrent and go to the Peers section, do you see others?

And, what is the status of the trackers? Do they show as Working, Updating or Not working?

368  DHT notes 

And for peers no on the list it show 0 (number) 

And tracker some work other don't.

It start too upload now but really bad only like 150kb can be unlucky but nomaly it a few MB sek

Link to comment
1 hour ago, tola5 said:

368  DHT notes 

And for peers no on the list it show 0 (number) 

And tracker some work other don't.

It start too upload now but really bad only like 150kb can be unlucky but nomaly it a few MB sek

 

please note that in order for uploading to work:

  1. you have to have port forwarding through your vpn provider and setup the client to use those ports 
  2. upload speed will be based on your vpn's location and your speed to it.
On 8/15/2020 at 7:07 PM, Dyon said:

Welcome to my fourth Docker Container that I've ever created. qbittorrentvpn, a fork of MarkusMcNugen's qBittorrentvpn, but with WireGuard support!

 

qbittorrent-icon-128.png.95be4d6a2a9e436e57b356360412bdb1.png

 

Overview: Docker container which runs the latest qBittorrent-nox client while connecting to WireGuard (experimental) or OpenVPN with iptables killswitch to prevent IP leakage when the tunnel goes down. This project is based of my DyonR/jackettvpn, which is based of MarkusMcNugen's qBittorrentvpn.

 

Base: Debian 10.5-slim

Automated Build: Not yet

Application: https://github.com/qBittorrent/qBittorrent

Docker Hub: https://hub.docker.com/r/dyonr/qbittorrentvpn/

GitHub: https://github.com/DyonR/docker-qbittorrentvpn

 

Because this project is quite similar to MarkusMcNugen's Project, I asked permission of him beforehand.

when wg is active, local access is blocked. This includes the webui. I have tried:

  1. changing the webui port from 8080 to another port 7979/8181
  2. editing qBittorrent.conf to change the webui port
  3. manually passing the port as an Extra parameter 
  4. giving the container its own ip
  5. adding my local network to the wg conf
    1. when doing this wg does not connect. the error message is "RTNETLINK answers: File exist". see the attached image.

these are the same issues i was unable to over come in my post here: 

 

when wg is off or openvpn is used. no issues.

 

wg-error.png

Link to comment
12 minutes ago, rukiftw said:

 

please note that in order for uploading to work:

  1. you have to have port forwarding through your vpn provider and setup the client to use those ports 
  2. upload speed will be based on your vpn's location and your speed to it.

when wg is active, local access is blocked. This includes the webui. I have tried:

  1. changing the webui port from 8080 to another port 7979/8181
  2. editing qBittorrent.conf to change the webui port
  3. manually passing the port as an Extra parameter 
  4. giving the container its own ip
  5. adding my local network to the wg conf
    1. when doing this wg does not connect. the error message is "RTNETLINK answers: File exist". see the attached image.

these are the same issues i was unable to over come in my post here: 

 

when wg is off or openvpn is used. no issues.

 

wg-error.png

@rukiftw I'll investigate. Are you running the container in Bridge mode or with an own IP (like br0 custom IP)?

 

Link to comment
23 hours ago, rukiftw said:

 

please note that in order for uploading to work:

  1. you have to have port forwarding through your vpn provider and setup the client to use those ports 
  2. upload speed will be based on your vpn's location and your speed to it.

 

yea test speed and it shold be ok it work now some time but fell more bad TorGuard vs PIA as I use before sadly there some problem with it at the moment. any way thx

Link to comment
59 minutes ago, itlists said:

I change the default admin password through qbt webUI. When I tried to login to the webUI with new password, I keep getting rejected. The login screen just keeps refreshing when clicking on Login

Could you check if you would be able to log in using a In-Private/Incognito window?

Edit: I was able to replicate the issue. It seems to be a caching issue from a browser.

If you use Chromium-based browsers (Google Chrome, the new Microsoft Edge, Brave), Press F12, go to the Applications tab, select 'Clear Storage'.

Note that this will also clear the cookies related to Unraid itself.

Edited by Dyon
Link to comment
19 hours ago, rukiftw said:

@Dyon i have tried both ways. 

I'm sorry, but I havent been able to replicate your issue. I only get the message 'RTNETLINK answers: File exists' if I use a custom IP (which is, as a side note, not recommended).  

Could you maybe tell more about the setup that you are using?

Did you keep the Docker settings as default? Does the WireGuard config work on other devices like your PC or Phone?

 

Link to comment
1 hour ago, Dyon said:

Could you check if you would be able to log in using a In-Private/Incognito window?

Edit: I was able to replicate the issue. It seems to be a caching issue from a browser.

If you use Chromium-based browsers (Google Chrome, the new Microsoft Edge, Brave), Press F12, go to the Applications tab, select 'Clear Storage'.

Note that this will also clear the cookies related to Unraid itself.

Is there a way to reset the qBT config settings without removing and re-installing the container?

Link to comment
6 minutes ago, itlists said:

Is there a way to reset the qBT config settings without removing and re-installing the container?

Go to your appdata share and remove qBittorrent.conf: (appdata)/qbittorrentvpn/qBittorrent/config/qBittorrent.conf

Can also run this from the Unraid terminal (if you didn't change the config/appdata path):

rm /mnt/user/appdata/qbittorrentvpn/qBittorrent/config/qBittorrent.conf

This will remove all the qBittorrent settings, and install a clean config when the container starts up again.

Edited by Dyon
  • Thanks 1
Link to comment
1 hour ago, Dyon said:

Could you check if you would be able to log in using a In-Private/Incognito window?

Edit: I was able to replicate the issue. It seems to be a caching issue from a browser.

If you use Chromium-based browsers (Google Chrome, the new Microsoft Edge, Brave), Press F12, go to the Applications tab, select 'Clear Storage'.

Note that this will also clear the cookies related to Unraid itself.

Thanks. Any workaround for this other than clearing unRaid cache?

Link to comment
1 hour ago, itlists said:

Thanks. Any workaround for this other than clearing unRaid cache?

Unfortunately it seems to be caused by some policy of browsers.

I think this is what causes this issue:

If you have a Docker that hosts an application with the same Cookie name that qBittorrent also uses, called SID (session id cookie), it is unable to overwrite this cookie because qBittorrent is by default http, and a http website can not overwrite a https cookie.

 

See also this error message from Chrome.

image.thumb.png.ca5a0899eed78287ca19bf15ec3df205.png

 

I'll look into generation of https certificates by default of this Docker to bypass this.

  • Thanks 1
Link to comment
5 minutes ago, Jerky_san said:

Slightly off top topic but @Dyonany chance you could make a wireguard docker container for SABnzbd?

I never used SABnzbd, so I don't know how that program works and how to install it.

But based of the documentation on their website it seems relatively simple. I might look at it later, will also let you know via a private message if it's done, or if I need someone to test 😜

  • Like 1
Link to comment
4 hours ago, itlists said:

Thanks. Any workaround for this other than clearing unRaid cache?

I've pushed an update to the container.

  • The container will now check if the new environment variable called ENABLE_SSL is set to yes, if so, it will execute checks and fix the config to make it compatible.
    • By default this is set to 'yes' if you use the new template, which should be live within a few hours on CA.

If you would like to Enable SSL/HTTPS now please do the following:

  1. Update the container
  2. (Stop the container)
  3. Edit the container
  4. (bottom of page): Add another Path, Port, Variable, Label or Device
  5. Config type: Variable
    1. Name: ENABLE_SSL
    2. Key: ENABLE_SSL
    3. Value: yes
    4. Press add
  6. Scroll up to the top right and set the slider from basic view to advanced view
  7. Change 'http' in the WebUI section to 'https'
  8. Apply
  9. You should now have the container running with https.
Link to comment

Anyone know why I am getting the error?

 

Quote

Wed Aug 19 13:33:56 2020 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #581748 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

 

Also how do I check my IP to make sure the VPN is working?

Link to comment
4 minutes ago, Fatmonk8 said:

Anyone know why I am getting the error?

 

 

Also how do I check my IP to make sure the VPN is working?

I personally haven't seen that error message before. Odd.

To check your IP you can do the following:

  1. Open the console of the Container
  2. Enter execute the following command to install curl:
    1. apt update && apt -y install curl
  3. After that run this command:
    1. curl ifconfig.me
  4. This will return the IP used to connect to ifconfig.me
    1. Check the IP of you home connection by going to https://ifconfig.me/
    2. If the IP of you home connection and the container match, the VPN is not working. If they are different it should be working.
      1. If you get a timeout or unreachable error, your VPN is not working
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.