Cross-seeding of torrents with same hash values in ruTorrent (help?)

[despatch45]

Hi guys I have a dedicated seedbox and using ruTorrent. In ruTorrent is too easy to cross seed if the torrent has different hash values or there are additional files/missing files then it does it automatically.

The issue I was having was that I could easily cross-seed to two trackers with no issues (both torrents had different hash values and one or two files were missing) but when I try to add the third tracker the log says "file successfully added" but it doesnt show up as a separate torrent. After a bit of googling I found out it was due to the files being exactly same and the torrent having same hash values.

My questions is there a simple way to cross-seed torrents from different trackers with ruTorrent in seedbox with torrents having same hash values?

[GTC]

No.
If I recall correctly if the files have different piece sizes rtorrent will load them separately, however this is not helpful for your scenario

[despatch45]

hmm i guess there is no way around then :(

[AcidBath]

I banged my head on the wall for a while on this, and no, you cannot load the same torrent with identical hashes.
You COULD re-hash the torrent yourself and leave the NFO out or something, then load that torrent file.
You could also run Deluge, Transmission, etc, and use that to load duplicate torrents.

[S0Ulk33p3r]

Might seem like a silly thing to try but I have no problem cross-seeding to 3 or 4 trackers, really the only thing I can think of if your are following the proper procedure for cross-seeding, what I would suggest is try labeling your torrents to allow a distinction between them, other then than I don`t see what you would be doing differently then me, I`m using Rutorrent 3.5. Try that, I would be very interested to see why you are unable to do this. Let me know and I`ll see if theres something that I`m doing different that makes more sense then this outlandish idea

[Nojus]

I have the same problem too on torrents that are private, unprivate and private torrents run good (1 private 1 non private).

[viola12]

For same hash there seems no way around it in rTorrent. Some people suggest running 2 instances of rTorrent.

[pyroscope]

There is no way around it in ANY client, what µT does is FOLD duplicates into the existing item, which is a no-no for private sites.

[silverfish]

I have struggled with this too. In the end I ran another instance of rTorrent. I wish there was a better solution!

[baztard]

Is this something a private tracker would potentially implement a rule to fix if requested or would they rather you not "outside seed" like this? I have two trackers that are frequently using the exact same hash. I'd love to seed both, but this prevents me from doing it without manual intervention. From what I've read, simply requiring that every torrent has a small tracker.txt file or really anything different and recalculating the hash would fix the issue.

[r0tt0r]

I also came across this problem and a manual solution in ruTorrent is to go to [ Trackers ] in the selected .torrent details and disable all but one tracker. This way, the other one takes over.