Leaderboard

Hello! We inform you that all of our Lithuanian servers are being withdrawn and dismissed. The datacenter provider, Cherry Servers, has just asked for a block of all outbound ports except a few ones they called "standard ports" (sic) to prevent any possible future "copyright infringement" (to be noted: no infringement in the past has ever been proved). It is clearly an unacceptable request for us, and we guess for everyone, and it also reveals the true face of Cherry Servers datacenter as an enemy of the Internet. For us, it's also an option to finally get rid of the last servers still not supporting IPv6. Cherry Servers was one of our last providers still lacking IPv6 support, a fact that should have given us a "head up!" about Cherry Servers poor commitment to providing decent services. We will be actively looking for an alternative datacenter. We will be looking for datacenters where the concept of mere conduit is understood, and IPv6 infrastructure is available. In the meantime keep in mind that we offer several servers in the Baltic region as well as other, nearby countries. Kind regards

RESOLVED Had to de-select Automatic Port Selection and manually set to 1194. Perhaps upstream policy changes with my ISP have occurred. But it's working now. Thanks @giganerd for taking an interest.

There is one thing you absolutely need to do: Bind qBittorrent to your TAP adapter! In Advanced section, look for a "Bind to interface" setting and select the TAP adapter from the drop-down menu when you're connected. This causes qBittorrent to only use the TAP adapter when talking to the outside world, and if that adapter is not in a connected state it won't be able to talk. Easy. It's like a kill switch: If the connection dies, all connections of qB die. If you reconnect, qB will reconnect to peers. In Speed section, set your max upload to whatever your uplink is you're subscribed to, -10%. The "problem" you might be facing is that a connection between computers is a two-way street. When you're downloading packets, you're also sending packets back which ACKnowledge that you received the package. As your download throughput increases, so does the amount of ACKs sent back. Plus, if other clients download from you, the bottleneck is perfected. If you carelessly ignore the max upload setting, you allow the torrent client to fill your uplink with packets.

How is a more adequate answer than the one given to you supposed to look? Through five servers you are unable to watch Netflix as of now, this is confirmed by that same Air Staff quoted by you. If it happens with others and you think they're also affected, post them at your convenience, and be sure to also give some more info about your setup (server, port, protocol, device, etc.) After all, it's not your thread, you just came along and posted a nearly empty "I have the same issue" post, by mentioning an even less helpful piece of information about your renewal. I don't see you meaningfully contributing with a workaround, or any piece of info enabling everyone to enjoy Netflix via AirVPN again. Maybe a server that works for you with certain connection settings? – Since you gave no info about which server shows the symptoms you described. Maybe with a certain app? We have 30+ US servers. Surely one is working? And have you followed Staff's suggestion with the cache as of now? Let us help you help yourself, and maybe others, too…