"Torrent not added! Maybe exists." - doh, I'm trying to cross seed it, of course it exists...any resolution?

[cleverestx]

I'm getting "Torrent not added! Maybe exists." - this is for OPS and RED only so far (my only music trackers) - Is any resolution possible for this?

EX:

Torrent: [ Music ] Christie Front Drive - Christie Front Drive (1996) [FLAC]
Searching: Christie Front Drive Christie Front Drive 1996
2 matched of 23 results.
Grabbing release: Christie Front Drive - Christie Front Drive [1996] [Album] [Remastered 2010] [FLAC Lossless] [CD] [Cue]
Torrent not added! Maybe exists.
Grabbing release: Christie Front Drive - Christie Front Drive [1996] [Album] [FLAC Lossless] [CD] [Cue]
Torrent not added! Maybe exists.

[Investigamer]

Having the same issue here unfortunately, many matches but always results in "Torrent not added!" (using trackers Milkie, TorrentLeech, ReelFlix, FearNoPeer, and MAM).

[NelsonDane]

Same issue here

[kearkan]

I'm seeing the same issue, just set up with qbit and prowlarr and seeing this same error across Milkie, FearNoPeer, digitalcore and some others.

[swannie-eire]

I'm seeing the same issue, just set up with qbit and prowlarr and seeing this same error across Milkie, FearNoPeer, digitalcore and some others.

Many of those trackers have the same torrent with just there own tracker announce.

Download each of the the torrents and confirm they have different info hashes using something like torf

[kearkan]

Many of those trackers have the same torrent with just there own tracker announce.

Does that mean the best way to cross seed these is to add the trackers to the torrent manually? Set qbittorrent to add all trackers to all torrents? I'm not sure of how to achieve cross-seeding in these situations.

On closer inspection it actually looks like the one that seedcross is finding is the originally downloaded torrent.

[Mapzle]

I had the same issue, but I managed to fix it.
After checking the qb client log, I noticed that the download link was being sent directly to the Jackett configuration link. Since it was on a different host, "http://127.0.0.1:9117/" couldn’t be resolved. Switching to the public IP address worked perfectly.