For some odd reason, I am not able to see the list of active/completed downloads in the qBittorrent client and I’m just curious if anyone has had this issue before? At this point i don’t really know where to look to fix this. I got into docker a week ago, so maybe I’m missing something important?
The above text is what i was initially going to post on here. Now I’m posting here because I’m curious if this is a known issue and what can be done about it.
What i did to resolve this was changing the default port of 8080 to 8100. I would love to hear if this is known to everyone or im just silly. If not, this is probably something that needs to be investigated further as to why.
As you can see from the first image when it is listening for http requests at 8080, for some reason it is not able to fetch the torrents that are currently downloading. I have been able to confirm this since i am using homepage.dev dashboard where i can see active downloads. I’m yapping again. The point of this post is to let new users know about this possible issue.
For future reference, all you need to do is:
change the http listening port from 8080 to 8100 (or any other port).
Change the environment variable from 8080 to 8100, like so: WEBUI_PORT=8100
Stop the 1 container you have running and see if the other one stays online.
The qbittorrent container is currently on port 8100. After stopping it, i tested the default port 8080 without success.
Side note we don’t support/recommend portainer
Yeah, I’ve seen that in a few threads. I stopped using that a week ago after running into some issues myself, i just use it to get a brief overview of the containers. I started learning docker compose and have stuck with it since
If you want some support, put it back on the default ports as noted in the container readme, provide your docker compose snippet, the full logs beginning with our ascii logo (use a bin service), and the output of uname -mr && docker version
nah thats okay, i’ve spent enough time on this. Although, the whole reason for this post was to save other users some time if they bumped into the same issue. I did a search beforehand but there were no similiar cases like mine.
I’m sure i could re-open this at a later time if i absolutely have to use port 8080. Thanks for the assist anyways.
