Application Name: Qbittorrent

Application Site: https://www.qbittorrent.org

Docker: https://hub.docker.com/r/linuxserver/qbittorrent/

Github: https://github.com/linuxserver/docker-qbittorrent/

 

Please post any questions/issues relating to this docker you have in this thread.

 

The default username/password for the webui is admin/adminadmin

 

If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support.

Edited September 14, 20186 yr by linuxserver.io
wrong link

When I open the webUI - all I get is a blank page, with literally nothing on it. 

 

 

Edited August 15, 20177 yr by shEiD

2 hours ago, shEiD said:

When I open the webUI - all I get is a blank page, with literally nothing on it. 

The lsio guys are going to ask you for this

 

https://forums.lime-technology.com/topic/57181-real-docker-faq/#comment-564345

 

@Squid thanks for reminding me, added the screens.

I was getting the blank page as well. It looks like this container doesn't like having the default webui port changed. Setting the host port 3 parameter to anything other than 8080 produces the white page.

@impalerware thanks. Changing back the port to 8080 worked.

 

Although 8080 is quite popular port among the containers, isn't it? Hope nothing else will that hell-bent on keeping 8080

 

Another weird thing - even after changin back to 8080 the webUI works only in Firefox and only in Chrome Incognito mode. It still gives me a blank page in regular Chrome.

On 16/08/2017 at 2:15 AM, shEiD said:

@impalerware ...the webUI works only in Firefox and only in Chrome Incognito mode. It still gives me a blank page in regular Chrome.

Probably worthless advice, but have you cleared the cache?

Probably worthless advice, but have you cleared the cache?

Nope, exactly what I'd suggest.

Sent from my LG-H815 using Tapatalk

Same issue I have SAB running on 8080 tried another port and got white page.

Sent from my SM-G930F using Tapatalk

Also getting the blank screen in chrome but working in incognito. Clearing cache logged me out of every website i frequent but didn't help haha 

 

 

The port seems to change back every time I change the web port from 8080 to 8081.  Do you know what I am doing wrong.

On 9/27/2017 at 6:19 AM, superderpbro said:

Also getting the blank screen in chrome but working in incognito. Clearing cache logged me out of every website i frequent but didn't help haha 

 

 

 

I figured this out.

 

Allow popups on the site in your browser and it will load the interface. I'm not sure how it loads as a popup, but it's working lol

Edited October 4, 20177 yr by Quiks

On 10/2/2017 at 3:55 PM, Altek86 said:

The port seems to change back every time I change the web port from 8080 to 8081.  Do you know what I am doing wrong.

Are you changing it in the Qbt WEBUI settings or the container?

 

Edit: I found I had the same issue as you, but was able to figure it out. With the base settings, any time you change the port in the QBT interface, it will reset to 8080 when rebooting the docker.

 

To fix this, you need 2 changes from the default config.

 

Remove the original 8080:8080 port map

 

create a new one 6666:6666 (whatever your new port is)

add a new variable

Key: WEBUI_PORT

Value: 6666 (again, whatever your new port is)

 

apply this and your UI should now work on the new port.

 

However, clicking WEBUI on your docker in the UnRaid UI will yield a webpage opening with :8080 which won't load. I'm still trying to figure out how to change the default webpage since it seems hardcoded to 8080.

 

Hopefully this helps you or anyone else trying to change their port!

 

edit: I figured out that I had the view on basic. Switched it to advanced, and I can change the default launch URL as well.

 

That should fix all the issues for everyone.

 

Woot!

Edited October 4, 20177 yr by Quiks

12 hours ago, Quiks said:

 

I figured this out.

 

Allow popups on the site in your browser and it will load the interface. I'm not sure how it loads as a popup, but it's working lol

Popups are already allowed

 

EDIT: Hmm.. It works if i manually type in http://192.168.1.2:8080/ .. But not if i access the webui from unraid's webui.

Edited October 4, 20177 yr by superderpbro

18 hours ago, Quiks said:

Are you changing it in the Qbt WEBUI settings or the container?

 

Edit: I found I had the same issue as you, but was able to figure it out. With the base settings, any time you change the port in the QBT interface, it will reset to 8080 when rebooting the docker.

 

To fix this, you need 2 changes from the default config.

 

Remove the original 8080:8080 port map

 

create a new one 6666:6666 (whatever your new port is)

add a new variable

Key: WEBUI_PORT

Value: 6666 (again, whatever your new port is)

 

apply this and your UI should now work on the new port.

 

However, clicking WEBUI on your docker in the UnRaid UI will yield a webpage opening with :8080 which won't load. I'm still trying to figure out how to change the default webpage since it seems hardcoded to 8080.

 

Hopefully this helps you or anyone else trying to change their port!

 

edit: I figured out that I had the view on basic. Switched it to advanced, and I can change the default launch URL as well.

 

That should fix all the issues for everyone.

 

Woot!

It worked beautifully.  you do need to reinstall the app and delete all the data from appdata!

Also you have to add the container port info as well if that wasnt clear enough 6666:6666

 

Thanks Quiks!

 

I wonder if that works with all apps like Sabnzbd.  some issue with that one but no worries for me since I could change one.

Edited October 4, 20177 yr by Altek86

11 hours ago, superderpbro said:

Popups are already allowed

 

EDIT: Hmm.. It works if i manually type in http://192.168.1.2:8080/ .. But not if i access the webui from unraid's webui.

Weird. I can't reproduce that, so I don't think I'll be of help on that one.

 

I did have the exact same symptoms you did (where it works correctly in incognito), and I specifically had to unblock pop-ups on that site before it started working normally.

 

manually "typing it in" working doesn't really make much sense.

 

It's just passing the URL.

 

Try manually editing the URL to what you're typing in on the advanced view and see if it starts working.

 

It does have some PORT:8080 type of syntax by default

 

 

 

 

5 hours ago, Altek86 said:

It worked beautifully.  you do need to reinstall the app and delete all the data from appdata!

Also you have to add the container port info as well if that wasnt clear enough 6666:6666

 

Thanks Quiks!

 

I wonder if that works with all apps like Sabnzbd.  some issue with that one but no worries for me since I could change one.

If I'm understanding correctly, the WEBUI_PORT thing was something specifically added to this container. The main docker page is what led me down the clues to figuring it out. I could be wrong though.

I'm having an issue with the download folder, whenever I download a torrent to move or delete I have to apply permissions to the download folder. This is ofcorse after I stop seeding and remove it from qBittorrent interface. 

 

it's a bit frustrating

Has anyone been able to get a proxy server to work with this?  Im trying to get my torguard proxy working which works with the windows version of qtorrent but the test torrent is never seen hitting torguards server.

 

Edit: I ended up working with torguard and for some reason creating a random login made it work.

Edited February 3, 20187 yr by Ryland

is anyone else having problems with file permissions with this docker?  When I try to delete or move completed files in windows, I can't until I run the docker safe permission tool

16 hours ago, DZMM said:

is anyone else having problems with file permissions with this docker?  When I try to delete or move completed files in windows, I can't until I run the docker safe permission tool

I havent had these issues.

Hi guys, does anyone know how I can set this up to extract completed torrents? I'm used to the "run upon completion" from Windows where I'd use unrar CLI for this, but in a Docker container I dont have a clue where to start. Thanks

2 hours ago, Fredrick said:

Hi guys, does anyone know how I can set this up to extract completed torrents? I'm used to the "run upon completion" from Windows where I'd use unrar CLI for this, but in a Docker container I dont have a clue where to start. Thanks

 

Basically install unrar via the nerdpack plugin, then run command on completion:

 

unrar x "%F/*.r*" "%F/"

 

On 2/10/2018 at 6:11 PM, Fredrick said:

 

Basically install unrar via the nerdpack plugin, then run command on completion:

 

unrar x "%F/*.r*" "%F/"

 

I have installed unrar using nerdpack, but now where I am supposed to write that command? 

 

Do I have to change something? my downloads in qbittorent are in /downloads/

 

Edited March 4, 20187 yr by L0rdRaiden

In the qbittorrent settings "Run external program on torrent completion"