Jump to content
linuxserver.io

[Support] Linuxserver.io - Qbittorrent

152 posts in this topic Last Reply

Recommended Posts

1 hour ago, WantACookie said:

Hey guys. I'm having an issue getting port mappings to work properly. I have my pfsense box routing all traffic through my VPN service based on IP, however my VPN only forwards a specific port for me and it's not the default 6881. If I change the port in the docker settings from 6881 to the port I need it to run on, when the docker starts, the port mappings still show 6881 as the port. Can't figure out how to change this. Any help would be appreciated. Thanks!

Post your docker run command.  Link in my sig or in the docker faq

Share this post


Link to post

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='qBittorrent' --net='eth1' --ip='192.168.0.13' -e TZ="America/New_York" -e HOST_OS="unRAID" -e 'TCP_PORT_6881'='16830' -e 'UDP_PORT_6881'='16830' -e 'TCP_PORT_8080'='8080' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/Media/':'/downloads':'rw' -v '/mnt/user/system/appdata/qbittorrent':'/config':'rw' 'linuxserver/qbittorrent' 

Share this post


Link to post

You've changed the port on the docker side, you should change the port on the host side and leave the docker port alone.

Sent from my Mi A1 using Tapatalk

Share this post


Link to post
24 minutes ago, CHBMB said:

You've changed the port on the docker side, you should change the port on the host side and leave the docker port alone.

Sent from my Mi A1 using Tapatalk
 

Thanks for the help. I'm new to unRAID and Docker in general, could you explain how I change the port on the host side?

Share this post


Link to post
1 hour ago, CHBMB said:

You've changed the port on the docker side, you should change the port on the host side and leave the docker port alone.

Could be wrong (usually am), but isn't he assigning the container to a specific IP, which implies it now runs in HOST mode, and ports are unaffected?

1 hour ago, WantACookie said:

Thanks for the help. I'm new to unRAID and Docker in general, could you explain how I change the port on the host side?

If you need to change the ports the app runs on, then switch the network mode back to bridge, which will allow you to change the host side.  What you've got is the app running on a separate IP address which means that it's port settings are law, and cannot be changed (ie: change the environment variables you've changed for port settings back to their default values).

 

TLDR: When assigning a container to a specific IP, you cannot change the port assignments

Share this post


Link to post
1 hour ago, Squid said:

Could be wrong (usually am), but isn't he assigning the container to a specific IP, which implies it now runs in HOST mode, and ports are unaffected?

If you need to change the ports the app runs on, then switch the network mode back to bridge, which will allow you to change the host side.  What you've got is the app running on a separate IP address which means that it's port settings are law, and cannot be changed (ie: change the environment variables you've changed for port settings back to their default values).

 

TLDR: When assigning a container to a specific IP, you cannot change the port assignments

Oh I did not know that's how it should be done. I wanted all my Dockers on separate IPs and separate NICs so I have them all set up as custom. If I set them all to BRIDGE they will all have the same IP as the machine itself? Thanks for your help.

Share this post


Link to post
Oh I did not know that's how it should be done. I wanted all my Dockers on separate IPs and separate NICs so I have them all set up as custom. If I set them all to BRIDGE they will all have the same IP as the machine itself? Thanks for your help.
It's not that there's a correct way to do it. It's all how you want to do it. Myself I don't see why you need to have separate IPs for my use case. Yours may be different if you are trying to limit bandwidth via pfsense

Sent from my LG-D852 using Tapatalk

Share this post


Link to post
18 hours ago, Squid said:

Could be wrong (usually am), but isn't he assigning the container to a specific IP, which implies it now runs in HOST mode, and ports are unaffected?

If you need to change the ports the app runs on, then switch the network mode back to bridge, which will allow you to change the host side.  What you've got is the app running on a separate IP address which means that it's port settings are law, and cannot be changed (ie: change the environment variables you've changed for port settings back to their default values).

 

TLDR: When assigning a container to a specific IP, you cannot change the port assignments

Yeah, sorry about that, I should have looked closer, was just heading out the door and hastily replied.  Sorry @WantACookie

Share this post


Link to post
1 minute ago, CHBMB said:

Yeah, sorry about that, I should have looked closer, was just heading out the door and hastily replied.  Sorry @WantACookie

No need to apologize, I appreciate the help. I need to figure out a solution to this.

 

16 hours ago, Squid said:

It's not that there's a correct way to do it. It's all how you want to do it. Myself I don't see why you need to have separate IPs for my use case. Yours may be different if you are trying to limit bandwidth via pfsense

Sent from my LG-D852 using Tapatalk
 

It's not that I'm limiting bandwidth, I'm just using pfsense to route all traffic for a specific IP through my VPN. So the qBittorrent docker needs to be on a separate IP, but also use the port I want. Is there any way I can achieve this?

Share this post


Link to post
23 hours ago, WantACookie said:

No need to apologize, I appreciate the help. I need to figure out a solution to this.

 

It's not that I'm limiting bandwidth, I'm just using pfsense to route all traffic for a specific IP through my VPN. So the qBittorrent docker needs to be on a separate IP, but also use the port I want. Is there any way I can achieve this?

 

 

I think you may be able to change the port by looking at 

 

/config/qBittorrent/qBittorrent.conf

and specifically the line 

 

Connection\PortRangeMin=6881

 

Share this post


Link to post
10 hours ago, sparklyballs said:

 

 

I think you may be able to change the port by looking at 

 


/config/qBittorrent/qBittorrent.conf

and specifically the line 

 


Connection\PortRangeMin=6881

 

Thanks for the help. I just checked that out and it's already set to my specified port. But still shows 6881 in the port mappings. This is really driving me insane.

Share this post


Link to post
53 minutes ago, WantACookie said:

Thanks for the help. I just checked that out and it's already set to my specified port. But still shows 6881 in the port mappings. This is really driving me insane.

 

Ignore what it says in the webui, afaik it's just parsing that from the template.  In host mode it doesn't make a difference anyway

Share this post


Link to post

Updated this docker and experiencing lots of problems now. WebUI shows speeds as 'udnefined', and lots of stuff (eg, torrent name, size, etc) are all blank. 

Removed the docker/reinstalled, Tried again with additional step of deleting all appdata for qbittorrent, problem persists... Not sure what else to do. 

Share this post


Link to post
2 hours ago, ct1996 said:

Updated this docker and experiencing lots of problems now. WebUI shows speeds as 'udnefined', and lots of stuff (eg, torrent name, size, etc) are all blank. 

Removed the docker/reinstalled, Tried again with additional step of deleting all appdata for qbittorrent, problem persists... Not sure what else to do. 

screenshots from latest version of this image...l

Screenshot 2018-09-26 at 02.20.50.png

Screenshot 2018-09-26 at 02.20.59.png

Screenshot 2018-09-26 at 02.21.29.png

Screenshot 2018-09-26 at 02.21.36.png

Screenshot 2018-09-26 at 02.21.43.png

Screenshot 2018-09-26 at 02.21.56.png

Share this post


Link to post

Just updated the docker and all my torrents are gone and the UI is completely messed up.

 

EDIT: Turns it it was a browser issue. Deleted the cache and everythings back to normal now.

 

Edited by Outcasst

Share this post


Link to post

anyone can help me with running a unrar script, 

 

i was running

 

find /qbit-downloads/ -name '*.rar' -execdir unrar e -o- {}

 

and it would unrar into the directory properly using a different docker but since I moved to this one it doesn't recognize the -execdir command for find. if anyone can help that would be awesome

Share this post


Link to post

I can't set the watched folder, I input /mnt/user/Media/Dropbox/Blackhole/ but it wont save.

 

Any help would be appreciated

 

Cheers Marvel

Share this post


Link to post

Was having the Error Unknown problem too.  Logs said the file sizes weren't matching, so I manually renamed my incoming folder.  It started working again, so I added the files back into the newly created incoming folder.  For whatever reason so of them seems to crash this new version of qbittorrent.  I don't have much there so don't mind starting over.

 

You might want to empty your log folder, it's probably pretty big now.

Share this post


Link to post

Morning. I'm just moving to qbitdocker from a vm (to free up some overheads.)

I've got the docker installed and running. With VPN off I can open the webui and am presented with the login screen, if I enable the VPN setting I get connection refused, but it looks like the VPN is connecting ok, this is from my log:

 

 

2018-10-30 12:13:47.524216 [info] VPN_ENABLED defined as 'yes'
2018-10-30 12:13:47.545426 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/Netherlands-Amsterdam-TCP.ovpn
dos2unix: converting file /config/openvpn/Netherlands-Amsterdam-TCP.ovpn to Unix format...
2018-10-30 12:13:47.563242 [info] VPN remote line defined as 'nl1-ovpn-tcp.pointtoserver.com 80'
2018-10-30 12:13:47.577025 [info] VPN_REMOTE defined as 'nl1-ovpn-tcp.pointtoserver.com'
2018-10-30 12:13:47.590801 [info] VPN_PORT defined as '80'
2018-10-30 12:13:47.604599 [info] VPN_PROTOCOL defined as 'tcp'
2018-10-30 12:13:47.618544 [info] VPN_DEVICE_TYPE defined as 'tun0'
2018-10-30 12:13:47.632245 [info] LAN_NETWORK defined as '192.168.10.0/24'
2018-10-30 12:13:47.646542 [info] NAME_SERVERS defined as '8.8.8.8,8.8.4.4'
2018-10-30 12:13:47.660380 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2018-10-30 12:13:47.674485 [info] Adding 8.8.8.8 to resolv.conf
2018-10-30 12:13:47.688371 [info] Adding 8.8.4.4 to resolv.conf
2018-10-30 12:13:47.702022 [info] Starting OpenVPN...
Tue Oct 30 12:13:47 2018 WARNING: file 'Wdc.key' is group or others accessible
Tue Oct 30 12:13:47 2018 WARNING: file 'credentials.conf' is group or others accessible
Tue Oct 30 12:13:47 2018 OpenVPN 2.4.4 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Sep 5 2018
Tue Oct 30 12:13:47 2018 library versions: OpenSSL 1.1.0g 2 Nov 2017, LZO 2.08
Tue Oct 30 12:13:47 2018 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Tue Oct 30 12:13:47 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]213.x.x.x:80
Tue Oct 30 12:13:47 2018 Attempting to establish TCP connection with [AF_INET]213.x.x.x:80 [nonblock]
Tue Oct 30 12:13:48 2018 TCP connection established with [AF_INET]213.x.x.x:80
Tue Oct 30 12:13:48 2018 TCP_CLIENT link local: (not bound)
Tue Oct 30 12:13:48 2018 TCP_CLIENT link remote: [AF_INET]213.x.x.x:80
Tue Oct 30 12:13:48 2018 WARNING: Bad encapsulated packet length from peer (18516), which must be > 0 and <= 1626 -- please ensure that --tun-mtu or --link-mtu is equal on both peers -- this condition could also indicate a possible active attack on the TCP link -- [Attempting restart...]
Tue Oct 30 12:13:48 2018 Connection reset, restarting [0]
Tue Oct 30 12:13:48 2018 SIGUSR1[soft,connection-reset] received, process restarting
Tue Oct 30 12:13:53 2018 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Tue Oct 30 12:13:53 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]213.x.x.x:80
Tue Oct 30 12:13:53 2018 Attempting to establish TCP connection with [AF_INET]213.x.x.x:80 [nonblock]
Tue Oct 30 12:13:54 2018 TCP connection established with [AF_INET]213.x.x.x:80
Tue Oct 30 12:13:54 2018 TCP_CLIENT link local: (not bound)
Tue Oct 30 12:13:54 2018 TCP_CLIENT link remote: [AF_INET]213.x.x.x:80

Also tried using a different endpoint:

Tue Oct 30 13:10:40 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]172.x.x.x:80
Tue Oct 30 13:10:40 2018 Attempting to establish TCP connection with [AF_INET]172.x.x.x:80 [nonblock]
Tue Oct 30 13:10:41 2018 TCP connection established with [AF_INET]172.x.x.x:80
Tue Oct 30 13:10:41 2018 TCP_CLIENT link local: (not bound)
Tue Oct 30 13:10:41 2018 TCP_CLIENT link remote: [AF_INET]172.x.x.x:80
Tue Oct 30 13:11:41 2018 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)

Tue Oct 30 13:11:41 2018 TLS Error: TLS handshake failed

Tue Oct 30 13:11:41 2018 Fatal TLS error (check_tls_errors_co), restarting

Tue Oct 30 13:11:41 2018 SIGUSR1[soft,tls-error] received, process restarting

Tue Oct 30 13:11:51 2018 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.

Tue Oct 30 13:11:51 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]172.x.x.x:80
Tue Oct 30 13:11:51 2018 Attempting to establish TCP connection with [AF_INET]172.x.x.x:80 [nonblock]
Tue Oct 30 13:11:52 2018 TCP connection established with [AF_INET]172.x.x.x:80
Tue Oct 30 13:11:52 2018 TCP_CLIENT link local: (not bound)
Tue Oct 30 13:11:52 2018 TCP_CLIENT link remote: [AF_INET]172.x.x.x:80
Tue Oct 30 13:11:54 2018 WARNING: Bad encapsulated packet length from peer (18516), which must be > 0 and <= 1626 -- please ensure that --tun-mtu or --link-mtu is equal on both peers -- this condition could also indicate a possible active attack on the TCP link -- [Attempting restart...]

Tue Oct 30 13:11:54 2018 Connection reset, restarting [0]
Tue Oct 30 13:11:54 2018 SIGUSR1[soft,connection-reset] received, process restarting
Tue Oct 30 13:12:14 2018 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.

Tue Oct 30 13:12:15 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]172.x.x.x:80
Tue Oct 30 13:12:15 2018 Attempting to establish TCP connection with [AF_INET]172.x.x.x:80 [nonblock]
Tue Oct 30 13:12:16 2018 TCP connection established with [AF_INET]172.x.x.x:80
Tue Oct 30 13:12:16 2018 TCP_CLIENT link local: (not bound)
Tue Oct 30 13:12:16 2018 TCP_CLIENT link remote: [AF_INET]172.x.x.x:80
Tue Oct 30 13:12:16 2018 TCP connection established with [AF_INET]172.x.x.x:80
Tue Oct 30 13:12:16 2018 TCP_CLIENT link local: (not bound)
Tue Oct 30 13:12:16 2018 TCP_CLIENT link remote: [AF_INET]172.x.x.x:80
Tue Oct 30 13:12:30 2018 WARNING: Bad encapsulated packet length from peer (18516), which must be > 0 and <= 1626 -- please ensure that --tun-mtu or --link-mtu is equal on both peers -- this condition could also indicate a possible active attack on the TCP link -- [Attempting restart...]

Tue Oct 30 13:12:30 2018 Connection reset, restarting [0]
Tue Oct 30 13:12:30 2018 SIGUSR1[soft,connection-reset] received, process restarting

 

Edited by karldonteljames

Share this post


Link to post

Not to worry. I spoke to purevpn and it turns out that they had the wrongs files on their website!!! i got the latest certificate and the latest server details and it started working!! Thanks for your help though!

Share this post


Link to post

Just tried to install this. With default ports and bridge mode I got a error page trying to load the web interface for the container, just the regular old can't find the web page error.

 

I noticed that the log shows port 8080 but the container template is set to map 8082 container to 8082 host. I deleted that and add my own for container 8080 and host 8082. Now the web interface loads but its just a white page with nothing on it. Not sure if I did anything wrong or the template is broken.

Share this post


Link to post
1 hour ago, Dimtar said:

Just tried to install this. With default ports and bridge mode I got a error page trying to load the web interface for the container, just the regular old can't find the web page error.

 

I noticed that the log shows port 8080 but the container template is set to map 8082 container to 8082 host. I deleted that and add my own for container 8080 and host 8082. Now the web interface loads but its just a white page with nothing on it. Not sure if I did anything wrong or the template is broken.

Question:  When you edit the template does it state for repository mace/qbittorent or linuxserver/qbittorent?

 

Just went to test your problem, and a regression error in CA wound up under this circumstance that it would always pull mace instead of linuxserver.  Pumping out an update to CA right now.

Share this post


Link to post

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.