Torguard public ip detection failed torrent#I just realized that I also sometimes do the "remote" procedure while in the house but using my cellphone over the home WiFi, which is finding a torrent URL and passing it through Transdrone to Deluge. Yes, the only torrent client I ever use is Deluge on my home network server. Is my 30-second check interval often enough for my IP not to be seen?ĭoes just pausing torrents in Deluge remove them from the Peer list that other peers see?Īnd of course, is there a way to handle all this? Is better than a hard-wired Torguard server IP address? When the status shows "Tracker Status: 34.204.227.31: Error: Connection timed out" but it's still downloading, is it still actually using the proxy? Is the problem really that the Proxy is "disconnecting"? So, lots of things I don't know for sure: IOW, I don't think my kill switch is very useful at the moment. Torguard public ip detection failed download#HOWEVER, I don't really believe that my real IP has to be shown in the tracker status for the download to be using it, and making me visible. The script sends me a txt message so I know to look at Deluge to see what's going on. I don't know if that's good enough to stop my visibility to peers so I actually halt the server which removes the process entirely. I initially thought I'd pause all torrents in Deluge. If my script finds my IP address, I figure the proxy has disconnected. If I don't find my real IP address I know it's working. My simple kill switch therefore runs in a cron job every 30 seconds, gets the check torrent info with "deluge-console info 0975cf2f18db055ef67f87651637e0da366e9877" and scans it for my real IP address. I believe I've occasionally seen my real IP address on the STATUS tab of the "Check My Torrent IP Tool" in Deluge, and I assume it's because the proxy disconnects. It seems there is no kill switch for proxy use, so I wrote a simple one yesterday. After a couple of minutes the torrent checker status changes back to "34.204.227.31: Error: Success, TorGuard Netherlands Socks5 Proxy Connected." So, something a bit flaky in Deluge in that it can't detect the proxy disconnecting, but can detect it becoming active? So it seems the active Deluge doesn't detect the proxy down? The odd thing is that if I change the fake IP address back to in the running Deluge (without stop/restart), after less than a minute it starts downloading again. BUT, if I exit and restart Deluge and it's daemon, THEN it won't download, and the checker status is now shows "34.204.227.31: Error: Connection timed out". I did a test and changed to 123.123.123.123 and downloading continued and the checker still said "Netherlands Socks5 Proxy Connected". "34.204.227.31: Error: Success, TorGuard Netherlands Socks5 Proxy Connected."īut downloading always continues. "Tracker Status: 34.204.227.31: Error: Connection timed out", or Typically the torrent checker status shows one of the following: After that first ISP warning last year, I may have thought that a hardwired IP might disconnect more often? Or, I may have thought that with the host name, if the proxy died it would switch to another and continue downloading instead of stopping altogether. For the first 4 years I had used a particular host address from the long list online, but I changed it to "" last year. My Deluge Proxy config has Socks5 W/Auth, my username/pswd, and port 1085 for Peer, Web Seed, Tracker, and DHT. Am I right, that the proxy can occasionally disconnect? (I did read several Topics here in the forum about this.) My theory is that the proxy is disconnecting but Deluge (v1.3.13 running on Linux) keeps downloading. It wasn't until last year that I got my first copyright warning from my ISP, but then I got 1 a week ago and 9 more yesterday. Another reason for the switch to a proxy was that I run a mail server on my desktop and even with help from Torguard Support, it would be complicated to use the VPN, such as installing DD-Wrt on my router, adding firewall rules, etc (if I understood it at the time). Initially I bought a VPN but decided I didn't want the whole house to suffer the performance (my wife often works from home) so I switched to a proxy. I've been running Torguard proxy for 5 years now.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |