Kuusou

I'm setting up a new container, but the default account doesn't work. Is there a reason for this, or was it changed?

Unraid allowed me to take everything I was doing haphazardly across a few machines and seamlessly integrate it all into a single box, with a method of expansion and support not available elsewhere. I don't see myself using anything else for my home server setup, and have plans for future upgrades and even new Unraid boxes in the future. One thing I think we're missing is a proper file management solution within the UI. I currently have to utilize at least three 3rd party solutions to quickly move files around within the environment, while handling permissions. This is, in my opinion, something that should be a solid user friendly part of the Unraid experience, but currently isn't.

Woops, didn't realize what logs were which. It seems your update fixed the white screen for me though. My issue now is that changing the two given webui ports to the port I want seems to keep the 8080 port involvement, and then not let me access the webui anymore. If I just use 8080 it works fine. is there something else I need to edit here that I cant see? qbittorrent.log Edit: I was reading up on the other qBittorrent dockers and they seem to have the same issue. It might be a limitation of some kind. Let me know if you work around it. I'd love to change the port. Edit2: I'm unable to tunnel Radarr and Sonarr through the docker to use as a.. proxy.. for my proxy.., which I currently do with my other torrent client. Is there a workaround for this, or something I need to enable/do differently? Or would you simply recommend doing it a different way if I'd like to utilize this container from now on? Also I wanted to thank you for creating, working on, and updating/fixing this container. I had been waiting for someone to do so for a while, and even looked into options for doing it myself, but have little experience with dockers in unraid, so having a ready, or mostly ready option is just beautiful.

+1 I'm currently utilizing the Krusader docker , as well as CA Config Editor for this task and would really love a built in file manager/editor with permissions available.

Currently the Docker Containers are sorted by "Application" which puts them in alphabetical order. This isn't exactly a problem, but I'd personally like to be able to sort this by "Auto-Start", leaving my infrequently used containers at the bottom of my list, especially when not actually in use, and have it stay that way on reload. I'm certain others would like to do the same, or even sort by "Version" so that dockers with updates can be placed at the top of the list (for those who like to do their updates manually) or even the ability to sort by "Auto-Start" and then "Version" allowing for both scenarios to be in play at once. It's maybe a tad superfluous, but sometimes it's the little things with the UI that make the experience that much better overall.

I attached the log for you. Thanks for the quick help. qBittLog.txt

I'd really like to use qBittorrent over Deluge, but I'm having a bunch of trouble with this docker. My initial issue was: Options error: Unrecognized option or missing or extra parameter(s) in [CMD-LINE]:1: config (2.4.4) Which I fixed by just taking the spaces out of the .ovpn file. Good to know for future reference I guess. Sadly after that frustration was over, the docker loads, with only warnings about the way passwords are being stored, but the Web UI won't work. Currently it's just a blank page no matter how I attempt to access it. Typing it in, bookmarking it, or attempting to use the "webui" function in Unraid, which I figured I'd give a shot since.. whatever. Either way it spits out the same blank page. The docker also still seems to input/output on 8080, even though I've changed it to 8114: -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 OUTPUT -o eth0 -p tcp -m tcp --dport 8080 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT I thought maybe the port was locked in another docker setting, so I stopped the docker using 8080, reloaded qBittorrent 8080 as its set port, but again, just a white page. ... As a side question, I wanted to ask if there was any interest or plans to change the docker to act more like binhex's where all of the VPN settings are done within the container setup, instead of afterwards? Not exactly important, but something I personally like about his dockers, and would like to see. And are there issues stemming from this webui situation that make this docker incompatible with Sonarr/Radarr, etc? I'd hate to fuss with this thing so much, finally get it working, and then find out I can't link anything to it.