Rubber, first don't  :crazy2: That looks like an error that I've seen with some versions of uTorrent. You don't say what you are using to create and post your torrent. Perhaps the staff here can help if it is QTM. Otherwise my advice is to use a different program to create your torrent, an earlier version of uTorrent or something like maketorrent. If you can give more information about exactly what you are doing it is easier too offer advice. And the manual upload is not very difficult if you follow the instructions.

You make some good points And sadly there is no way of knowing if the original poster is till around so you could be spending bonus points that nobody gets.

I let request set in my inbox for at least a day, which give me time to deal with dupes.   Then I usually get to them after 24 hours. They will get two notices about the points when it process them.

It could just mean that the tracker is down temporarily. No harm in deleting them if you have completed the download. Or just leave them and see if the tracker goes live again

Another member reporting the same issue message on the helpdesk, got it working at another atempt, without changing anything. Perhaps you just give it a trial?

It would appear that you have resolved the issue.

It appears that while improving the tracker so that there are less timeouts received at the torrent clients announces, a glitch prevented the system to log the (first) seeding started. Which then lead to the "not seeding" messages sent out and later automated deleting.  :afr: The different messages to the Helpdesk and this topic helped to become aware of the issue, than you. Please understand that when such question first drops in, before there are multiple in a short period, the usual standard cause is addressed in the reply. In your case it wasn't a standard answer, because the moderator did look into the log to see it was deleted for not seeded after 3 days. Certainly a lot of torrents got deleted and even more "not seeding" messages sent out wrongly. Sorry! The issue has been fixed.

Thanks for explaining that, Popper

someday there will come an option to tag pictures for better display

Nope, I tried a completely different one and that worked, so there must've been something about that particular torrent file  ??? Anyway, thanks for your reply 

Your last upload was moved away from the visible listings for being a duplicate to another existing torrent. That explains why you can't see it but QTM refuses the upload, because the torrent is still there at the moment. It will be deleted once no more downloading peer is seen. You should have got a PM about that duplicate, that is automated once a moderator confirms the duplicate report.

The sign in the bottom right hand corner isn't a real connectivity check. It just means µTorrent receives incoming connections, which may be due to previously opened ports by outgoing connections made from µTorrent (they stay open a little while). I don't have a Mac at hand, but when I've looked on µTorrent for Mac in a Apple Store, the User Interface was very similar to the Windows version. The only difference I've seen on a first glance was the file navigation using the Mac OSX file "Finder" and not the Windows file explorer (of course). So I would still expect the "Network" test being under µTorrent > Options > Setup Guide and the port used to connect in the µTorrent < Options < Preferences > Connection menu. It is the port set there you'll need to make sure the Mac OSX firewall allows incoming connections.

On another torrent site, the TORRENT links often don't load, but they provide both a TORRENT and MAGNET link, and the Magnet links work.  I honestly don't know what a Magnet link is.. but they work.

I've experienced for years that either the upload succeeds (if it is a relatively small video file) and then some sort of error meesage or if it is a bigger file taking very long to upload it times out with another failure message. Sorry, don't remember the wordings of the failure messages, don't do that often  >:D

Had that problem once and it was because of a corrupt video file. Once I replaced the file everything worked fine.

As much as it is not really recommended in some ways, there is another way in which to get around this with Vuze…. Just don't use the SSL tracker. For some reason, it's only the SSL tracker that causes this kind of error. There are two different tracker styles that we have. Their Announce URLs start as follows: SSL: https://tracker.gaytorent.ru/…. Non-SSL http://tracker.gaytorent.tw:2710/…...

Thanks!

If you have not already claimed your points, please click here to send junior a PM to request the FTUP credit.

Thanks guys.