flood
flood copied to clipboard
Connection could not be verified. - qBittorrent v4.5.0 Web UI (64-bit)
Discussed in https://github.com/jesec/flood/discussions/628
Originally posted by IamTheKingKong January 27, 2023 I run Flood on the same docker network (Synology server) as qBittorrent but for some reason, I can't connect to it. I've tried all localhost IPs but still nothing.
Any ideas?
Same here
+1
+1
+1
+1
+1
+1
+1
Compiling from master works with the latest qBittorrent release, or deploy jesec/flood:master
.
Compiling from master works with the latest qBittorrent release, or deploy
jesec/flood:master
.
The issue is some downstream consumers deploy only based on stable releases, so this is not a universal solution. Unfortunately it seems this project became unmaintained. So I don't see this being resolved in the near future.
Does anyone have the latest nightly? It was here before, but not available anymore.
EDIT:
Fixed it myself, it's here: https://github.com/enoch85/flood/releases/tag/master-20230405. You're welcome!
same issue, since this does not seem to be fixed anytime soon, any recommendations for another webui for qbittorrent?
using WSL for @enoch85 's release works perfectly for me. It's a shame this repo is inactive, i love the UI compared to vuetorrent
I created a "nightly" Docker image fork of hotio's rflood image, that automatically updates flood with each push to the master branch. It's a minor change to the original image.
It basically takes the most recent successful run of this workflow, grabs the id, forwards it to the Dockerfile, and then downloads the release from that run.
Simple, but effective, and it should be automatically updated with the upstream flood and qbittorrent.
Link: https://github.com/vp-en/qflood
FYI 'jesec/flood:master-distroless' works fine. No need for a bundle with qbit or anything.
https://hub.docker.com/r/jesec/flood/tags
I created a "nightly" Docker image fork of hotio's rflood image, that automatically updates flood with each push to the master branch. It's a minor change to the original image.
It basically takes the most recent successful run of this workflow, grabs the id, forwards it to the Dockerfile, and then downloads the release from that run.
Simple, but effective, and it should be automatically updated with the upstream flood and qbittorrent.
Link: https://github.com/vp-en/qflood
Moved it to https://github.com/engels74/qflood
just made a new release 4.8.0