Vuze Won't Run

[tonydrake420]

WOW!  You guys really are superstars.  Seeing as I'm the one that started all this.... I thought I should let you know that I have been watching this thread even after I had given up all hope.  I checked in today and saw the last post regarding Hola.  I thought I'd give it a whirl and......... abracadabra!  Fantastic.  I have only one question left, now that I have my beloved Vuze up and running again.

Why, when I've been using both Hola and Vuze since Adam was a boy did it all go so suddenly wrong?  A gold star and a smartie to the one who can answer that!  And.... what would happen if (I am unlikely to start fiddling around again now, but one never knows!) I were to reinstall Hola?!!?

Anyway........ thank you all so much for your input and advice.


 

I'm with Sodam on this one. I havent been at this for days, but hours yes(the usual, uninstall, 32/64 queries etc etc), and I was lucky to find this thread. After learning new fantasmagoricle things about command line, I got Vuze up and running albeit using a different port. GREAT suggestion by ArronM! I too found that Hola was hogging the port, and I have quoted Sodam because I have the same question, in that if I wanted to reinstall Hola, would it find itself another port to use, or would it push Vuze out of the way again? I think I might just never close Vuze again to be safe! ;P

 

ok so i was following and understanding some, but now with this hole hola thing i am lost and sure many others will be. so  for us less technically proficient ppl would some one please explain what hola is and how to fix it?

[ekstasee]

ok so i was following and understanding some, but now with this hole hola thing i am lost and sure many others will be. so  for us less technically proficient ppl would some one please explain what hola is and how to fix it?

 

hi Tony, I didn't know what Hola was and I suspected that it may have been an application associated with media streaming, pay-per-view or something similar, but I did understand that it whatever it was, it was using and monopolising a port that the Vuze Launcher relies on being aing able to access, to complete the Vuze launch.  

Anyway, on reading your query, I judt did a "BING" and it seems that Hola is a VPN service (search if you don't know what that is) that these folk have been using for their BT activity.

[reddog]

ok so i was following and understanding some, but now with this hole hola thing i am lost and sure many others will be. so  for us less technically proficient ppl would some one please explain what hola is and how to fix it?


 

hi Tony, I didn't know what Hola was and I suspected that it may have been an application associated with media streaming, pay-per-view or something similar, but I did understand that it whatever it was, it was using and monopolising a port that the Vuze Launcher relies on being aing able to access, to complete the Vuze launch.  

Anyway, on reading your query, I judt did a "BING" and it seems that Hola is a VPN service (search if you don't know what that is) that these folk have been using for their BT activity.

 

Thats right ekstasee and tonydrake. Hola is something that can be used for viewing Geoblocked content, but is also a streaming application that plugs into your browser. Tony, if you didnt know what it was, its likely you dont have it and thus it isnt what is causing your problem. What I can say though, is ArronM's idea of something blocking your port could happen with more programs than just Hola, so it could be worth having a look at your Resource Monitor. 
Happy hunting!

[parg]

The latest beta has some changes that should help get Vuze running if it is a port issue such as that with Hola - see http://dev.vuze.com/ for the latest beta and manual installation instructions.

[tonydrake420]

sorry, I am not much for programming so most of that just went way over my head so I may just wait till it works seeing as it usually get an update to fix theses things. I looked int what Parg  suggested but have no idea what to do with those files after I download them and really don't wanna bug you guys to walk me through what is likely remedial to you.

[tonydrake420]

I am also starting to think it is a NAT problem caused by the isp/cable company I have blocking vuze and other such torrent sites due to illegal downloading capabilities and or just to curb downloading in general in order to free up bandwidth because a couple ppl told me they got letters regarding downloading and bandwidth usage, and also when I run the vuze internet connection test this is what I get:

Test starting
Default public address is 207.255.33.9
1 NAT device found
    waugh1959: address=192.168.1.1:1780, public address=207.255.33.9
No SOCKS proxy found
No HTTP proxy found
No explicit bind address set
Testing HTTP outbound
    Test successful
Testing TCP outbound
    Test successful
Testing UDP outbound
    Test successful
Testing TCP port 57835 inbound
    Test failed: NAT test failed: Connection timed out (207.255.33.9:57835)
    Check your port forwarding for TCP 57835
Testing UDP port 57835 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 57835
1 public/external addresses found
    207.255.33.9
    AS details: as=11776,asn=ATLANTICBB-JOHNSTOWN - Atlantic Broadband Finance, LLC,US, bgp_prefx=207.255.0.0/18[/207.255.0.0-/207.255.63.255]
Vuze Services test
    Vuze Website - www.vuze.com
        Certificate: CN=*.vuze.com, OU=Domain Control Validated - RapidSSL®, OU=See 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 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 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 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 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 www.rapidssl.com/resources/cps ©15, OU=GT10270993
    Connection result: 200/OK
Distributed protocol test
  Incoming routing established for 6D0E9706A81CD0D08A13CC8918C5815778413A30
  Searching 128 contacts for 8 test targets
  Making outbound connection to /206.169.80.162:53966
  Making outbound connection to /83.155.2.131:50500
  Making outbound connection to /76.173.185.19:52538
  Making outbound connection to /88.124.163.55:6881
  Making outbound connection to /82.233.224.62:51892
  Making outbound connection to /105.228.54.204:17465
  Making outbound connection to /88.166.214.197:36758
  Making outbound connection to /68.82.89.225:59453
  Making outbound connection to /104.136.223.59:29174
  Making outbound connection to /93.22.232.177:12452
  Making outbound connection to /89.156.214.35:20689
  Making outbound connection to /31.52.109.98:35094
  Making outbound connection to /202.90.82.113:32869
  (LS 2) Outbound connection fail: end of stream on socket read
  Making outbound connection to /73.200.42.168:16646
  Making outbound connection to /88.122.20.104:36405
  Searching complete, 15 targets found
    Status: sessions=14, out_attempts=15, out_connect=15, 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,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
    Outbound,Seed,connected, hand sent, hand recv, bitf sent, bitf recv
    No incoming connections received, likely NAT problems
  Incoming routing destroyed for 6D0E9706A81CD0D08A13CC8918C5815778413A30

[ArronM]

The latest beta has some changes that should help get Vuze running if it is a port issue such as that with Hola - see http://dev.vuze.com/ for the latest beta and manual installation instructions.

We've also fixed up the installer to detect whether other apps are using our port, and pick another one. So, in theory, one can re-install Hola. It will take port 6880. Then re-install Vuze, and the vuze installer will pick port 6881.

But honestly, I haven't heard many good things about Hola in the press lately, so people might be better off (and download faster) without it :)