Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

qBittorrent-git (4.2.0alpha) Login failure #159

Closed
aTosser opened this issue Jul 22, 2019 · 9 comments
Closed

qBittorrent-git (4.2.0alpha) Login failure #159

aTosser opened this issue Jul 22, 2019 · 9 comments

Comments

@aTosser
Copy link

aTosser commented Jul 22, 2019

I am testing out qbittorrent-git and they have changed the API again. I get login failures now in electorrent. I can still log in fine at the webUI so.
Just a heads up.

Settings Error Error: Invalid login
at QBittorrent.<anonymous> (/tmp/.mount_electojW…torrent/index.js:93)
at Request._callback (/tmp/.mount_electojW…torrent/index.js:68)
at Request.self.callback (/tmp/.mount_electojW…uest/request.js:185)
at Request.emit (events.js:182)
at Request.<anonymous> (/tmp/.mount_electojW…est/request.js:1161)
at Request.emit (events.js:182)
at IncomingMessage.<anonymous> (/tmp/.mount_electojW…est/request.js:1083)
at Object.onceWrapper (events.js:273)
at IncomingMessage.emit (events.js:187)
at endReadableNT (_stream_readable.js:1092)

@tympanix
Copy link
Owner

tympanix commented Jul 22, 2019

Thank you for informing about this. It looks like we have to update qbittorent yet again. Keeping backwards compatibility will be harder and harder though. For now use an older version of qbittorrent

@aTosser
Copy link
Author

aTosser commented Oct 15, 2019

@tympanix Heads up it seems (according to the github milestones for qbittorrent) that they are planning to relese 4.2.0 in the next week-ish... May be time to take a poke at this.

The /api/v2/ prefix that you are aware of is becoming the default and the legacy API is going to be dropped from 4.2.0+

The login method has been moved to /api/v2/auth/login

It also seems some methods have been changed some, I noticed while browsing the code deletePerm no longer exists and deleteFiles is now a parameter passed to delete so there may be a couple of hiccups along the way.

Let me know if you need some testing, we can sit down and hammer it out if you have the time.

Weeeeeee....

@olympia
Copy link

olympia commented Dec 7, 2019

More and more repos and channels are providing qBittorrent v4.2.0 now and due to the above, Electorrent is not usable as from this version. Could you please look at the upgrade?

@tympanix
Copy link
Owner

tympanix commented Dec 7, 2019

An upgrade is surely necessary. Sadly, I don't have the resources to implement this feature as of right now. 😢 This will however be my top priority when I can allocate time for this project.

@AnanyaKirti
Copy link

could you tell me what needs to be done? Maybe I can help

@tympanix
Copy link
Owner

@AnanyaKirti we need an updated implementation of node-qbittorrent which is a dependency of Electorrent. Backwards compatibility with older versions would be desirable.

@icex
Copy link

icex commented Dec 19, 2019

@tympanix - see my quick patch https://github.com/icex/node-qbittorrent/commit/83eab5184be72e8c5eb690d780b15fcaa2b25b03

No backward compatibility, all I could do in a few hours(I have zero experience in Angular and Electron, sorry).

@aTosser
Copy link
Author

aTosser commented Dec 28, 2019

honestly with icex's patch we could just rename node-qbittorrent to node-legacy-qbittorrent and either make a new menu entry or some conditional voodoo for auto-detection.

@roncamma
Copy link

Woawh pretty cool !:) 💟

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants