Jump to content
Not connected, Your IP: 3.228.21.186

Recommended Posts

Hi,

 

Some strange behaviour is happening when the VPN is connected:

1) Everything was working as-is until 3 days ago

2) Now theres no torrent activity at all even with PEX/DHT enabled (also cannot connect to trackers)

3) Cannot reach port 46555 externally (port forwarding is set up to be 46555->46555), but can internally

4) Can access other ports externally

5) Can ping/access external servers

 

When not connected via VPN, everything works fine. Point 4 is concerning, since it indicates the VPN connection is working and forwarding traffic, but just not for the transmission port I guess.

 

Setup

* Ubuntu 12.04

* Sirius, Heze servers via port 443 and UDP

 

Terminal outputs

user@box:/var/log$ sudo lsof -l | grep transmiss

transmiss 22850 113 10u IPv4 4579574 0t0 TCP *:46555 (LISTEN)

transmiss 22850 113 11u IPv6 4579576 0t0 TCP *:46555 (LISTEN)
transmiss 22850 113 12u IPv4 4579577 0t0 UDP *:46555

 

user@box:/var/log$ nc 127.0.0.1 46555 < /dev/null; echo $?
0

 

user@box:/var/log$ sudo ufw status
Status: inactive

 

Troubleshooting steps so far

  • Rebooted
  • Downloaded config, tried different VPN servers
  • Disabled all firewalls
  • Confirmed that the port 46555 is accessible locally via UDP/TCP
  • Viewed transmission logs and saw "Could not connect to tracker"
  • Tried using a different port for transmission

Any hints and assistance would be greatly appreciated!

 

Thanks

 

Share this post


Link to post

Okay, another update. I added the torrent guard IP checker torrent, and it connected successfully giving the following message:

 

checkMyTorrentIp.png
Tier 1
  • Announce error: Success, Your torrent client IP is: 46.21.151.107 - Today 11:09:21 PM
    Next announce in 28 minutes
    Scrape error: Tracker gave HTTP response code 404 (Not Found) - Today 11:06:11 PM
     
     
     

Other torrents aren't starting though.

Share this post


Link to post

The below trackers are reporting the the connection has failed. They work however without the VPN. Also, all other traffic in the VPN appears to be working fine. Is it possible that these trackers have blocked the VPN IP range? Also, I thought trackers were redundant.. any idea what PEX and DHT isn't helping?

 

  • udp://tracker.openbittorrent.com:80
    Last Announce: N/A
    Announce not scheduled
    Scrape error: Connection failed - Today 11:18:34 PM
    Seeders: 409 Leechers: 122 Downloads: 10
Tier 2
  • udp://tracker.publicbt.com:80
    Last Announce: N/A
    Announce not scheduled
    Scrape error: Connection failed - Today 11:19:54 PM
    Seeders: 254 Leechers: 65 Downloads: 10
Tier 3
  • udp://tracker.istole.it:6969
    Last Announce: N/A
    Announce not scheduled
    Scrape error: Connection failed - Today 11:18:40 PM
    Seeders: 398 Leechers: 115 Downloads: 10
Tier 4
  • udp://tracker.ccc.de:80
    Last Announce: N/A
    Announce not scheduled
    Scrape error: Could not connect to tracker - Today 10:45:20 PM
    Seeders: N/A Leechers: N/A Downloads: N/A
Tier 5
  • udp://open.demonii.com:1337
    Last Announce: N/A
    Announce not scheduled
    Scrape error: Connection failed - Today 11:20:14 PM
    Seeders: 385 Leechers: 105 Downloads: 4634

Share this post


Link to post

Switching to Persei server seems to be working.

 

My guess is that the IP ranges are being blocked by those trackers for servers Sirius and Heze.

Share this post


Link to post

Nope, even Persei isn't working. The connections that were working were through my real IP. 

 

I think that DHT/PEX aren't working because the port forwarding isn't working. But I'm a noob when it comes to how torrents work.

 

Tier 1
  • udp://tracker.openbittorrent.com:80
    Announce error: Connection failed - Today 11:52:53 PM
    Next announce in 2 minutes, 8 seconds
    Scrape error: Connection failed - Today 11:54:00 PM
    Seeders: N/A Leechers: N/A Downloads: N/A
Tier 2
  • udp://tracker.publicbt.com:80
    Announce error: Connection failed - Today 11:54:13 PM
    Next announce in 13 minutes
    Scrape error: Connection failed - Today 11:54:13 PM
    Seeders: N/A Leechers: N/A Downloads: N/A
Tier 3
  • udp://tracker.istole.it:6969
    Announce error: Connection failed - Today 11:54:13 PM
    Next announce in 14 minutes
    Scrape error: Connection failed - Today 11:54:13 PM
    Seeders: N/A Leechers: N/A Downloads: N/A
Tier 4
  • udp://tracker.ccc.de:80
    Announce error: Could not connect to tracker - Today 11:52:13 PM
    Next announce in 1 minute, 28 seconds
    Scrape error: Could not connect to tracker - Today 11:54:00 PM
    Seeders: N/A Leechers: N/A Downloads: N/A
Tier 5

Share this post


Link to post

I just opened a support ticket for this exact same issue. The port forward checking tool in the client area returns with error 111. Hope this gets resolved soon.

Share this post


Link to post

I'm using Vuze client on Win 8.1. I eliminated my router and connected directly to  my cable modem. When my vpn client is not running, the NAT test for the forwarded port passes. Once I connect to the vpn and bind to that connection, the NAT test for the forwarded port fails. I'm not sure what's going on, but it is definitely not on my end. I hope tech support can get this resolved. I'm useless without this. This problem also happens with the router connected and properly configured for the forwarded port.

Share this post


Link to post

I'm glad I'm not the only one experiencing this

 

UPDATE: I've formatted my system to install Ubuntu 14.04. Everything is a fresh install, but the problem still persists. Connections are made with no VPN, but when the VPN is connected transmission connections fail. That is, the connections can be made on the local network but not via the VPN.

Share this post


Link to post

I'm finally connecting with my forwarded port. It seemed to clear up after working with tech support. They did some testing and said everything looked good on their end. It may be a coincidence, but I'm now connecting and working good. 

Share this post


Link to post

Had the same problem with magnet links failing. Changed my forwarded ports to UDP only, and all is good now. Ports showed unreachable when it was both TCP and UDP. It all was working before the recent updates to the servers, so who knows, maybe TCP got messed up.

Share this post


Link to post

Had the same problem with magnet links failing. Changed my forwarded ports to UDP only, and all is good now. Ports showed unreachable when it was both TCP and UDP. It all was working before the recent updates to the servers, so who knows, maybe TCP got messed up.

 

Hello!

 

Thanks for this warning, we will investigate.

 

Kind regards

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Security Check
    Play CAPTCHA Audio
    Refresh Image

×
×
  • Create New...