Hi,

I'm trying to cross-seed (both accept it) 2 same torrents from 2 different private trackers. I'm using ruTorrent to manage downloads on my seedbox.

When the first torrent is loaded and finished, when I try add the second one... nothing happens.

When I manually try to add the second one and tick "random hash", it's added, verified and then... red cross "unregistered torrent" and no upload is possible

I made a little digging on the forum, no real solutions. I hope I can find one today.

Thanks in advance for your help.
T.

Hi Tsoert. I cant say I have a good answer to this, but have you tried installing Deluge and adding the torrent file there instead? It may work, as otherwise RuTorrent just thinks you are trying to add the same torrent a second time in my experience. If anyone has a definitive answer to this I'd be curious to hear it though.

Hi @multipack, thanks for your answer.
Do you mean simultaneously use Deluge and ruTorrent?
If yes, I'm afraid the contractual terms of my seedbox's provider stipulate not to use two torrent clients at the same time.

Yeah Deluge and RuTorrent running simultaneously should work. Do you mean your seedbox provider doesn't allow more than one client? Hmm..

Originally Posted by multipack

Yeah Deluge and RuTorrent running simultaneously should work. Do you mean your seedbox provider doesn't allow more than one client? Hmm..

Exactly.

I have never had a company tell me not to. Ok I may not have ever combed the ToS but I have run Deluge (from my desktop) alongside the RuTorrent web GUI with lots of providers and nobody has ever said a word. Where does it say it? Are you sure? I'd change providers.

Hi @multipack,

Well... it seems that the two torrents I want to cross-seed from different private trackers have the same HASH. That's why they can't be added simultaneously.
Which is a shame really because it shows that some uploaders upload the EXACT torrent with the EXACT Hash, perhaps to avoid cross-seeding (but apparently it's allowed on most private trackers) or because to much of a hassle to change the HASH codes for each tracker.

Not that I blame them totally, they do a great job, I just wonder why some HASH are the same and some are not.

Finally I guess you're right, I should use two different torrent clients. But this is what my provider says :
https://support.seedboxes.cc/Frequen...e-slot-allowed

Any idea?
Thanks
T.

Yeah I realise it's the same hash, but it's strange because the announce would be wrong if you just uploaded the exact same file. I don't really understand how they do that, although I realise that's the problem, and quite often it occurs with files from sister sites (like IPT and TD etc) so the uploaders must be being lazy but I don't quite get how? :/

You aren't wrong about the terms of service either. Can't see anything about it in this one so maybe the only answer would be to switch providers https://www.seedhost.eu/terms-of-service.php

Am sure there must be a way to get around the problem, but the fact no one else has answered suggests no one else knows either!

Best answer so far from a TD user:

That's correct.

The hash will be the same though when the files are exactly the same & the piece size is the same, which is why they can be the same on different trackers. This is set when the torrent file is created and isn't something you have any control over, that's why there is no user solution.

One solution is one or both trackers could add a tracker specific file to the filelist (e.g. a 'torrentday.txt' file with the word 'torrentday' in it), this would work because each torrent would ignore the extra files not associated with it and would cause the torrents to have different hashes. You would have to convince one or both trackers to implement this feature. This wouldn't be too hard for human uploaders to implement, but I'm not sure how hard it would be to add the file on bot added torrents.

I don't think that's right though, because I regularly seed 10+ versions of the same file from various sites without any issue, and the announce is embedded in the torrent file. The hash is random and the chances of it being identical is slim. I think.