Long time Vuze torrenter switching to qBittorrent.
I’ve successfully started downloading a TV show via a search using the 1337 plugin so no firewall issues.
In the connection options I set it to use my VPN connection and I see the globe icon in the status bar switch between red and green when I stop and start the VPN. So it looks like I binded to it properly.
I also have the VPN kill switch enabled.
I’m fairly sure I’ve done all I need to do but would like to know if there’s another step I might be missing. Is there a test I can do to be sure I’m fully VPN routing for all things qBittorrent?
You can check using ipleak, they have a empty torrent which checks your IP, then disconnect the VPN, it should be dead if binded, if not then it’ll show your real IP
Well, I don’t know wtf was going on there. I decided (for no apparent reason) to try a different torrent - an old episode of family guy that 1337 said had over a thousand seeders and THAT ONE WORKED. That was going through Ethernet. So naturally I stopped it, closed qB, fired up the VPN with kill switch and restarted qB and it wouldn’t work again. I did a whatismyipaddress in the browser and it said I was in Sweden (despite my VPN saying it was setting me to UK), so I chose another city in the UK which did report properly. Connected to it and then the torrent started going with no intervention.
Conclusions ?
Ignore the fire icon, it’s not necessarily as bad as it seems despite the mouseover tooltip info it shows
Try a different torrent
Try a different country on the VPN
Another thread on here says try clicking on the port randomizer in the options
Really not sure which of those was the key. What I definitely know though is that I’m now pretty much configured the same way I was before and now its working.
Update: Well, I did see it working as shown in the screenshot. I just went back to it after 10 minutes and it’s stalled, still at 0.7%. Maybe I got over-excited there. It does seem that 99% of the seeders aren’t showing up though. I guess the three working trackers I have there aren’t very useful.
Is it normal to see a view like that, where most trackers timeout or have some other error?
Thanks for the reply. I did try that yesterday and it did respond in that way. It certainly looked good, I just wanted to make sure I was 100% covered on all fronts. Good to know about the searching bypassing the VPN, but that’s familiar. I always used to go to magnetdl and copy the magnet links and paste them into Vuze. So it’s not a downgrade, it’s still an upgrade being able to get results from 1337 without having to visit their malware-ridden website
Unfortunately, today when I wanted to try again I’m stuck with the fire icon in the status bar and despite trying to download something with > 1000 seeds, I get nothing. I had that situation for a while yesterday too, but as soon as I tried to download something it all changed and I got the green globe. Not this time though.
It’s StrongVPN, used it for over a decade and never had any issues from torrenting, although I do only ever torrent TV shows. It’s not even a relevant factor right now though, I’ve set qB to use Ethernet and turned off the VPN (and its kill switch) and still stuck with a very active torrent that won’t get going.
qB is running on a Windows 11 virtualbox VM with a Windows 11 host. It worked on Wednesday going through the VPN. So all the network, vpn, qB, malwarebytes, and firewall settings were all good. Tried again Thursday after having only shutdown the VM and restarted it, and nothing - torrents won’t start.
Tried ubuntu download as suggested by D0_stack. Well there’s a revelation. My burny burny icon went to green and trackers look good, download started immediately with a decent speed. It really does seem like 1337 torrent links are somehow not up to scratch.
Well I use NordVPN and to bind it to QBit since Im on Wifi I bind it to the NordLynx protocol, then for IP adds I bind to the Ip that starts with 10.XX.XX.XX and it works for me.
I can’t get rid of that fire icon no matter what I do. Even unbinding and disconnecting the VPN and setting qB to use direct Ethernet. Firewall is set to allow qB through on private and public networks. I made the tragic mistake of shutting the machine down while it was working perfectly and then starting it up the next day. Foolish to expect it to still work I know. Giving up for now, too much of a time sink.
Interesting. I did notice yesterday it was all orange and burny and then I started a download (an old episode of the simpsons) and it went green. Tried the same thing today with a 1000+ seeder episode of the simpsons and it never got going. It kept saying 1 seed despite the 1337 search saying it was over a thousand. Maybe tomorrow it’ll be better. If it does work again, I’ll be backing up that vdi file for safekeeping
