Torrent client not showing seeders

[twinkerzzz]

When i go to my profile > torrent leeching > neither of the 2 torrents that are being problematic are shown to be present at all which seems very odd.
All my other 10 leeching torrents are present and correct including two unconnected (0 seeder) indications.
Nor are the problematic torrents present in the 'torrents seeding' list which i would expect anyway as they have 0% completion and are technically still leaching torrents.

SO with regards checking the URL announce address is there another way i can do this ? Also to verify - i think you mean by check the URL announce address - make sure the URL announce address shown in the bittorrent client trackers box (see attachment) matches the URL tracker announce URL….. - im sorry but i am having difficulty understanding where else the tracker announce URL for individual torrents can be seen or located to double check this information. Please advise or screen cap location for me.

I've screen capped the Tracker URLs as shown in my bittorrent client for each of the rogue torrents:
screen cap 1:
menonedge - The one and only Logan McCree
screen cap 2:
Toby Ross: Classic Porn Collection (1977 - 1991)

The two torrents are not queued. btw. They should both be active. I restarted the bittorrent but no change.

thanks for your attention
:blink:
tzz

[Popper]

Yes, I meant the tracker URL in the pictures. I've compared it with your Profile's information and it looks to be correct.
(The pictures are removed, because the URL contains your personal secrete passkey)

The http 404 error is very strange here, because it is a feedback from the server (tracker) that the requested information is not found …

However, torrent works fine for me, including the tracker URL with your passkey. So it must be something on your side or between the tracker and you. Still I've no idea what it could be.

Please try to reboot the computer (not just standby and on again) to clear all caches.

Can you please try to change the .tw in the tracker URL to .ru ?

[twinkerzzz]

ok - thanks for taking care of the URL check.

I'll keep an eye on this thread meantime to see if any more feedback / advice occurs re: the 404 error or other suggestions - It's a bit out of my league technically….

thanks meanwhile.....
:crazy2:
tzz

[Popper]

Can you please try the two things proposed: reboot and changing the URL from .tw into .ru (in the torrents properties)

[twinkerzzz]

@Popper:

Can you please try the two things proposed: reboot and changing the URL from .tw into .ru (in the torrents properties)

did reboot - no change
changed .tw to .ru - no change

more info:
the toby ross torrent was loaded into the bitorrent client on saturday btw
the Logan Mccree was loaded today.
I generally shut down and reboot and end / start of each day…......

..... :afr2:

[Popper]

Can you remove one of the torrents from your BitTorrent and re-download it from GayTorrent.ru and then add it again?

[twinkerzzz]

hi P - thanks for baring with me

yes - ive done that with both torrents at some point today - removed and redownloaded the torrent - no change when they are added to the bitorrent client - it starts off saying status off line but then reverts to error 404. I was wondering if you had tried downloading the torrents in question and if you get the same problem or is it just me….?

tzzz :blownose:

[Popper]

Yes, I have. See one of my earlier posts, including with your passkey (so it is not your account being restricted).

Are you using a proxy service by coincidence?

[twinkerzzz]

I dont think so - im not sure what a proxy service is - i just have a router and internet supply…..

twzz

[metafile]

I have always had that 404 error message. However, it's never interfered with my ability to upload/seed or download/leech. I don't know if that helps narrow down the problem, but I've always just ignored that error.

[Popper]

That are "Scrape" errors. Our tracker got the scrape support deactivated. Therefore, that error is "normal" fr all torrents which are stopped or queued. µTorrent shows another error message in that case, something like "scrape not allowed", not http 404 (http 404 is what you see in Transmission for example).

The solutions are multiple:

• just wait the torrent to start as you do
• change the queuing priority settings so it starts
• force start

The emphasis is on start, our tracker delivers detailed peer information once a torrent is started.

This should not be the issue of the topic opener …

[twinkerzzz]

Pooper is correct - as previously mentioned all my leeching torrents are active and none need force starting or are indicated as 'queued' which is usually clearly visible in the progress bar and easily changed by force-starting. So that's not been a solution here.  Also i don't know what a 'scrape' is but i don't have that word showing in any of the screen caps i've put up.

tzz

[twinkerzzz]

its been a week now - no change on these 2 torrents - just thought i would check in to see if nay new trouble-shoot ideas had brewed…...

:cheesy2: :blownose: :blind:

[Popper]

Are you using multiple torrent client programmes?

[twinkerzzz]

no im not - do you think it's worth trying another torrent client ? Might that make the difference ? I'm using BitTorrent V.7.6.1 - a client which ive used for years…...

[twinkerzzz]

so im going to take up your suggestion and install a new bittorent client.

I can't find any rules on banned bittorrent clients but just in case -  i was thinking of trying one of:
Tixati
QBittorent
Mediaget
Azureus/Vuze (which i've tried before but didnt really like)

Could you tell me if any of these bittorent clients are banned by this site ?

thanks for your time….
twzzz

[Popper]

What about just updating your BitTorrent to a resent stable built?

Out of your list, qBittorrent has been tested by staff on Mac, GNU/Linus and Windows (Vista) to work well.

[twinkerzzz]

cool - the Bittorrent client update has solved the issue . i guess i should have thought about that earlier…..

thanks for your troubleshooting and guidance -

:cheers:
twzzz

[Popper]

Thanks for the feedback. Good to know the solution in case other members have such an issue.