Thread: "utorrent problem" cannot upload to libtorrent

i am facing a strange problem
utorrent simply refuses to upload anything to libtorrent seedboxes (even when i am the uploader and only seed)
the libtorrent peers get connected but it simply do not upload anything to the seedbox
uploads to deluge seedboxes normally
utorrent 2.2.1



any help appreciated

edit- solved automatically

I am having a very similar problem with utorrent 3.0.
No upload to libtorrent seedbox even if I'm the only seeder and there's one libtorrent leecher...

Edit:
On the same torrent, I'm maxing my up speed with deluge though.

Bump, anyone ?

Can you just not connect to some libtorrent peers or to all of them?
Some users, including myself, have set rtorrent up to force encrypted traffic, which means only peers who allow encryption can connect to you.
Maybe that's the problem and you both don't allow encrypted traffic OR it's the other way round and the other libtorrent users only allow normal traffic.

Adding on Magisters advice. You can also do this utorrent.


1. Go to: Options > Preferences > BitTorrent
2. Go to ‘Protocol encryption’, you can choose between ‘enabled’ and ‘forced’. ‘Enabled’ will give you more connections but offers less protection against traffic shapers.
I would recommend to try ‘enabled’ first, if that doesn’t work, try to swich to ‘forced’.
3. Ticking ‘Allow legacy incoming connections’ allows non ecrypted clients to connect to you. This improves compatibility between clients but makes you more vulnerable to traffic shapers.
I would recommend to tick this box, but if that doesn’t connect you, untick it!

From utorrent help file (F1).

Protocol Encryption

• The Outgoing dropdown menu allows you to select the mode of encryption that you prefer µTorrent to establish. All modes will accept incoming encrypted connections, and the encryption is 2-way.
  
  • Disabled will force µTorrent to attempt to establish only unencrypted outgoing connections.
  • Enabled will allow µTorrent to establish encrypted and unencrypted outgoing connections, depending on how the peer responds to the handshake. This option provides µTorrent with the largest pool of peers to pick from for connecting to, but incurs additional overhead that may often be unnecessary in most typical situations.
  • Forced forces µTorrent to establish only encrypted outgoing connections. Any peer that doesn't support encryption will not be connected to. It is recommended that you not use this option unless your ISP actively searches for unencrypted outgoing connections, as it can impair your ability to connect to peers.
• Allow incoming legacy connections allows µTorrent to accept unencrypted incoming connections. If disabled, any incoming connection that is unencrypted will be ignored. It is recommended that you not disable this option unless your ISP actively searches for unencrypted incoming connections, as it can significantly impair your ability to connect to peers.

On utorrent (3.0), I'm running forced encryption with the legacy connections disabled.
On Deluge (1.3.3) I'm running forced inbound and outbound encryption + full stream level and encrypt entire stream enabled.

I tried to change utorrent settings as Kyllah suggested but it didn't work.
I also tried to disable the encryption settings on deluge and I still maxed my up speed to the same libtorrent seedbox.

I think it's safe to assume this problem has nothing to do with encryption settings.

Magister, I viewed the peers I'm connected to for about an hour, I didn't see any libtorrent peers, it could be just a coincidence though.
I'm seeding about 300 torrents btw.

Thanks guys.

Edit: I tried to download something that libtorrent seedbox is seeding and I did get connected and downloading (with utorrent). I'm buffled...

I can't really tell you what the problem was, maybe it was just coincidence and you just weren't connected to libtorrent peers when you were watching.
When you have the connection set to force encryption you can't connect to users that only allow normal transfers.

The way the bittorrent protocol works is that it favors peers with greter potential, aka with a faster connection. It may have been the reason for this phenomaen.

Overall, I'm glad that it's resolved at least for LibChamp.

Um the problem was uploading to libtorrent, not downloading. I'm still unable to seed with utorrent to libtorrent users...

Maybe changing the version of utorrent will fix this ?
Can I simply downgrade or upgrade it while keeping all of my torrents as they were ?

I thought the problem was connecting overall, but it applies the same, because the bittorrent proctocol favors faster connections, which can cause ta problem.
When you are the only seed it's still possible that encrypts can be the problem or that the torrent isn't set to private, because that's mandatory with private trackers.

I don't think that changing the utorrent version will make any difference, because don_rocks had the same problem, but a different utorrent version.