Clarification: I mean - Are the Socks 5 proxy settings not working? The proxy provider says the subscription is activated but all trackers are suddenly "not working" in qbittorrent. I'm seeding 900 torrents. with lots of different trackers.
Socks 5 Proxy settings ignored in 3.1.3
-
Starshine
Socks 5 Proxy settings ignored in 3.1.3
Hi all - is this a known limitation or something? I wish I had known before I shelled out for a 3 month subscription!
Clarification: I mean - Are the Socks 5 proxy settings not working? The proxy provider says the subscription is activated but all trackers are suddenly "not working" in qbittorrent. I'm seeding 900 torrents. with lots of different trackers.
Clarification: I mean - Are the Socks 5 proxy settings not working? The proxy provider says the subscription is activated but all trackers are suddenly "not working" in qbittorrent. I'm seeding 900 torrents. with lots of different trackers.
Last edited by Starshine on Mon Jan 13, 2014 10:33 am, edited 1 time in total.
-
Starshine
Re: Socks 5 Proxy settings ignored in 3.1.3
I added an explanation above.
Trackers are reporting "not working" and there were some previous instances of people reporting problems with qbt using Socks 5 proxies suggesting there was a bug .
Trackers are reporting "not working" and there were some previous instances of people reporting problems with qbt using Socks 5 proxies suggesting there was a bug .
-
ciaobaby
Re: Socks 5 Proxy settings ignored in 3.1.3
Can the listening port be forwarded (for UDP at least) through the proxy? and if so ... Is it?
-
Starshine
Re: Socks 5 Proxy settings ignored in 3.1.3
Hi thanks for responding. Yes port forwarding is set up properly on this machine and is working. The proxy provider is stating that 1080 (VPN port) should be specified for the proxy. That port is opened on the router and the firewall and works fine normally.
The problem with this provider "TorrentPrivacy" and their torrent proxy is that it is only configured to work with uTorrent, Vuze and Bittorrent.
It was so totally unexpected that it took a while until I realised it. I have used BT Guard previously and that is client agnostic - works with anything as long as you configure properly.
I logged a support case with TorrentPrivacy requesting a refund since they had not flagged the limitation on their website - should have been clearly stated that only 3 clients were supported.
They said they will look at adding qbittorrent to their configuration, but I am not willing to wait for that, since my subscription is ticking.
I'm waiting to see now, if they will refund - if not they can expect a few rather bad reviews.
The problem with this provider "TorrentPrivacy" and their torrent proxy is that it is only configured to work with uTorrent, Vuze and Bittorrent.
It was so totally unexpected that it took a while until I realised it. I have used BT Guard previously and that is client agnostic - works with anything as long as you configure properly.
I logged a support case with TorrentPrivacy requesting a refund since they had not flagged the limitation on their website - should have been clearly stated that only 3 clients were supported.
They said they will look at adding qbittorrent to their configuration, but I am not willing to wait for that, since my subscription is ticking.
I'm waiting to see now, if they will refund - if not they can expect a few rather bad reviews.
-
ciaobaby
Re: Socks 5 Proxy settings ignored in 3.1.3
Not port forwarding on your router, but actually across the proxy server.
Have you tried listening on the 'standard' BitTorrent ports (6881 - 6999)?
Personally I have never used a proxy that allowed any BitTorrent client to work without some connectivity problems.
Have you tried listening on the 'standard' BitTorrent ports (6881 - 6999)?
Personally I have never used a proxy that allowed any BitTorrent client to work without some connectivity problems.