This is an issue related to the latest version of uTorrent. We recommend using version 2.2.1. Also, you need to make sure that you add some port forwarding rules in your router to forward the port that your torrent client uses to their respective computers, both in TCP and in UDP. Without this, getting upload traffic can be difficult.
As I mentioned in my PM to you, DHT is used for dynamic peer exchange, which is not used on a private tracker like ours. There is obviously some other under-laying issue here that needs to be addressed. We first need to find the tracker status message. If you are using uTorrent or BitTorrent, you can find this by clicking on the torrent, then clicking on the "Trackers" tab. The status message will be located beside the announce URL.
As for the connection, it is likely that either your government, or possibly just your ISP has put some routing restrictions in place, which are preventing you from connecting to our tracker. This is another option to be able to get around such internet censorship. I personally use PrivateVPN these days. Just be aware that you need to use a server location that supports port forwarding. Some server locations will only forward a specific port, while other servers will forward ALL ports. If you are using a server that only forwards ONE port, then you need to also make sure that your torrent client is configured to use the port that is being forwarded.
This simply means that one of our staff has promoted (or refreshed) the torrent to make it appear back at the top of the list. If you look at the first line of the description, you will see the original date that it was actually uploaded.
As for the SBP, the SBP is deducted from your available total, however because you are the uploader who receives these points, they are immediately credited back to you, seemingly cancelling out the transaction. Simply put, it is a torrent that was uploaded by you at some point in the past, which has been brought back to the top of the list to help revive it.
There is no way that I know of to change the default option. If you want to search including dead, this is something that you need to specify manually on each search.
The SSL tracker is a more secure option. Some VPN providers, certain torrent clients, and some proxy services don't play well with the SSL tracker. I would suggest enabling the SSL tracker option so that all new .torrent files that you download will tell your torrent client to use the SSL tracker by default.
If you want to test whether or not you will have issues with the SSL tracker option, you can try changing the tracker URL in your torrent client for an existing torrent. To do this, simply change the beginning of the URL.
Change this: http://tracker.gaytorrent.tw:2710/
To this: https://tracker.gaytorrent.ru/
If you are able to switch over to the SSL tracker without any issue, then I would recommend that you change ALL your existing torrents over to the SSL tracker, and enable that option so that all future downloads are automatically branded with the SSL tracker, instead of the regular tracker.
@urx585 & @xios01: In your cases, it would appear you may have been affected by a system glitch due to your upload speed. I will reset your accounts and enable a feature for you that should resolve this problem for you.
Have you tried clearing your cache & cookies and restarting your browser?
Also, have you tried more than one browser?
Are you able to take a screenshot of this error so that I can get an understanding of exactly where this is happening?
This could also be a sign of improper port forwarding settings on your network. See, you need to make sure that the port that your torrent client uses is forwarded in your router to your computer, both in TCP and UDP. This is a rather critical step to ensure that you can properly receive incoming connections. While you may be able to still seed on some trackers, even as a passive node, this is something that is very difficult to do with our system.
So… You need to make sure that the proper port forwarding settings are in place.
I get about 13 down / 3 up…. And that's spread across not one, but FOUR pre-Y2K legacy COPPER ADSL lines bonded together into a single line with the speed of all four lines combined.
If I am not mistaken, the size limit is 4 GB, or to be more precise, 4,194,304 bytes.
Which torrent would you like deleted and why?
If you are having trouble receiving upload traffic with the torrents that you have seeding, this is likely not because of a "flaw" in the tracker, but rather, is caused by not forwarding the correct port in TCP and UDP from your router through to your computer. See, without the port that your torrent client uses being forwarded through to your computer, you will end up with the EXACT issue that you are describing, where seeding becomes incredibly difficult.
Also, if you are using a VPN, you need to be sure that you are either using the port that they are forwarding (as a number of providers/servers only forward ONE port), or that you are using a server that forwards ALL ports. This is a very critical part to being able to seed.
Wouldn't the client report the "stop" behavior to the tracker so it can remove the user from the seeding list? How could it not report the upload traffic also?
Just my guess. I'm not an expert of it.
You would think so, however it seems that this does not happen and that any data transferred from the last up to 30 minutes before stopping the torrent gets lost for some reason.
It should also be noted that you need to have made at least three forum posts anywhere in the forum to be able to see this section of the forum.
There are two things that can cause this. One of them is the @ symbol in the file or folder name. This causes big problems with creating torrents because of how it affect the bencoding of the .torrent file. The second possibility is you may have exceeded the number of files that you can handle in a single torrent. This is most common with picture sets. If you have picture sets, it may help to roll only the pictures of the set into a single ZIP file but make sure to NOT put the videos themselves into the ZIP file.
In your torrent client, you are using an IP Filtering list. Either the address or possibly one of the subnet ranges that our tracker uses is on your list. Please ensure that the following IP address and subnets are NOT found within your IP Filter list:
77.247.179.58
77.247.179.58/32
77.247.179.32/27
77.247.176.0/21
If you find ANY of the above in your IP Filter list, the connection to the tracker simply will NOT work until they are removed from the list, or the actual IP address itself is whitelisted and verified BEFORE looking through the hosts to block.
I've never been too worried, especially now that I've had to settle down with only having ONE partner.
Stalled usually means that there has been no activity on the torrent due to no leechers. If you start seeding them again, I can help you get some upload traffic from it.
I usually skirt around the issue by doing the force start/resume to force the torrents to keep seeding/leeching.