Uploaded Not Change When Seeding Complete 100%
-
This time I made a torrent of 5.7G size big, my seeding has completing 100% and the snatched is over 14 now. Here's my torrent page,
https://www.gaytorrent.ru/details.php?id=3e5eb6fbe18c2bce2aa7ceff5c48333d2bd3f77360a25dadWhen my seeding is keep going, I open my personal profile, I find my Uploaded Amount didn't chage :cry2: (image NO.1), this is impossible to happen. Then, I find my torrent information also has the same problem, the Upl. stays at 889.01MB all the time, as you see, the file-size is bigger than Upl.(image NO.2). My total Upload Amount shows in utorrent is over 6.75GB now (image NO.3).
Are u kidding me? :afr: What's the problem of it? What will you indemnify me for my losses if the Uploaded Amount still not change? This is my valuable collection.
-
The Uploaded shows only 21.5GB now, not increasing 6.75GB. The problem is still exist.
-
I am working on the Helpdesk request for this now. Due to the sensitivity of what needs to be discussed, I will leave my reply in the helpdesk shortly. I can give general information here, but in your case, this will require discussing information specific to you and your connection that would be best left discussed in private.
-
I am working on the Helpdesk request for this now. Due to the sensitivity of what needs to be discussed, I will leave my reply in the helpdesk shortly. I can give general information here, but in your case, this will require discussing information specific to you and your connection that would be best left discussed in private.
Thanks for caring about this :hug2:. So far, my total Up. shows in utorrent is 8.92GB now (image 1). I have to quit seeding now, because as you see, the Upl. is not increasing normally in my profile (image 2). This is a severe problem that the Number of Uploads is not 1:1 count synchronously. It means I have lost my Upl. 8.92-(22.23-20.84)=7.53GB in the past seeding. I hoped this can be considered about and seize back my loss of Upl.
PS: Also the tracker is working normally (image 3). I don't know what is this problem.