-
Notifications
You must be signed in to change notification settings - Fork 94
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
Old version. #170
Comments
+1. I'm looking forward to the "block certain extensions" functionality so I can auto-block those pesky .lnk malwares... |
That’s EXACTLY what led me here and to post that. Lol. |
Yea, looking at the main page, this developer hasn't updated in 3 years. Might be abandoned. I changed my docker image over to one maintained by "dyonr". Very easy, just changed 'markusmcnuggen' to 'dyonr' in my docker compose. All other configs stayed the same. Uses the latest qbittorrent version. FYI... |
Yeah I saw that it had been a while and decided to post in case the developer decides to hop back on. I’m gonna look into the one you said but I have a synology server that is running this. I used this guide to get it all set up: https://www.blackvoid.club/qbittorrent-via-vpn-docker-container-running-on-synology-nas/ and thought it would be easier if the image gets updated but don’t know how easy it would be changing to the one you said. Hopefully it’s easier than I think. Lol |
I just set it all up and it's up and running with the torrents I was seeding on the client. I was afraid I was going to lose what I had in there. I added *.lnk |
BTW, and in hopes of helping anyone else, I tried the dyonr image on a synology on DSM-7 but there seems to be an issue on DSM 7 and even QNAP about the iptables. Trigus42/alpine-qbittorrentvpn#52. I had to revert to using the original container as it seems right now that we cannot update past that on DSM 7. |
I also tried the dyonr version but it didn't work got issues with dev/tun not existing and then another issue this is the only one that worked |
I'm currently running v4.3.8 Web while there is a v4.6.7 desktop version out. Will this be updated soon?
The text was updated successfully, but these errors were encountered: