Troubleshooting

From BakaBT Wiki
Jump to: navigation, search

Contents

Before You Start

1) Be sure to read the FAQ and this troubleshooting page for answers.

2) Search the forums for similar problems.

3) Perform a simple Google search to see if your problem is already known and answered.

4) If all of the above fails, post your problem on our forums. Be sure to include as much detail as possible. Refer to step 1, you must have read the entire FAQ before posting your problem.

(This page is for technical questions relating to the Bittorent and connectivity protocols and clients that use it. For BakaBT site-related questions, see the FAQ.)

Connectivity Issues

Why can't I connect? Is the site blocking me?

Your failure to connect may be due to several reasons.

Server downtime

Sometimes the server goes down a little while due to the heavy load that maintenance tasks put on the server. This should resolve itself within half an hour, so wait a while and see fi the server goes back up again.

Maybe your address is blacklisted

If you cannot then the reason for the problem lies elsewhere. In particular it does not block lower level protocols, you should be able to ping/traceroute the server even if your address is blacklisted. It should not stop you from reaching the site. This works at Apache/PHP level, it's just a script that blocks logins from those addresses. The site blocks addresses of banned users.

Your ISP blocks the site's address

DNS name resolution and/or network problems are the usual culprits.) There's nothing we can do. In this case it doesn't matter if the proxy is anonymous or not, or which port it listens to. Note that you can still visit the site via a proxy, follow the instructions in the relevant section. You should contact your ISP (or get a new one). (In first place, it's unlikely your ISP is doing so.

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.

I can't log in

I try to log in but get brought to another login page

This could be due to one of a few possible reasons:

You're on a dynamic IP

The login script doesn't like dynamic IPs. Nothing you can do about this except try to get a static IP or find a VPN service that will give you a static IP.

Cookie Problems

Clear your cookies and try again. Make sure cookies are enabled in your browser-of-choice.

Browser Problems

Maybe your browser is a freshly released one that is still in alpha or early beta. Report this issue to them and hope they fix it in a future release.

I try to log in but it says my account is suspended

See: Account Restrictions

The page takes forever to load after I log in

The server might be momentarily unresponsive, try again in half-an-hour.

Torrent Errors

What's this IOError - Error13 Permission denied error?

It shows up when your client is for some reason unable to open the partially downloaded torrent files. IOError means Input-Output Error, and that is a file system error, not a tracker one. 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. NTFS is much more robust and should never permit this problem.) 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 supports FAT - or NT/2000/XP with FAT formatted hard drives.

Other torrent errors

Check FAQ:Torrent and Tracker Issues and see if the error message is already covered there.

Speed Issues

I can't seem to seed at all, or my upload speed is really slow.

If there are no leechers... If you are on a torrent that has something like 10 seeders and 2 leechers, the chances of you uploading a great deal are slim to none. what are you expecting? First, check that you actually have someone to upload any data to.

Suppose that you sell apples. You have some very nice, juicy apples, but there's one problem - 100 other people in the marketplace also sell apples. Now, 3 potential customers walk into the marketplace, and they're looking for apples; what are the chances that they will buy from you?

Unless you have very good reason to believe that your uploading speed is severely below normal, do not ask us why you can download at 1MB/s but can only upload at 100KB/s. Secondly, if you are able to download very quickly but can only upload at about 1/10th of your download speed, this is perfectly normal. Most internet access plans offered by ISPs follow this asymmetric-speed, and few ISPs will actually offer plans with uplaod rate as fast as download rate.

How can I improve my download speed?

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 seeder-to-leecher ratio is low. TorrentFreak have created a great guide on how to improve your download speed. You'll find it here. (side note: If you did not enjoy the slow download speed, remember to seed well so that others will not have to endure the same.)

There are a couple of things that you can try on your end to improve your speed:

Do not immediately jump on new torrents

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.) In particular, do not do it if you have a slow connection.

Check your connection settings

See" "Connectivity Issues".

See if your ISP is throttling you

There are several online services, such as Glasnost, that allow you to do so. Some ISPs actively throttle Bittorrent traffic. Find out if your ISP does so.

If your ISP throttles you, try enabling Protocol Encryption in your torrent client settings.

Limit your upload speed

The upload speed affects the download speed in essentially two ways:

  1. 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.
  2. 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.

A good thumb rule is keeping the upload at about 80% of the theoretical upload speed. The upload should be kept as high as possible while allowing the ACKs to get through without delay. 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.) The full effect is a combination of the two.

browsing or ftp), always think of the overall upload speed. Know your client. The same applies if you are using your connection for anything else (e.g. Shad0w's) do it on a per torrent basis. Azureus) limit global upload speed, others (e.g. Some clients (e.g. If you are running more than one instance of a client it is the overall upload speed that you must take into account.

Limit the number of simultaneous connections

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. Note that these numbers are additive, if you have two instances of a client running the numbers add up. Some operating systems (like Windows 9x) do not deal well with a large number of connections, and may even crash. There are no fixed values for this, you may try 60 or 100 and experiment with the value.

Limit the number of simultaneous uploads

The ideal number is typically much lower than the number of connections, and highly dependent on your (physical) connection. 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. Isn't this the same as above? No.

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. The download speed should increase as soon as you have some pieces to share. This makes the starts slow, in particular if, by change, the peers you are connected to include few or no seeders.

Why is my browsing so slow while leeching?

You will have to use a third-party solution, such as NetLimiter. If you are a peer in a fast torrent it will almost certainly saturate your download bandwidth, and your browsing will suffer. A client like Azureus allows the user to limit uploads & downloads. Your download speed is always finite.

Browsing was used just as an example. The same would apply to gaming, IMing, etc., ...

Why is my port number reported as "---"? (And why should I care?)

The tracker has determined that you are firewalled or NATed and cannot accept incoming connections.

Even worse, if two peers are both in this state they will not be able to connect at all. This means that other peers in the swarm will be unable to connect to you, only you to them. This has obviously a detrimental effect on the overall speed.

You will also find lots of information on the subject at PortForward). Check your router documentation and/or support forum. The way to solve the problem involves opening the ports used for incoming connections (the same range you defined in your client) on the firewall and/or configuring your NAT server to use a basic form of NAT for that range instead of NAPT (the actual process differs widely between different router models.

My ISP uses a transparent proxy. What should I do?

Caveat: This is a large and complex topic. It is not possible to cover all variations here.

Short reply: change to an ISP that does not force a proxy upon you. If you cannot or do not want to then read on.

What is a proxy?

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): Basically a middleman.

Type Description
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 or 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?

The relevant ones are HTTP_CLIENT_IP, HTTP_X_FORWARDED_FOR and REMOTE_ADDR. It lists the HTTP headers that the server where it is running received from you. Try ProxyJudge.

Why is my port listed as "---" even though I'm not NAT/Firewalled?

The BakaBT tracker is quite smart at finding your real IP, but it does need the proxy to send the HTTP header HTTP_X_FORWARDED_FOR. 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. 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.

I am on a dynamic IP/I just changed my static IP recently, and it seems to have affected my bittorent connection settings.

BakaBT uses a keypass-based system (See: How is my traffic tracked?). Changes in your IP will not affect your connection to the tracker, as long as you downloaded the torrent file when logged in.

There are peers in the swarm but I can't connect to any of them.

Your ISP may be shaping traffic. Enable encryption in your torrent client, and set it to the highest level possible.

Note: This does not hide your IP from other peers!