Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
New Vuze update broke VPN Helper
#1
I just updated to the latest Vuze program on 2 computers and it seems to have broken the VPN Helper plugin.  I use PIA for my VPN and Vuze does not seem to read the Port Forwarding port from PIA anymore.  Before the update it worked fine.
I can manually set the port under "Connection".  But, unless I uncheck the "Use VPN's Port Forwarding" under "Plugins : VPN Helper" the proper port number won't stay.

I am using PIA version .65.  I see their latest release is .68.  Do I need to update to get it working again?

Java 1.8.0_121 (64 bit)
Oracle Corporation
c:\program files (x86)\java\jre1.8.0_121
SWT v4716, win32
Windows 7 v6.1, x86
V5.7.5.0/4 az3
Reply
#2
When you have the "Use VPN's Port Forwarding port" on, does the plugin report it got a port successfully, or does is have a warning?

If it says it's ok, and got a port, and it's different than the one reported by the PIA app, everything should still be ok. PIA allows for multiple open ports. The plugin tries to use the existing one, but may end up getting a new one. You can always check to see if your Peer list has any "R" (Remote) connected clients. If it does, then the port is good.

If there was a warning, we've had a few people solve the problem by blanking out the "PIA Program directory" path in the plugin config and restarting Vuze.

Let me know if you get anywhere with this info

(03-24-2017, 02:43 PM)camaro1919 Wrote: I just updated to the latest Vuze program on 2 computers and it seems to have broken the VPN Helper plugin.  I use PIA for my VPN and Vuze does not seem to read the Port Forwarding port from PIA anymore.  Before the update it worked fine.
I can manually set the port under "Connection".  But, unless I uncheck the "Use VPN's Port Forwarding" under "Plugins : VPN Helper" the proper port number won't stay.

I am using PIA version .65.  I see their latest release is .68.  Do I need to update to get it working again?

Java 1.8.0_121 (64 bit)
Oracle Corporation
c:\program files (x86)\java\jre1.8.0_121
SWT v4716, win32
Windows 7 v6.1, x86
V5.7.5.0/4 az3
Reply
#3
(03-24-2017, 08:57 PM)'ArronM' Wrote: When you have the "Use VPN's Port Forwarding port" on, does the plugin report it got a port successfully, or does is have a warning?

If it says it's ok, and got a port, and it's different than the one reported by the PIA app, everything should still be ok. PIA allows for multiple open ports. The plugin tries to use the existing one, but may end up getting a new one. You can always check to see if your Peer list has any "R" (Remote) connected clients. If it does, then the port is good.

If there was a warning, we've had a few people solve the problem by blanking out the "PIA Program directory" path in the plugin config and restarting Vuze.

Let me know if you get anywhere with this info




 

If I check the box "Use VPN's Port Forwarding port"  and if I have PIA already running it reports "Port stored in PIA Manager config is 43617" and "Core port TCP/UDP changed from 51011 to 43617" and shows a green "OK" icon.  I do lose all of my "R" connections in my peer list
If I un-check the box, the "Port stored" message does not appear and I still get a green "OK" icon.  If I set the TCP/UDP ports under "Connection" to the port assigned to me by PIA everything works fine and my "R" connections return in my peer list.
If I stop PIA everything stops and I get a red "BAD" icon.
I need to use the port PIA assigns to me when I connect to their servers (currently 51011).
I tried upgrading PIA Manager from v0.65 to their latest release v0.68 and the issue with Vuze VPN Helper is unchanged.

I had a similar issue last year when I changed my password for PIA and forgot to change it in Vuze VPN Helper.  Vuze saw PIA was running but it did not read the right port.  When I entered in the right password, VPN Helper started reading the right PIA assigned port again.
I tried blanking out the "PIA Program directory" path in the plugin config and it did not help.

This is a result of a failed Network Status test run, below it is a good test run;
Test starting
Default public address is 172.xx.xx.xxx
Bindable addresses: 127.0.0.1, 10.xx.xx.xx, 192.xxx.xx.xxx
0 NAT devices found
No SOCKS proxy found
No HTTP proxy found
1 bind addresses
    10.xx.xx.xx
Testing HTTP outbound
    Test successful
Testing TCP outbound
    Test successful
Testing UDP outbound
    Test successful
Testing TCP port 43617 inbound
    Test failed: NAT test failed: Connection to 172.xx.xx.xxx:43617 (your computer) refused
    Check your port forwarding for TCP 43617
Testing UDP port 43617 inbound
    Sending outbound packet and waiting for reply probe (timeout=5000)
    Sending outbound packet and waiting for reply probe (timeout=10000)
    Sending outbound packet and waiting for reply probe (timeout=15000)
    Sending completion event
    Test failed: Inbound test failed
    Check your port forwarding for UDP 43617
1 public/external addresses found
    172.xx.xxx
    AS details: as=46562,asn=TOTAL-SERVER-SOLUTIONS - Total Server Solutions L.L.C., US, bgp_prefx=172.xx.xx.x/xx[/172.xx.xx.x-/172.xx.xx.xxx]
Vuze Services test
    Vuze Website - http://www.vuze.com
        Certificate: CN=*.vuze.com, OU=Domain Control Validated - RapidSSL®, OU=See http://www.rapidssl.com/resources/cps ©15, OU=GT10270993
        Connection result: 200/OK
    Client Website - client.vuze.com
        Certificate: CN=*.vuze.com, OU=Domain Control Validated - RapidSSL®, OU=See http://www.rapidssl.com/resources/cps ©15, OU=GT10270993
        Connection result: 200/OK
    Version Server - version.vuze.com
        Connection result: 200/OK
    Pairing Server - pair.vuze.com
        Certificate: CN=*.vuze.com, OU=Domain Control Validated - RapidSSL®, OU=See http://www.rapidssl.com/resources/cps ©15, OU=GT10270993
        Connection result: 200/OK
    License Server - license.vuze.com
        Certificate: CN=*.vuze.com, OU=Domain Control Validated - RapidSSL®, OU=See http://www.rapidssl.com/resources/cps ©15, OU=GT10270993
        Connection result: 200/OK
    Plugins Website - plugins.vuze.com
        Certificate: CN=*.vuze.com, OU=Domain Control Validated - RapidSSL®, OU=See http://www.rapidssl.com/resources/cps ©15, OU=GT10270993
        Connection result: 200/OK
Indirect Connect test
    Connecting to https://www.vuze.com
    Certificate: CN=*.vuze.com, OU=Domain Control Validated - RapidSSL®, OU=See http://www.rapidssl.com/resources/cps ©15, OU=GT10270993
    Connection result: 200/OK
Distributed protocol test
  Incoming routing established for XXXX
  Searching 128 contacts for 8 test targets
  Making outbound connection to /65.186.44.33:43612
  Making outbound connection to /71.57.141.218:6881
  Making outbound connection to /89.173.25.202:6881
  Making outbound connection to /59.101.167.75:24760
  Making outbound connection to /109.63.205.0:58768
  Making outbound connection to /76.164.227.242:36675
  Making outbound connection to /47.55.24.40:51157
  Making outbound connection to /91.83.122.79:27360
  Making outbound connection to /108.39.92.29:44372
  Making outbound connection to /79.19.1.165:25791
  Making outbound connection to /82.242.35.227:50500
  (LL 11) Outbound connection fail: end of stream on socket read
  Making outbound connection to /67.177.50.236:32450
  Searching complete, 12 targets found
    Status: sessions=11, out_attempts=12, out_connect=12, in_connect=0
    Status: sessions=11, out_attempts=12, out_connect=12, in_connect=0
  Destroying tester
Test complete
  Results
    Outbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Seed,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Seed,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Seed,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Seed,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Seed,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Leecher,connected, hand sent, hand !recv, bitf !sent, bitf !recv
    Outbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    No incoming connections received, likely NAT problems
  Incoming routing destroyed for XXXX


When I use the port assigned to me by PIA the following entries change;

Testing TCP port 51011 inbound
    Test successful
Testing UDP port 51011 inbound
    Sending outbound packet and waiting for reply probe (timeout=5000)
    Sending completion event
    Test successful

Distributed protocol test
  Incoming routing established for BC43B80A12FD3A18592842A5C627E9C293C16587
  Searching 128 contacts for 8 test targets
  Making outbound connection to /75.69.75.128:53404
  Making outbound connection to /192.0.182.141:13115
  Making outbound connection to /47.200.227.172:40614
  Got incoming connection from /75.69.75.128:65433
  Got incoming connection from /192.0.182.141:62338
  Got incoming connection from /47.200.227.172:49448
  Making outbound connection to /68.53.137.216:33388
  Got incoming connection from /68.53.137.216:62409
  Making outbound connection to /78.194.151.43:16290
  Got incoming connection from /78.194.151.43:61901
  Making outbound connection to /82.243.74.233:51319
  Making outbound connection to /78.134.16.96:24878
  Making outbound connection to /31.54.93.240:60392
  Got incoming connection from /78.134.16.96:62636
  Got incoming connection from /82.243.74.233:50117
  Got incoming connection from /31.54.93.240:51575
  Making outbound connection to /176.23.193.12:62699
  Got incoming connection from /176.23.193.12:56436
  Searching complete, 9 targets found
    Status: sessions=18, out_attempts=9, out_connect=9, in_connect=9
  Destroying tester
Test complete
  Results
    Outbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Seed,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Seed,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Outbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
    Test successful
  Incoming routing destroyed for BC43B80A12FD3A18592842A5C627E9C293C16587
Reply
#4
(03-24-2017, 08:57 PM)'ArronM' Wrote: When you have the "Use VPN's Port Forwarding port" on, does the plugin report it got a port successfully, or does is have a warning?

If it says it's ok, and got a port, and it's different than the one reported by the PIA app, everything should still be ok. PIA allows for multiple open ports. The plugin tries to use the existing one, but may end up getting a new one. You can always check to see if your Peer list has any "R" (Remote) connected clients. If it does, then the port is good.

If there was a warning, we've had a few people solve the problem by blanking out the "PIA Program directory" path in the plugin config and restarting Vuze.

Let me know if you get anywhere with this info




 
Good news, I hope!  Vuze VPN Helper appears to be working again on one computer.
I removed PIA v0.65 from my system (including all user config data).  I blanked out all data in VPN Helper.  I installed the latest PIA program (v0.68) and entered the PIA path way, user name and password into VPN Helper again.  It seems to have worked.  VPN Helper read the port from PIA Manager, but the message changed from "Port stored in PIA Manager config is xxxxx" to "Port returned from RPC is xxxxx"  I will need to wait for PIA to change my port number to see if it reads the new port.

Another issue popped up, in the bottom tool bar, my "Routing" icon is now red instead of green.  If I hover the mouse pointer over it it appears to be trying to connect to both 127.0.0.1 and 10.xx.xx.xx. Any idea what may be causing this?

Thank you for your help.
Reply
#5
(03-24-2017, 08:57 PM)'ArronM' Wrote: When you have the "Use VPN's Port Forwarding port" on, does the plugin report it got a port successfully, or does is have a warning?

If it says it's ok, and got a port, and it's different than the one reported by the PIA app, everything should still be ok. PIA allows for multiple open ports. The plugin tries to use the existing one, but may end up getting a new one. You can always check to see if your Peer list has any "R" (Remote) connected clients. If it does, then the port is good.

If there was a warning, we've had a few people solve the problem by blanking out the "PIA Program directory" path in the plugin config and restarting Vuze.

Let me know if you get anywhere with this info

(03-24-2017, 02:43 PM)'camaro1919' Wrote: I just updated to the latest Vuze program on 2 computers and it seems to have broken the VPN Helper plugin.  I use PIA for my VPN and Vuze does not seem to read the Port Forwarding port from PIA anymore.  Before the update it worked fine.
I can manually set the port under "Connection".  But, unless I uncheck the "Use VPN's Port Forwarding" under "Plugins : VPN Helper" the proper port number won't stay.

I am using PIA version .65.  I see their latest release is .68.  Do I need to update to get it working again?

Java 1.8.0_121 (64 bit)
Oracle Corporation
c:\program files (x86)\java\jre1.8.0_121
SWT v4716, win32
Windows 7 v6.1, x86
V5.7.5.0/4 az3



 


Upgrading the PIA app to v75 just broke VPN Helper for me again. Downgrade PIA to v65 and VPN Helper works again. With v75 VPN Helper gets a port but it is not the one assigned by PIA. I tried clearing the path to pia_manager, restarting Vuze, and pointing the path back to pia_manager, which worked when I had trouble several months ago after upgrading to v65, but this time it didn't help. PIA login and password are set in VPN Helper config.

Everything works fine when I use PIA v65, but I'd really like to be able to upgrade to the latest version.
Reply
#6
This has happened to me on the last two upgrades!  It took me a while to remember how I fixed it, but here goes.  

It may have something to do with checking the box "Use VPN Helper" that appears during the installation process as this seems to erase the stored password for PIA.  Retype your user name and password into the boxes provided (Tool, Options, Plugins, VPN Helper) and save the configuration. Also, make sure the UPnP plugin is checked "enable", refresh the mappings, and check your router to make sure the correct port is being passed through.  Likewise, make sure you are using the correct password from PIA (I had changed mine from the random string they assign you when you sign up).

​Maybe next time do not check "Use VPN Helper" during the installation process and see if that helps.  I cannot find the version number, but I am on the latest PIA manager so this should work for you.
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  New Version? gigglepot33 4 2,696 12-19-2017, 12:12 AM
Last Post: ekstasee
  migrate archives to new computer and keep torrent stats molosse 1 978 12-18-2017, 10:41 PM
Last Post: ekstasee



Users browsing this thread: 1 Guest(s)