Open CWarder opened 1 year ago
I've noticed this issue (with regards to the adding of a torrent) - but this only occurs when I'm using the standalone server option, which I'm assuming is similar to @CWarder. If I simply utilize iQbit as an alternate web UI (in the traditional sense), everything works fine.
@CWarder - is your docker container also running qbittorent?
I've had the same issue, none of the buttons actually worked. I recieved all of the incoming data, but couldn't interact with the server. I come with the idea to that if GET requests are OK, but POST requests are not then problem lying in communication with the servers communications, (thanks to my experience working with back- + frontend apps) my first thought was Cross-Site Request Forgery (CSRF)
. I tried to fix it from iQbit server side, but with no luck. Then in qBittorrent -> options -> Web UI tab
I found option to disable it. Unchecked it and everything started to response from iQbit standalone server.
I will update readme later when I investigate this issue more. Mb it's possible to fix without unchecking this functionality
cc @chippewaChris @CWarder
I'm using it in a docker, specifically from haruvon/iqbit.
When opening the new torrent dialog and placing a torrent link or file, when hitting the add torrent button nothing happens. The dialog box remains open and no torrent is added.
Separate issue, for some reason iqbit isnt requiring any authentication to access. Just auto logs in, bypassing the webui credentials.