Please login to reply
|
|||||
[#160318]
Written by: frontliner [20/05/2011, 19:03] |
|||||
is there a list of http trackers we can use? i've changed my port a couple times and eventually i gets blocked by comcast. i have verified it does work when i first change the port, downloads will use dht and finish, but when my rss grabber gets the next set about a day or two later with the new shows, the port is blocked. |
|||||
[#160334]
Written by: znavy264 [21/05/2011, 02:24] |
|||||
nova, then could you kindly tell us or explain to us why everything is moving towards udp? i'm sure one day udp will be supported by just about every client out there....but you have to remember one major thing....who are the majority of your customers? the answer: college students and/or people of that age group. if you think about it, not everyone who torrents has access to their router...therefore they are either stuck with dhcp or have something that's blocking them from torrenting because they live on a college campus where they have no access to their own router, so most people use a proxy or by some other means. so scifi3001, you are wrong, and i agree with salmonella. i really don't believe you guys are looking at the big picture, which should be about the majority of your customers. go ahead, ask btguard how many customers they support! i'm betting you that at least 90 percent of those customers use eztv releases. with that being said....lots of people are moving to other releases because yours are not working...and i'm pretty sure the average torrent user has no clue how to fix that, so they start moving onto other releases, like by scenetime or torrenting, something that has working http trackers. i honestly do not see why it's such a big deal for eztv guys to add an extra (working) http tracker. why are you so against it? also, for those of you users reading this....the tracker that i find to work for just about every torrent is: http://tracker.publicbt.com:80/announce i know adding the port number to the address is like basically using udp....but it seems to work even if you use http....although the other udp trackers don't seem to work when adding http to them. i hope that helps you guys temporarily since the site admins don't really seem to care about current issues, and are only working towards "the future". |
|||||
[#160342]
Written by: akbar [21/05/2011, 04:33] |
|||||
wtf? my earliest memory of port forwarding my router, 10+ years ago, included udp and tcp |
|||||
[#160496]
Written by: frontliner [23/05/2011, 00:43] |
|||||
what are you supposed to do if dht/udp is blocked by your isp? | |||||
[#160552]
Written by: 234sale [23/05/2011, 11:20] |
|||||
also,,, some other sharing communities use old versions of ut,, thus,, like me if your on 1.83 ut,,, then you'll have to find another software to download from eztv |
|||||
[#160563]
Written by: TheBard [23/05/2011, 13:53] |
|||||
hi all, i understand why you started to use udp exclusively, and i don't want to beg for http trackers. i really want to solve this thing myself, but i don't even know where to start. i use utorrent 2.2.1 and all tcp/udp traffic is port-forwarded by my router to my bittorrent pc's ip address. the various "enable dht tracker support" boxes in utorrent are all checked. as far as i could find out, utorrent supports udp trackers and dht just fine, just like this port-forwarding should be enough for it to work. but in utorrent i only get a "[dht] waiting for announce..." and "udp://tracker.ccc.de:80 connection timed out." error. all the information i was able to find on the net was very basic, just simple stuff on how to configure your router, no usable troubleshooting, except some forum thread where it was recommended to delete and rebuild your dht.dat, which did exactly nothing for me. again, i'm very willing to help myself and learn, but can anybody please point me in the right direction? thanks in advance! |
|||||
[#160566]
Written by: Meztv [23/05/2011, 14:32] |
|||||
there still seems to be a lot of torrents published with http trackers (lol and fqm for instance). i constantly get slow starts because the openbittorrent http tracker in the torrent times out. i manually change it to udp most times, but it's a bit of an annoyance. i support the move to udp but it doesn't seem to be 100% implemented yet? |
|||||
[#160620]
Written by: Fealar [24/05/2011, 03:28] |
|||||
after a day of cursing and refreshing my port knowledge i got on the vuze port wiki and saw i had to change my incoming tcp/udp port to 49001. this solved the problem for me so i hope it helps others too. oh and eztv.... come on if you change the system like this at least give us a heads up and tell us how to fix it, would have been a nice gesture. fealar. |
|||||
[#160659]
Written by: TheBard [24/05/2011, 13:26] |
|||||
fealar, perfect! that did it. many thanks for the info. i still don't really understand why you need port 49001 - but at least it works now. again, thank you. |
|||||
[#160680]
Written by: blubacon [24/05/2011, 19:51] |
|||||
disclaimer: i'm a noob, so what i'm going to type next is majorly noobish! i'm using utorrent 2.2.1 i wanted to download 'sanctuary'. when i added it (like is usually do) via this site, the "dht" in the status bar in ut said waiting to load or something. after about 5 mins of waitng, i check the tracker, and it was "http://tracker.openbittorrent.com/announce" ;. so, i went to another site that i know the good folks at eztv posts torrents to (or that site hosts eztv torrents, whatever). when i added their torrent for "sanctuary", it came with 4 of udp trackers: udp://tracker.ccc.de:80 (times out) udp://tracker.istole.it:80 (working) udp://tracker.openbittorrent.com:80 (working) udp://tracker.publicbt.com:80 (times out) soo..... not sure what's going on with the torrents posted on this site (http tracker), but the eztv torrents from the other site has the working udp trackers. don't know if this helps anybody, but it helped me sort things out on my end. peace! |
|||||
[#160687]
Written by: slaymer [24/05/2011, 21:52] |
|||||
thanks for working this out, it has sorted out all my vuze issues i had utorrent installed but didn't like how you needed to install a webui client to use remote access (i can remote in via android using vuze webui) thanks again |
|||||
[#160774]
Written by: Micha [26/05/2011, 01:15] |
|||||
i can download criminal minds s06e24 and glee s02e22, but the rest doesn't work. can somebody explain how to solve this problem ? in dummie language... |
|||||
[#160820]
Written by: tommyjonq [26/05/2011, 16:44] |
|||||
okay, let's not mess ourselves. if they were "people people" they wouldn't be tech geniuses. i just downloaded and launched the newest build of transmission 2.31 for mac os x (i run 10.5) and the eztv torrents are downloading just fine. is transmission the greatest thing since sliced bread? no. are the flipping udp tracked torrents downloading? yes. |
|||||
[#160821]
Written by: tommyjonq [26/05/2011, 16:48] |
|||||
uhhhhhhhh, when i try to "reply" to a post, my post gets posted somewhere else. do i care? not that much. but i did want to let people know that the newest version of transmission for mac (i use os 10.5) does support udp trackers and eztv torrents are working fine. |
|||||
[#160848]
Written by: rocky500 [27/05/2011, 07:33] |
|||||
i was having the same problems for a few weeks now. after reading this thread i updated my utorrent from v1.81 to v2.21. all fixed now. connects to trackers. thanks. |
|||||