Closed ghost closed 6 years ago
It's probable that the version you're using of qBittorrent isn't compatible with the version I implemented against. qBittorrent was definitely one of the worse when it came to APIs so I wouldn't be surprised.
@Qata yeah I remember they added quite a bit of CORS protection in 3.3.13, that broke things for API users and people reverse proxying like me, so that's likely the cause here too :/
@qauff Are you okay with just switching to Deluge? Honestly it was just a pain to implement support for qBittorrent in the first place so I might remove it if it's now broken.
@Qata Hm.. I could do that yeah. I'd prefer not to cause I do have deluge set up for something else. I suppose I could have two deluges, might be tricky!! But doable. No biggie if qBittorrent is too much of a pain. I get it, they change a lot!
@Qata qBittorrent changes were mostly about authentication and some data formatting, merge my pull request #41 ?
Closed via #41
my server is running qBittorrent 3.3.16 and deluge 1.3.12 (I've got an NGINX reverse proxy providing HTTPS access to both). BarMagnet works with my deluge set up, but not qBittorrent. BarMagnet throws the error: "Unable to authenticate. No error info provided, are you sure that's the right port?" I'm 100% certain it's the right port.
Here's a screenshot of the error.
the Open UI button shows the correct URL:
Open UI
Any ideas what could be wrong, or what I could try to make this work?