tessierp

The service appears to start however, I am unable to access the webui externally. I did a curl on the localhost 8080 and able to see the login page however...

Update on this situation. In my docker-compose.yml, I set both the internal and external ports to 6080 and then deployed the service. The container initially fails once because it is...

Tried the new release.. No change, still can't access the webUI if I map 6080->8080

No can do.. Doesn't work for me from a swarm, ports just wont map at all. The container still reports 8080 even if the service itself by way of the...

I did go in the container to run curl on port 6080 and qbittorrent returned the login page however something is not mapping the ports right but the issue is...

Alright so I confirm this is still broken, no matter what I do I can't access the external ports at all.

Same problem here.. Whenever APIs are being used and depending on how many are used on the dashboard, the CPU usage can jump above 50% usage when the dashboard is...

> It seem little bit absurd that a page with bunch of links is taking so much cpu. I had to stop the container because my server was almost flying...

Hi, that we know. But it shouldn't take as much CPU power as it does.

While what you say is technically true, it should not spike as high as it does. I have way less than that and yet usage spiked to above 47%. This...