Jump to content

unregistered torrrent


flitox

Recommended Posts

ok let's try to stay simple,

i've just tried to upload a torrent, creating the file with utorrent posted no problem but after uploading it on the site and downloading it to be able to seed, i just kept getting an unregistered torrent msg.

thinking something was wrong with the tracker, i check the files/folder name and remove what could be offensive to it (like ' , ! & etc....), make another file but still same msg.

try renaming everything very simply, just one word for the folder and only number for the files, still the same result.

so decided to try creating the same torrent file using trader's little helper and this time, torrent get accepted by tracker and i can seed my files.....

so something got wrong with the little torrent file created by utorrent. not every time with any folder i choose but every time with some certain folder.

Link to comment
Share on other sites

certainly but this doesn't explain why when created with utorrent, the torrent get notified as unregistered, no matter how many time i try to do it and when i used another software, at 1st try the torrent get accepted.

so there is something wrong somewhere with utorrent when creating torrent file.

i never had that problem before until today when i tried to make one with the latest built

Link to comment
Share on other sites

adding a txt file doesn't change anything, i'm still getting the unregistered torrent msg

choosing a different piece size change nothing at all, unregistered torrent.

i try again to create the same torrent using TLH and it worked perfectly.

THL had a test torrent option, i tried it on hte torrent created with utorrent, but the report said there was no error. (but the fact are when uploaded it get an unregistered torrent message from the tracker)

Link to comment
Share on other sites

I don't know what this traders little helper is... If you want to check out differences between the torrents check out Ultima's Bencoded File Editor. It's a small download and allows viewing of torrent keys.

What is important is the INFO dictionary, that creates the INFOHASH which the tracker uses for tracking. Open up multiple instances of B.F.E. and load each of the torrents in. See what is different :/

Link to comment
Share on other sites

alright will do that tomorrow and post the result here

for your information Traders little helper is doing that:

Traders of lossless compressed audio files (e.g. ape, flac, mkw, or shn files) have to handle a lot of different applications to decode, encode, create/verify checksums, fix sector boundary errors, or create torrent files. Moreover some are command line programs requiring a deeper knowledge of how to use various parameters.

Trader's Little Helper bundles all the important features of those applications in one single easy-to-use graphical user interface offering

Verification of checksum files (md5, ffp, st5, and cfp files)

Creation of checksum files (md5, ffp, st5, and cfp files)

Test of encoded audio files (ape, flac, and shn format)

Display of audio file properties (ape, flac, shn, and wav files)

Fixing of sector boundary errors that come with ape, flac, shn, and wav files

Decoding of ape, flac, and shn files

Encoding of wav files to ape, flac, or shn format

Creation of torrent files

Creation of skt files for non-seekable shn files

Drag & Drop usage

Integration in Windows Explorer via context menu

in latest version, there is also an option to check torrent file

Link to comment
Share on other sites

;) Yes after you pointed it out I did look for it http://www.thetradersden.org/forums/showthread.php?t=17951 and http://tlh.easytree.org/ would have been useful in your original post. I looked at it but didn't see it had torrent creation capability.

The point still stands, SOMETHING is different. Whether you need to seed the torrent DOWNLOADED from the site after it is uploaded from creating in uTorrent OR you choose to add whatever site-specific keys it adds into the INFO dictionary prior to upload or adding into uT so that it registers... I am actually interested. Some sites add a "source" key via their scripts to ensure infohash uniqueness.

Link to comment
Share on other sites

ok heres the difference

with utorrent as creator:

piece lenght (i)=65536

pieces (B)[8300]=...

with THL:

piece lenght(i)=131072

pieces (B)[4160]=...

thats the only difference i've spotted

oops wait i checked that with the files i've created, not the one downloaded off the site!

will do that tomorrow for sure cuz it's getting very late here

Link to comment
Share on other sites

ok so i've tried creating the torrent using utorrent with 128ko selected for piecesize and when doing this, torrent is recognized by the tracker.

i did try to do the math with the numbers i wrote above (piece lenght X pieces) and to my surprise i didn't find the same result with the 2 tested torrent files.

or this time i both checked 128ko for piecesizes with utorrent & TLH and the number were the same

piece lenght(i)=131072

pieces (B)[4160]=...

Link to comment
Share on other sites

ok just did that with piecesize at 32 on public tracker and it worked without problem while on the site i first posted, only piecesize of 128 get accepted (and all other get unregistered torrent msg). so it looks like it is in the end a tracker problem.... weird thing is that when using another torrent creator, with the same piecesize, torrent get accepted. do you get an idea of why those make with utorrent get rejected??? since the torrent file seems exactly the same except for the line

created by (B)[13]=utorrent/180b

Link to comment
Share on other sites

:) Good detective work. That is odd that it would not "register" with a piecesize smaller than 128 KiB. All you can do is perhaps ask for a different error message perhaps, with a failure REASON, ... that is if their submittal page does not say "all torrents must have a piecesize of at LEAST .125 MiB.
Link to comment
Share on other sites

only torrent file is 128ko piece get accepted, it doesn't work when they are bigger either.

and that doesn't happen with every torrent i try. they are some folder where everything goes normally and some where i have to specify that 128ko pieces size in order to get it to work..... crazy!

also never happened before i update to latest built.....

i'll try to ask if i can get a different msg and a reason

Link to comment
Share on other sites

... So these TLH torrents are all accepted automatically no matter their piecesize?? That sounds... implausible but not impossible. It could also be the site has an (unspecified) bias towards a certain torrent creator's torrents :( The workaround as suggested is to change the created-by key in the torrent... i.e. with Ultima's B.F.E.

But since that didn't work... keeping track of all you're doing is half the work for this. :/ The other half is getting a sympathetic tracker higher-up to listen to you. If there are other usage / torrent key questions feel free to ask. :D

Link to comment
Share on other sites

as i said i never had problem with torrents created with utorrent with that tracker until i tried with last build.

i quite sure it never happen with previous build but if you want i can try reinstalling previous build and see if i get the error also

Link to comment
Share on other sites

You saw yourself... there is no difference in the torrent. That's all the tracker should be looking at. If removing the created-by key doesn't fix it it's definitely something in the tracker's "check" script. Are you sure it was given enough lead-time to be put on their "good torrent" list?? I know demonoid had some internal checker ... it had to be given ~ 5 minutes sometimes for you to be able to seed.

To keep confusion to a minimum, it would be a good idea to have each of your PREVIOUS uT in their own folder separate from your working uT... downgrades are not always handled well. Relevant FAQ entry.

Link to comment
Share on other sites

i'm not too sure to understand what you mean by:

it would be a good idea to have each of your PREVIOUS uT in their own folder separate from your working uT

also where i could get hold of previous bulid .exe (the links i know are always to some install .exe that will automatically install ut to program files/utorrent folder)

i'll try that tomorrow anyway, just to create a torrent and see if it get accepted or rejected.

also yes i think i've give them enough lead-time. TLH made torrent would either be in the good list as soon as it get added to the list or in the worst case i would have need to stop/start again torrent once to have it accepted. the ones made with ut, i've tried up to 5 time to stop/restart torrent with no result

Link to comment
Share on other sites

Since you're only using the old versions to create a torrent... for verification, just make a folder (i.e. for 1.7.7 or 1.6.1 make "1.7.7" and "1.6.1" as folders) create a blank file called settings.dat in there and place the exe in there. Then Ctrl-N to create a torrent (either specify "auto-size" or manually force 128 KiB) and try uploading it....

I sure hope this site allows editing of torrents.. so you can keep updating this torrent on their site with the different torrent/infohash but still see it as the SAME torrent you were originally trying to upload.

Also before you try to seed any of these duplicate torrents it's likely you will need to REMOVE the previous ones in uT. For the data with the SAME piecesize the infohash is the same and as such you will get the "file already appears to be in the list do you want to add the trackers"... instead of proving something about the torrent itself is incorrect.

Link to comment
Share on other sites

although i do not use utorrent myself, i too have seen this problem reported by 3 different people in the last 24hrs, and attempted to assist in those cases

torrents created in the latest utorrent 1.8 beta build seem to show unregistered torrent when uploaded to some private trackers. i had one user create torrents from different files, with different names, all same issue. he did try changing the chunk size (without success), but i do not believe they tried large chunk sizes (above 128)

however... a .torrent created by an older utorrent 1.8 beta build from the same files, using the same settings, and uploaded to the same tracker works fine, and the suggestion to downgrade to the previous 1.8 build fixed this problem for all three people

seems to me like something has changed in the latest utorrent build that has broken its compatibility

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...