Tracker offline?
-
Based on a number of user reports, users who are running Transmission 3.0 are having no end of difficulty with the tracker. […]
When you do try to connect and seed or leech a torrent, is there an error message that you're getting from the tracker, and if so, what is the error message?
I'm back to v. 2.94 and, surprisingly, things look back to normal (crossing fingers…).
I've never had error message per se. But the “announce” process was failing for most torrents:
• sometimes being delayed by 2 hours, again and again;
• sometimes the inspector window showing “announce en cours” (announce waiting) indefinitely.Also, the number of active torrents seen by the site would appear ridiculously low; I'm seeding several hundreds (now 473) but the site would see only a tiny fraction of that.
(The attached picture reflects the back to normal situation.)
-
When you do try to connect and seed or leech a torrent, is there an error message that you're getting from the tracker, and if so, what is the error message?
It just says "Could not connect to tracker"
-
This will connect to the regular tracker, rather than the SSL tracker.
IT WORKED!!! sorry for my english.. so everytime i download a torrent I have to change the tracker?
-
I thought it was an issue on my side! I can seed but download doesn't seem to be working
-
I can download but I can't seed, and I seem to have tried most of the advice in this thread, including disabling the ssl tracker, editing existing torrent trackers to include http://tracker.gaytorrent.tw:2710/ before announce, updating the DNS, rolling back transmission, bouncing around to different VPN endpoints. I'm hoping to be able to get back to seeding/sharing soon
-
Still not working for me. I'm using the updated tracker but with Bigly or Deluge and I have set my dns to google and cloudflare. But all I get is "Error: Timeout". I tried using tunnelbear and that seemed to work, but I generally don't use a vpn. I saw that some ips are being blocked because of the ddos attack. Is there any way to get my ip whitelisted?
nvm tunnelbear nolonger working
…aaaand it worked for a second then stopped working. I changed the tracker to the old url, then back to the new one, and a torrent started downloading, then stopped. I'm just going to assume the issues are persisting and hope they get fixed. Thanks for your hard work! :dick:
-
Still not working for me. Im using a Seedbox and my torrents arent downloading/seeding. I cant change the IP address.
-
same here, been having issues on and off for weeks.
-
On my end it started to work yesterday (TM3 client), now all torrents work fine with the default https://tracker.gaytor.rent/ tracker.
-
Not working here either (qBittorent).
Tried the tips already (also was already using the regular tracker).
-
I'm using Transmission 3.0 and all torrents still say cannot connect to tracker
-
This will connect to the regular tracker, rather than the SSL tracker.
IT WORKED!!! sorry for my english.. so everytime i download a torrent I have to change the tracker?
You can make this change permanent by clicking the "Profile" tab at the top of the page, then disabling the SSL tracker, and saving the changes at the bottom of the page.
-
I'm using Transmission 3.0 and all torrents still say cannot connect to tracker
You may find you have no end of difficulty with Transmission 3.0. You may need to roll back to version 2.94
-
Im using a Seedbox (Pulsedmedia) and my torrents arent downloading/seeding either.
As it's a seedbox I cant change the IP address.
Any ideas? Thanks
I assume you are using rutorrent - if you are go to torrent and then below select tracker tab and you can edit the tracker details
-
Im using a Seedbox (Pulsedmedia) and my torrents arent downloading/seeding either.
As it's a seedbox I cant change the IP address.
Any ideas? Thanks
I assume you are using rutorrent - if you are go to torrent and then below select tracker tab and you can edit the tracker details
this is my case, tested and it worked. Thank you
-
Had the same issue with Transmission 3.0 - redownloaded 2.94 again and is working fine. :cool2:
I'm using Transmission 3.0 and all torrents still say cannot connect to tracker
You may find you have no end of difficulty with Transmission 3.0. You may need to roll back to version 2.94
-
For me, I'm using deluge 2.0.3 trying to seed 500+ torrents. Usually about 200 of them report a tracker error and I have to manually "Update Tracker" or force another announce. Only about 16 torrents get re-announced without error at a time so I just keep re-announcing until all my torrents return OK tracker status. It's probably the DDOS protection feature that's causing it so it's a bit tedious, but manageable.
-
After a brief improvement a few days ago, things are terrible again.
SSL is unchecked in my profile, I'm using Transmission 2.94 and I have two types of messages:
• Tracker gave HTTP response code 404 (not found);
• Could not connect to tracker.I am seeding 476 torrents but the site (logically) sees only 86 of them.
-
I've tried good old Transmission 2.94, which worked fine for years, Transmission 3.0, which was only recently tried and does not work here but works elsewhere, and Deluge 2.0.3. None of them work, none of them can connect to the tracker. I have tried https, http, and added the .tw tracker. :cry2:
-
Does any one at the site, the site admins, know when this will be corrected? Downgrading to Transmission 2.94 does not always work and is not really a proper solution
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login