Hi,
Since updating to qbittorrent v3.3.13, I am unable to send to webui. I think something has changed in webui. Authentication is fine i have tested it, changed it and verified it by logging into the webui.
Branch/Commit: master/10a0c3012e600ed61cdff6a6108b2bb55062907b
OS: Windows 10
What you did: Manual search eposide to transfer via webui to qbitorrent
What happened: torrent not send to qbitorrent webui
What you expected: torrent send to qbitorrent webui
Logs: https://pastebin.com/pJUPeimj
https://github.com/qbittorrent/qBittorrent/commit/087856d3d8d6d77881c3d8378a95d80d693af2dd
This was implemented around that version.
We need to account for that change... I'll look into that, but I don't use qBT.
Tested, and the fix works.
Could you please push this fix to master branch? I am awaiting for this fix...
In the meantime you can switch to the develop branch in the advanced settings.
on /config/general/

Downside: you get this warning on all pages for the time being

@jabbink This fix has not been pushed to the develop branch either! Did you test on the devlop branch?
It has been on develop since 4 days ago: https://github.com/SickRage/SickRage/commit/be0c5eaac12d5736c49e9a54edb4b4cd5b260720

Issue is with qBitTorrent 3.3.13, downgrading to .12 fixed the issue
https://sourceforge.net/projects/qbittorrent/files/qbittorrent-win32/qbittorrent-3.3.12/
.14 is in the works to resolve this issue.
downgrading from 3.3.13 to 3.3.12 did it for me.. now my downloads are once again working
Again, upgrading SickRage would also work, which was the easier method for me as it's a matter of switching the branch/commithash of sickrage and restarting, instead of downgrading qBittorrent which requires more work.
@jabbink While I agree,
I guess some people find it easier than changing the branch on SickRage (you need to login with your Github credentials in SR)
Hmm, I never logged into either SickRage with my GH credentials, nor would you need credentials to clone a repository (specific branch/commit hash/anything public) when you chose https as protocol manually via the git cli tool.
You can do whatever you like with the git cli, but to checkout a different branch from within SickRage, you need to set your GH credentials (to get develop branch) or enable developer in config.ini (to get all branches).
REF: https://github.com/SickRage/SickRage/blob/96b53dee713dc35ebf295d0f37a67b2a36fb4ea3/gui/slick/views/config_general.mako#L1089-L1102
Any update on when this will make it to master?
much thanks,
~Raze42
I would also like to know. I would love to switch back to the master branch.
@miigotu Maybe you should just hotfix/cherry-pick it into master.
@Raze42 @Firedrake1 Also waiting on this to make it to master.
I've been using develop, but now downloaded episodes aren't showing anymore under develop.
Have to downgrade QBT and switch back to master in order to be able to see my dl'ed episodes and have auto-snatching work.
Master:

Develop:

@mickloud This has nothing to do with qBT. It's probably something we did in the last few days. Thanks for posting this, I'll look into it.
Edit: To be clear, I'm also experiencing this (not using qBT).
It's 100% qBT's issue. https://github.com/qbittorrent/qBittorrent/pull/6887
@procdaddy11 I was referring to the issue that downloaded episodes are no longer visible in SickRage. This has nothing to do with qBT.
The original issue discussed here was definitely caused by qBT.
@sharkykh Oh I know that episode display issue I just pasted doesn't have to do anything with qBT, I was just saying that I had switched to develop to skirt around the qBT issue for now, and this new issue popped up. I've been following this thread, but didn't mean to conflate them. I realized I wasn't clear -- I meant to say downgrade qBT and switch back to master. Anyway.. thanks for looking into it!