bittorrent (ktorrent) - can't connect

[uatavpn 6]

mint 17.3

ktorrent 4.3.1

 

tried servers both in the US and CA

 

neither torrents nor magnet links work

 

if i disconnect from the VPN, all is fine

 

torrent, tracker and DHT ports are all forwarded (VPN, not the router)

 

PEX, DHT and webseeds all enabled

 

Tue Apr 26 13:27:42 2016: UDPTracker::error : Timeout contacting tracker udp://9.rarbg.com:2710/announce
Tue Apr 26 13:27:42 2016: UDPTracker::error : Timeout contacting tracker udp://glotorrents.pw:6969/announce
Tue Apr 26 13:27:42 2016: UDPTracker::error : Timeout contacting tracker udp://p4p.arenabg.com:1337
Tue Apr 26 13:27:42 2016: UDPTracker::error : Timeout contacting tracker udp://tracker.coppersurfer.tk:6969/announce
Tue Apr 26 13:27:42 2016: UDPTracker::error : Timeout contacting tracker udp://tracker.internetwarriors.net:1337
Tue Apr 26 13:27:42 2016: UDPTracker::error : Timeout contacting tracker udp://tracker.leechers-paradise.org:6969
Tue Apr 26 13:27:42 2016: UDPTracker::error : Timeout contacting tracker udp://tracker.opentrackr.org:1337/announce

 

above is all torrent files, but as i said, magnet links don't work either

[Guest]

well you aren't providing enough information to actually troubleshoot it all you are saying is how they don't work and showing the trackers that don't work. But trackers connecting to their port isn't the issue it's likely the port setting you have on, to tell us your exact settings with the VPN and the torrent client would be needed for us to give any kind of answer to the problem cuz currently we would have no clue what it could be.

[uatavpn 6]

i have 3 ports forwarded in the 65k range, all TCP and UDP - the same ports are allowed in the firewall (incoming) and the log shows no traffic being blocked - in ktorrent, the same 3 ports are set (bittorrent port, tracker port and DHT port)
​
​the server i'm currently connected to is Lesath in Canada

​

​i'm not sure what else you may need to know, so please tell me what else i can provide

[Guest]

Well the firewall doesn't have much to do with the ports since it's being routed through the OpenVPN daemon, the ports are being connected through the server. I'm assuming mint is your OS so linux, have you tried picking one port only and using it on all settings? Also the trackers doesn't matter much which port you select since there you attempt to connect to them not the other way around, the ports are generally where the traffic from seeders get sent to.

 

Possibly even, if you can give me the torrent you used I can test if it works with other AirVPN that might help locate if it's on your end or AirVPNs

[uatavpn 6]

have you tried picking one port only and using it on all settings?

 

yes - just tested that now - no change

 

here's a test torrent...

 

mint iso: http://torrents.linuxmint.com/torrents/linuxmint-17.3-cinnamon-64bit.iso.torrent

 

should also add that i'm connecting using UDP (443) and OpenVPN (not the Eddie client)

[RidersoftheStorm 20]

The tracker port, you have forwarded, is that the UDP tracker port?

In K Torrent do you have the UpnP plug in checked?

The Bittorrent port, is that set at 8080? Sometimes called WebUI.

[uatavpn 6]

@LastChance - sorry, i was never notified of your reply

 

UDP tracker port is forwarded on the Air side (TCP & UDP), as well as allowed by my firewall (inbound), and configured in kTorrent "UDP tracker port" setting - it's in the 65k range

 

all the same is true for the bittorrnet port, except it's a different port number - it's also in the 65k range

 

i'm not using UPnP and there are no ports forwarded on my router

[Guest]

I tested the torrent with an AirVPN server and although it wasn't the trackers you reported having problems on it worked just fine and connected without problems. Also keep in mind while on the VPN port forwarding on your end as in firewalls and router has litterally NO positive effect it may cause your IP to leak since the ports are queried on the server not your internet but if you open the port on your system it's available and can be connected to despite VPN settings, all your traffic goes from the server to a random port that you are connected with.

[uatavpn 6]

thanks for your feedback - i'm a bit confused regarding port forwarding...

​

​when torrents/magnet links were working, i believe i wasn't able to upload (share) until i a ) forwarded a port on Air and b ) allowed it in my firewall

​

​before opening the port in my firewall D/L's worked, but i couldn't upload - at this point i can still do neither - every time i start a torrent the tracker status is listed as "announcing" until it times out and then i get the error that the trackers could not be reached​ 

[RidersoftheStorm 20]

UDP tracker port, might not have to be forwarded, if it is behind a router OR  software firewall.

What do you use for a firewall?

[uatavpn 6]

​iptables with the UFW GUI

​

as you suggested, ​nothing is forwarded currently in the firewall and nothing was ever forwarded in the router

[uatavpn 6]

still struggling with this and looking for help

[zhang888 1066]

What are the results of the port forwarding check? In the port forwarding page.

[uatavpn 6]

for the TCP port, error 110 - unreachable, time out

 

for the UDP port there is no option to check it

 

because of info provided in this thread, i don't know which ports, if any, need to be opened in my software firewall - to preform your test, i opened (incoming) both the TCP and UDP ports (TCP bittorrent and UDP tracker ports, respectively) - the DHT port i set the same as the tracker port

[zhang888 1066]

If you have the timeout 110 error then you didn't forward it correctly in your router or firewall.

You can search the forum about how to do this step on

[uatavpn 6]

the issue is the same with the firewall disabled

 

also i'm not sure how i could not forward a port correctly - the port # is correct, the direction is correct and the protocol is correct

 

i've been through several other threads here and either they don't apply or don't help

 

also if i ...

 

lsof -i |grep ktorrent

...it appears ktorrent is listening on the ports i forwarded

[zhang888 1066]

You might have a device (like a router) that prevents this from working. Are you behind NAT?

How are you running the OpenVPN client, on the router or on the Linux machine with the kTorrent?

 

You will need to post your iptables rules in case you run the client on the Linux machine.

Also, the forwarding should be done on the tun0 interface, not the eth0 one.

[uatavpn 6]

looks like a bug in kTorrent - just tried qBittorrent and it works fine with exactly the same settings

 

saw this kind of strangeness reported by another user as well

[uatavpn 6]

when you say that forwarding should be done on the tun0 interface, i assume you're referring to the s/w firewall (ufw) - my question is, should the torrent client also be set to use tun0 (or eth0)?

 

thanks