Can't connect to qBittorrent

[dasbootbee]

Discussed in #589

^{Originally posted by Izumiko August 27, 2022}
flood works fine with qbittorrent-nox 4.4.3.1, but when I upgraded to the latest version 4.4.4, it reports "Cannot connect to the client". Has anyone ever had the same problem?

[mouzzampk2014]

Everyone having this issue

[dasbootbee]

I did a search for qBittorrent in open issues and didn't find anything. Sorry if I made a dupe. For anyone having the issue, using qBittorrent 4.4.3 (or pulling an image with that tag) allows Flood to function again.

[mouzzampk2014]

Yes you are right 4.4.3 works fine. I think there are some API changes in newer version broke the flood connectivity.

I don't think its dupe so might be good idea to leave this open

[GuyKh]

Seeing the following in hte logs:

Error
    at t.default.updateAuthCookie (/usr/local/lib/node_modules/@jesec/flood/dist/index.js:3:1072292)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

[xXx-st4cktr4c3-xXx]

@jesec looks like 4.4.4 changed enforcement for HTTP methods, mainly to POST.

qbittorrent/qBittorrent@10d75e2
qbittorrent/qBittorrent@d6c9270

Can this be quickly updated since switching to POST for those methods shouldn't cause any issues with previous versions.

Thank you!

[GH0STREAP3R]

Any ETA when this will be fixed when using the latest qbittorrent version?

[Nedlinin]

Any ETA when this will be fixed when using the latest qbittorrent version?

This should be fixed on master. Need @jesec to cut a new release for most automated builders to build new images.

[mrhotio]

@jesec Could you make us a new release? Pretty please...

[runaroundhome]

For docker users you can use image: jesec/flood:master in docker compose to pull the latest changes. (which do work with qbt v4.4.5, just tested it)

[Hecsall]

For npm users, I managed to get everything working by installing the master branch version following the instructions found on the npm page

Installation
...

Or use @jesec/flood for cutting-edge builds.

A quick npm install @jesec/flood, and everything is working again.
Hope this helps

[GH0STREAP3R]

@jesec Could you make us a new release? Pretty please...

@jesec Any chance you could fulfill this request sometime soon please :)

[sammcj]

Any update on a release @jesec ?

[Jarsky]

Any update on a release @jesec ?

Since we havent seen any progress on this, i've compiled the binaries and put them here:
https://github.com/Jarsky/flood-releases/releases/tag/v4.7.0b

Just copy the flood-linux-x64 into your qflood docker container, rename it to flood, and change permissions.
e.g

docker stop qflood
wget https://github.com/Jarsky/flood-releases/releases/download/v4.7.0b/flood-linux-x64
chmod 777 flood-linux-x64
docker cp ~/flood-linux-x64 qflood:app/flood
docker start qflood

It should then work.

[GGG-KILLER]

Any update on a release @jesec ?

Since we havent seen any progress on this, i've compiled the binaries and put them here:
https://github.com/Jarsky/flood-releases/releases/tag/v4.7.0b

Just copy the flood-linux-x64 into your qflood docker container, rename it to flood, and change permissions.
e.g

docker stop qflood
wget https://github.com/Jarsky/flood-releases/releases/download/v4.7.0b/flood-linux-x64
chmod 777 flood-linux-x64
docker cp ~/flood-linux-x64 qflood/app/flood
docker start qflood

It should then work.

For this the docker image jesec/flood:master can be used.
And for npm, @jesec/flood can be used as well.

[Jarsky]

Any update on a release @jesec ?

Since we havent seen any progress on this, i've compiled the binaries and put them here:
https://github.com/Jarsky/flood-releases/releases/tag/v4.7.0b
Just copy the flood-linux-x64 into your qflood docker container, rename it to flood, and change permissions.
e.g

docker stop qflood
wget https://github.com/Jarsky/flood-releases/releases/download/v4.7.0b/flood-linux-x64
chmod 777 flood-linux-x64
docker cp ~/flood-linux-x64 qflood/app/flood
docker start qflood

It should then work.

For this the docker image jesec/flood:master can be used. And for npm, @jesec/flood can be used as well.

Yeah hes using qflood docker though, which uses the latest release (@jesec/flood/releases/latest). It combines qBittorrent & Flood into a single container. I was just providing one already compiled if he wants the binary

[S-n-d]

@jesec pretty please?

[lazerleif]

Any update on a release @jesec ?

Since we havent seen any progress on this, i've compiled the binaries and put them here: https://github.com/Jarsky/flood-releases/releases/tag/v4.7.0b

Just copy the flood-linux-x64 into your qflood docker container, rename it to flood, and change permissions. e.g

docker stop qflood
wget https://github.com/Jarsky/flood-releases/releases/download/v4.7.0b/flood-linux-x64
chmod 777 flood-linux-x64
docker cp ~/flood-linux-x64 qflood:app/flood
docker start qflood

It should then work.

Thank you so much! This works for me. Has tried for two hours to get my qflood working without success, until now 😄

[spyhuntergenral]

i'm guessing this project is abandoned? @jesec

[GH0STREAP3R]

i'm guessing this project is abandoned? @jesec

Sure would be nice to see him cut a new release, its been just about 7 months since it stopped working :\

[Jarsky]

i'm guessing this project is abandoned? @jesec

Sure would be nice to see him cut a new release, its been just about 7 months since it stopped working :\

I already compiled the fixed binaries, which you can get from the link below compiled back in December.....

Any update on a release @jesec ?

Since we havent seen any progress on this, i've compiled the binaries and put them here: https://github.com/Jarsky/flood-releases/releases/tag/v4.7.0b
Just copy the flood-linux-x64 into your qflood docker container, rename it to flood, and change permissions. e.g

docker stop qflood
wget https://github.com/Jarsky/flood-releases/releases/download/v4.7.0b/flood-linux-x64
chmod 777 flood-linux-x64
docker cp ~/flood-linux-x64 qflood:app/flood
docker start qflood

It should then work.

Thank you so much! This works for me. Has tried for two hours to get my qflood working without success, until now 😄

[GH0STREAP3R]

I already compiled the fixed binaries, which you can get from the link below compiled back in December.....

I seen and appreciate that, but it would be nice for him to cut a new updated release for people that use qflood images from other people like mrhotio without having to do your fix in case something messes up in the future.

[hausner]

ed binaries, which you can get from the link below compiled back in December.....

A

Managed to get up to latest release because of this fix - thanks.

Cant believe the project is abandoned. This is the best UI i have seen so far for qbittorrent.
Anyone know of any other active mobile UI friendly projects?

[brezinajn]

ed binaries, which you can get from the link below compiled back in December.....

A

Managed to get up to latest release because of this fix - thanks.

Cant believe the project is abandoned. This is the best UI i have seen so far for qbittorrent. Anyone know of any other active mobile UI friendly projects?

vueTorrent

[Arelav]

I guess it's time to stay on ghcr.io/hotio/qflood:release-8c5d56f if using docker-compose until I'll decide to move into another webUI

[jeffbyrnes]

For docker users you can use image: jesec/flood:master in docker compose to pull the latest changes. (which do work with qbt v4.4.5, just tested it)

For anyone coming here nowadays like I just did, this is the fix if you’re running Flood using the jesec/flood image.

[hausner]

i can recommend switching to Vuetorrent by WDaan (if thats allowed).

[Swazib0y]

Wondering if anyone can recommend a fix for a non docker install? I have installed via the PPA on ubuntu. Tnx

[Jarsky]

Wondering if anyone can recommend a fix for a non docker install? I have installed via the PPA on ubuntu. Tnx

Refer my comment above for a link to the fixed binaries. You can just overwrite the binary with the appropriate one (linux x64)
Its typically it will be in /etc/bin or /usr/bin.

[Monoboy4ik]

another trouble... cant add torrent via flood (qbit 4.6.4)
i can see in docker logs 2024-04-25T11:12:29.884007530Z POST /api/torrents/add-files 403 6.231 ms - 47 , maybe api has changed

[cgobat]

@trim21, are you able to cut releases? It seems like @jesec has abandoned this project...

[trim21]

@trim21, are you able to cut releases? It seems like @jesec has abandoned this project...

I'm not familiar with this issue, is this already fixed in master branch?

[cgobat]

Yeah, the fix has been on master since September 2022

[trim21]

OK, I'll prepare a release these days

[trim21]

please install latest flood 4.8.0

[kertzi]

Well, now looks like flood doesn't work with latest qbittorrent (5.0.3).

This is what I can see in flood log:

Jan 10 08:48:06 tunkio flood-linux-x64[678247]: Error
Jan 10 08:48:06 tunkio flood-linux-x64[678247]:     at ClientRequestManager2.updateConnection (/snapshot/flood/server/services/qBittorrent/clientRequestManager.ts:104:13)
Jan 10 08:48:06 tunkio flood-linux-x64[678247]:     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Jan 10 08:48:07 tunkio flood-linux-x64[678247]: PATCH /api/auth/users/kertzi 200 34.641 ms - 2
Jan 10 08:48:08 tunkio flood-linux-x64[678247]: GET /api/client/connection-test 500 1005.733 ms - 21
Jan 10 08:48:54 tunkio flood-linux-x64[678247]: GET /api/activity-stream 200 8.305 ms - -

So looks like GET call to /api/client/connection-test gets HTTP 500 so that's most likely the problem but not sure where I can find actual reason for this "internal server error code".

[trim21]

what flood version are you using？ try latest

[kertzi]

what flood version are you using？ try latest

ah, sorry forgot to mention. I'm using latest, 4.8.5
This is new setup.