Leaderboard

How do I use the files I've downloaded? Check out this guide. Downloaded a movie and don't know what CAM/TS/TC/SCR means? Check out this guide. Why did an active torrent suddenly disappear? There may be three reasons for this: (1) The torrent may have been out-of-sync with the site rules. (2) The uploader may have deleted it because it was a bad release. A replacement will probably be uploaded to take its place. (3) Torrents are automatically deleted after 28 days. How do I resume a broken download or reseed something? Open the .torrent file. When your client asks you for a location, choose the location of the existing file(s) and it will resume/reseed the torrent. Why do my downloads sometimes stall at 99%? The more pieces you have, the harder it becomes to find peers who have pieces you are missing. That is why downloads sometimes slow down or even stall when there are just a few percent remaining. Just be patient and you will, sooner or later, get the remaining pieces. What are these "a piece has failed an hash check" messages? Bittorrent clients check the data they receive for integrity. When a piece fails this check it is automatically re-downloaded. Occasional hash fails are a common occurrence, and you shouldn't worry. Some clients have an (advanced) option/preference to 'kick/ban clients that send you bad data' or similar. It should be turned on, since it makes sure that if a peer repeatedly sends you pieces that fail the hash check it will be ignored in the future. The torrent is supposed to be 100MB. How come I downloaded 120MB? See the hash fails topic. If your client receives bad data it will have to redownload it, therefore the total downloaded may be larger than the torrent size. Make sure the "kick/ban" option is turned on to minimize the extra downloads. Why do I get a "Not authorized (xx h) - READ THE FAQ" error? From the time that each new torrent is uploaded to the tracker, there is a period of time that some users must wait before they can download it. This delay in downloading will only affect users with a low ratio, and users with low upload amounts. Ratio below0.50and/or upload below5.0GBdelay of48hRatio below0.65and/or upload below6.5GBdelay of24hRatio below0.80and/or upload below8.0GBdelay of12hRatio below0.95and/or upload below9.5GBdelay of06h "And/or" means any or both. Your delay will be the largest one for which you meet at least one condition. This applies to new users as well, so opening a new account will not help. Note also that this works at tracker level, you will be able to grab the .torrent file itself at any time. N.B. Due to some users exploiting the 'no-delay-for-seeders' policy we had to change it. The delay now applies to both seeding and leeching. So if you are subject to a delay and get the files from some other source you will not be able to seed them until the delay has elapsed. Why do I get a "rejected by tracker - Port xxxx is blacklisted" error? Your client is reporting to the tracker that it uses one of the default bittorrent ports (6881-6889) or any other common p2p port for incoming connections. This tracker does not allow clients to use ports commonly associated with p2p protocols. The reason for this is that it is a common practice for ISPs to throttle those ports (that is, limit the bandwidth, hence the speed). The blocked ports list include, but is not neccessarily limited to, the following: Direct Connect 411 - 413 Kazaa 1214 eDonkey 4662 Gnutella 6346 - 6347 BitTorrent 6881 - 6889 In order to use use our tracker you must configure your client to use any port range that does not contain those ports (a range within the region 49152 through 65535 is preferable, cf. IANA). Notice that some clients, like Azureus 2.0.7.0 or higher, use a single port for all torrents, while most others use one port per open torrent. The size of the range you choose should take this into account (typically less than 10 ports wide. There is no benefit whatsoever in choosing a wide range, and there are possible security implications). These ports are used for connections between peers, not client to tracker. Therefore this change will not interfere with your ability to use other trackers (in fact it should increaseyour speed with torrents from any tracker, not just ours). Your client will also still be able to connect to peers that are using the standard ports. If your client does not allow custom ports to be used, you will have to switch to one that does. Do not ask us, or in the forums, which ports you should choose. The more random the choice is the harder it will be for ISPs to catch on to us and start limiting speeds on the ports we use. If we simply define another range ISPs will start throttling that range also. Finally, remember to forward the chosen ports in your router and/or open them in your firewall, should you have them. What's this "IOError - [Errno13] Permission denied" error? If you just want to fix it reboot your computer, it should solve the problem. Otherwise read on. IOError means Input-Output Error, and that is a file system error, not a tracker one. It shows up when your client is for some reason unable to open the partially downloaded torrent files. The most common cause is two instances of the client to be running simultaneously: the last time the client was closed it somehow didn't really close but kept running in the background, and is therefore still locking the files, making it impossible for the new instance to open them. A more uncommon occurrence is a corrupted FAT. A crash may result in corruption that makes the partially downloaded files unreadable, and the error ensues. Running scandisk should solve the problem. (Note that this may happen only if you're running Windows 9x - which only support FAT - or NT/2000/XP with FAT formatted hard drives. NTFS is much more robust and should never permit this problem.) What's this "TTL" in the browse page? The torrent's Time To Live, in hours. It means the torrent will be deleted from the tracker after that many hours have elapsed (yes, even if it is still active). Note that this a maximum value, the torrent may be deleted at any time if it's inactive.

This feature will allow: 1. Guest will now be able to comment on torrents. 2. Guest will be able to comment on profile accounts. 3. Guest will be able to rate torrents. Under progress and will soon be released.

We are adding a bunch of Notifications as follows: 1. Torrent Uploaded Notification: You will receive notifications on successful Uploads - This excludes Auto - uploaders - who use Bot Scripts. 2. Notifications on new comments, not direct message notifications. 3. Notifications on users thanking your torrents. 4. Notifications when you receive a review from a member. 5. Notifications when your torrents are deleted. 6. Notifications on new achievements. These are a few list of upcoming notifications.... This thread will be updated as soon as we have more notifications been added....

The cPanel accounts are created using a primary domain. All primary domains on the hosting account use “public_html” directory for all its website files and data. The sub-directories inside the public_html directory is occupied by the addon domains. The primary domain can also be setup to use a sub-directory inside public_html directory instead of public_html itself. Follow the below steps to change the document root of your primary domain in cPanel account. Please note that, you will need to have root SSH access to perform these steps. 1) Connect to your server via SSH as root user. You may follow the tutorial below, if you are using a Windows system to connect to your server via SSH. This tutorial explains how to use “Putty”, SSH client software to access server. 2) Using your favorite text editor (say vim) edit the following file. [iCODE]$ vim /cpanel/userdata/username/domain.com[/iCODE] Replace the “username” with your cPanel account username and “domain.com” with your primary domain name and “subdir” with your new directory. Find the following two lines in this file. [iCODE]documentroot: /home/username/public_html path: /home/username/public_html/cgi-bin[/iCODE] Modify these two lines to change the document root of your primary domain to a sub-directory inside “public_html” directory. [iCODE]documentroot: /home/username/public_html/subdir path: /home/username/public_html/subdir/cgi-bin[/iCODE] Save the file after changes are made and then delete the cache file for your primary domain. [iCODE]$ rm -vf /var/cpanel/userdata/username/domain.com.cache[/iCODE] 3) If the primary domain has an SSL certificate installed, edit the following file the same way as above. [iCODE]$ vim /var/cpanel/userdata/username/domain.com_SSL[/iCODE] Save the file after changes are made and then delete the cache file for your primary domain. [iCODE]$ rm -vf /var/cpanel/userdata/username/domain.com_SSL.cache[/iCODE] 4) Run the following scripts to update the user data cache and rebuild apache configuration file. [iCODE]/scripts/updateuserdatacache /scripts/rebuildhttpdconf[/iCODE] 5) Restart Apache server to load changes. [iCODE]$ service httpd restart[/iCODE] Source: [Hidden Content]

puff!!! Nice tut, thank you.

this is very useful if Cpanel is messing up and u can't fix issues like this. It's important to rebuild userdata else changes won't take effect..

How To Find Password Dumps With Google Dork With this little trick, you can find other peoples' account usernames : passwords for many websites. Go to pastebin.com or google.com and search this code. " Program: Url/ Host: Login: Password: Computer: Date: Ip: " Program: Url/Host: Login: Password: Computer: Date: Ip: Program: Url/Host: [Hidden Content] Login: Password: Computer: Date: IP: The results should come up with lots of passwords and account information for sites like Facebook, Gmail etc... Get An Account For Any Website! Go to [Hidden Content] In the url/search bar, copy and paste all of the following. Program: Url/Host: Login: Password: Computer: Date: IP: Now lets say you want an account for facebook. so after the Url/Host you would write in the facebook website address, just like this: Program: Url/Host: [Hidden Content] Login: Password: Computer: Date: IP: Searching for TO GET THE USERNAME AND PASSWORD OF ANY WEBSITE Here is d solution: Go to [Hidden Content] In the url/search bar, copy and paste all of the following. Program: Url/Host: Login: Password: Computer: Date: IP: Now lets say you want an account for facebook. so after the Url/Host you would write in the facebook website address, just like this: Program: Url/Host: [Hidden Content]/ Login: Password: Computer: Date: IP: Searching for this will show you dumps on the internet. A dump is when someone takes all the accounts that they have hacked, and places them on a website so everyone can gain access to them. You can use this to obtain accounts for any website, but the accounts won’t work all the time, because people may have already changed the login details, depending on how old the dump is. You will not find logins for every website. For example, if you search for facebook accounts, you are bound to find a lot of them, but if you search for a website that isn’t popular at all, or doesn’t have many users, you probably will not find any dumps. Hope this Helped.

Maybe my address is blacklisted? The site blocks addresses listed in the (former) PeerGuardian database, as well as addresses of banned users. This works at Apache/PHP level, it's just a script that blocks loginsfrom those addresses. It should not stop you from reaching the site. In particular it does not block lower level protocols, you should be able to ping/traceroute the server even if your address is blacklisted. If you cannot then the reason for the problem lies elsewhere. If somehow your address is indeed blocked in the PG database do not contact us about it, it is not our policy to open ad hoc exceptions. You should clear your IP with the database maintainers instead. Your ISP blocks the site's address (In first place, it's unlikely your ISP is doing so. DNS name resolution and/or network problems are the usual culprits.) There's nothing we can do. You should contact your ISP (or get a new one). Note that you can still visit the site via a proxy, follow the instructions in the relevant section. In this case it doesn't matter if the proxy is anonymous or not, or which port it listens to. Notice that you will always be listed as an "unconnectable" client because the tracker will be unable to check that you're capable of accepting incoming connections.

What is a proxy? Basically a middleman. When you are browsing a site through a proxy your requests are sent to the proxy and the proxy forwards them to the site instead of you connecting directly to the site. There are several classifications (the terminology is far from standard): Transparent A transparent proxy is one that needs no configuration on the clients. It works by automatically redirecting all port 80 traffic to the proxy. (Sometimes used as synonymous for non-anonymous.) Explicit/Voluntary Clients must configure their browsers to use them. Anonymous The proxy sends no client identification to the server. (HTTP_X_FORWARDED_FOR header is not sent; the server does not see your IP.) Highly Anonymous The proxy sends no client nor proxy identification to the server. (HTTP_X_FORWARDED_FOR, HTTP_VIA and HTTP_PROXY_CONNECTION headers are not sent; the server doesn't see your IP and doesn't even know you're using a proxy.) Public(Self explanatory) A transparent proxy may or may not be anonymous, and there are several levels of anonymity. How do I find out if I'm behind a (transparent/anonymous) proxy? Try ProxyJudge. It lists the HTTP headers that the server where it is running received from you. The relevant ones are HTTP_CLIENT_IP, HTTP_X_FORWARDED_FOR and REMOTE_ADDR. Why is my port listed as "---" even though I'm not NAT/Firewalled? The tracker is quite smart at finding your real IP, but it does need the proxy to send the HTTP header HTTP_X_FORWARDED_FOR. If your ISP's proxy does not then what happens is that the tracker will interpret the proxy's IP address as the client's IP address. So when you login and the tracker tries to connect to your client to see if you are NAT/firewalled it will actually try to connect to the proxy on the port your client reports to be using for incoming connections. Naturally the proxy will not be listening on that port, the connection will fail and the tracker will think you are NAT/firewalled. Can I bypass my ISP's proxy? If your ISP only allows HTTP traffic through port 80 or blocks the usual proxy ports then you would need to use something like socks and that is outside the scope of this FAQ. Otherwise you may try the following: Choose any public non-anonymous proxy that does not use port 80 (e.g. from this, this or this list). Configure your computer to use that proxy. For Windows XP, do Start, Control Panel, Internet Options, Connections, LAN Settings, Use a Proxy server, Advanced and type in the IP and port of your chosen proxy. Or from Internet Explorer use Tools, Internet Options, ... (Facultative) Visit ProxyJudge. If you see an HTTP_X_FORWARDED_FOR in the list followed by your IP then everything should be ok, otherwise choose another proxy and try again. Visit this site. Hopefully the tracker will now pickup your real IP (check your profile to make sure). Notice that now you will be doing all your browsing through a public proxy, which are typically quite slow. Communications between peers do not use port 80 so their speed will not be affected by this, and should be better than when you were "unconnectable". How do I make my bittorrent client use a proxy? Just configure Windows XP as above. When you configure a proxy for Internet Explorer you re actually configuring a proxy for all HTTP traffic (thank Microsoft and their "IE as part of the OS policy" ). On the other hand if you use another browser (Opera/Mozilla/Firefox) and configure a proxy there you'll be configuring a proxy just for that browser. We don't know of any BT client that allows a proxy to be specified explicitly. Why can't I signup from behind a proxy? It is our policy not to allow new accounts to be opened from behind a proxy.

Do not immediately jump on new torrents The download speed mostly depends on the seeder-to-leecher ratio (SLR). Poor download speed is mainly a problem with new and very popular torrents where the SLR is low. (Proselytising sidenote: make sure you remember that you did not enjoy the low speed. Seed so that others will not endure the same.) There are a couple of things that you can try on your end to improve your speed: In particular, do not do it if you have a slow connection. The best speeds will be found around the half-life of a torrent, when the SLR will be at its highest. (The downside is that you will not be able to seed so much. It's up to you to balance the pros and cons of this.) Limit your upload speed The upload speed affects the download speed in essentially two ways: Bittorrent peers tend to favour those other peers that upload to them. This means that if A and B are leeching the same torrent and A is sending data to B at high speed then B will try to reciprocate. So due to this effect high upload speeds lead to high download speeds. Due to the way TCP works, when A is downloading something from B it has to keep telling B that it received the data sent to him. (These are called acknowledgements - ACKs -, a sort of "got it!" messages). If A fails to do this then B will stop sending data and wait. If A is uploading at full speed there may be no bandwidth left for the ACKs and they will be delayed. So due to this effect excessively high upload speeds lead to low download speeds. The full effect is a combination of the two. The upload should be kept as high as possible while allowing the ACKs to get through without delay. A good thumb rule is keeping the upload at about 80% of the theoretical upload speed. You will have to fine tune yours to find out what works best for you. (Remember that keeping the upload high has the additional benefit of helping with your ratio.) If you are running more than one instance of a client it is the overall upload speed that you must take into account. Some clients (e.g. Azureus) limit global upload speed, others (e.g. Shad0w's) do it on a per torrent basis. Know your client. The same applies if you are using your connection for anything else (e.g. browsing or ftp), always think of the overall upload speed. Limit the number of simultaneous connections Some operating systems (like Windows 9x) do not deal well with a large number of connections, and may even crash. Also some home routers (particularly when running NAT and/or firewall with stateful inspection services) tend to become slow or crash when having to deal with too many connections. There are no fixed values for this, you may try 60 or 100 and experiment with the value. Note that these numbers are additive, if you have two instances of a client running the numbers add up. Limit the number of simultaneous uploads Isn't this the same as above? No. Connections limit the number of peers your client is talking to and/or downloading from. Uploads limit the number of peers your client is actually uploading to. The ideal number is typically much lower than the number of connections, and highly dependent on your (physical) connection. Just give it some time As explained above peers favour other peers that upload to them. When you start leeching a new torrent you have nothing to offer to other peers and they will tend to ignore you. This makes the starts slow, in particular if, by change, the peers you are connected to include few or no seeders. The download speed should increase as soon as you have some pieces to share. Why is my browsing so slow while leeching? Your download speed is always finite. If you are a peer in a fast torrent it will almost certainly saturate your download bandwidth, and your browsing will suffer. At the moment there is no client that allows you to limit the download speed, only the upload. You will have to use a third-party solution, such as NetLimiter. Browsing was used just as an example, the same would apply to gaming, IMing, etc...