• Announcements

    • Bommuraj Paramaraj

      Important Security Advisory   06/07/2016

      On June 6th, 2016, BitTorrent was made aware of a security issue involving the vendor which powers our forums.
      The vulnerability appears to have been through one of the vendor’s other clients, however it allowed attackers to access some information on other accounts. As a result, attackers were able to download a list of our forum users. We are investigating further to learn if any other information was accessed.Our vendor has made backend changes so that the hashes in the file do not appear to be a usable attack vector. As a precaution, we are advising our users to change their passwords. While the passwords may not be used as a vector on the forums, those hashed passwords should be considered compromised. Anyone using the same password for forums as well as other places is strongly advised to update their passwords and/or practice good personal security practices.


Established Members
  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About AnthonyB

  • Rank
  1. Yes - Adguard I disabled it and was able to successfully register and connect remotely. Re-enabled Adguard and put in an exclusion to not filter utorrent.exe and it seems to still be stable. Many thanks! Perhaps this should be documented or even mentioned in the uTorrent -> Preferences -> Remote setup page?
  2. I'm using UT 3.4.9 beta (build 43223) [32-bit] on Windows 10 For many months now, whenever I try and enable uTorrent Remote Access in the app I simply get "Status: Not accessible" and it goes into a loop of delay and re-trying. No connection issues reported in UT client itself (green tick bottom right corner in status bar). Does Remote work in the beta builds? if so, what can I check or troubleshooting can I do to try and determine the issue? Thanks in advance.
  3. Links fixed. To be honest' date=' I don't think this will help if a new (empty) settings file doesn't.[/quote'] I agree. Thus my belief that this is a bug given all the other data I've presented
  4. Actually, I was going to try yours from your sig yesterday but the redirect link is broken. If you could fix that then I'll definitely give it a go.
  5. Sorry, missed that. I'm not force seeding any torrents. As originally mentioned, this just started happening about 2 weeks ago with no change at my end aside from installing whatever beta builds were auto-updated so at this stage I'm more inclined to think this is a regression introduced in whatever build was released around 2 weeks ago.
  6. Just renamed the settings.dat/old to create fresh ones to test. Exact same behaviour being exhibited.
  7. For the last 2 weeks, I've found the beta builds have been uploading at my maximum upload rate even when in the scheduler it is in the White (i.e. "Turn Off") time period. It's not displaying in the main window that it's uploading anything and all active torrents show a Status of Queued. However, on the uTorrent title bar and status bar it is showing *something* uploading and my router logs show upload data at the same rate. I'm currently on 3.2.27272. Any ideas what might have happened from the builds around 2 weeks ago to cause this? Is this a bug or have a missed a new configuration option? I've made no config changes in months, simply accepted new beta builds of 3.2.x as they get pushed.
  8. For reference, still seeing exact same issue with Beta 25229
  9. Yep, been getting the same ever since upgrading to uTorrent 3.0 beta 25220. have to keep forcing re-check. When the torrent EVENTUALLY downloads it's perfectlly OK. Would love to know the cause of this as it's insanely annoying.