This is pretty much a random bug which will make it difficult to troubleshoot on the servers / host routers.

I ran into this today. First I was connected via my VPN and I was getting this message:
Connection Error (SSLHandshakeExecption: Remote host closed connection during handshake, SSL peer shut down incorrectly)

I restarted Vuse and the errors still happened. I then exited Vuse and disabled my VPN. Next I was getting the Timeout error. I shut down Vuse and enabled my VPN again and I had the Timeout error. I restarted Vuse again and it worked.

I know how hard it is to troubleshoot an issue like this when you can not reliably reproduce the error. I wish the Tech team good luck in tracing this bug.

Seems to be working for me as well.

UPDATE: After working for two torrents, all my trackers went "Connection timed out:connect" and trying a third torrent had the SSL Connect error for 3 tries, then started working again.  It seems to be a bit spotty.  Working sometimes and not other times.

I have been having a problem for a few weeks where using the "Quick Connect" on NordVPN in my Vuze will have the "Tracker Status" show up as "Connection Error (SSL Handshake)".  This is happening for most of the connections I am making, both for Seeding and trying to Download.

I am going to try the NordLynx and see if that helps any.

UPDATE: I switched to NordLynx and still have the "Connection Error (SSL Handshake)" error.

Hi,

I have the same problem, but I found something that helps get rid of the errros on many of the torrents.
It took some time, but by doing some network captures I think I found the solution.  I saw that some tracker checkes worked and other did not.  Comparing the requests I found that the working requests were on a single torrent, while the failed requests all had multiple torrent requests in them.

I found that the following change should work:

• Open the 'Options' page
    - 'Tools' - "Options'.
• Expand the 'Tracker' section.
• Click on the 'Client' sub section.
• Check the 'Disable per-tracker scrape aggregation (can help with trackers that report 'URL too long (414) errors)'
• Click 'Save'
• Restart Vuse (azureus)

The tracker status sould now work.  It may take longer as it is making single reqeusts, but they should work.

It seems that instead of returning the "414 - URL Too Long" error the system is just returning the "404 - Not Found" error.  The cause is the same, the URL that Vuse is sending when using aggregation is too long for the system to understand, and it fails the request.

Please let me know if this worked for you or if you had any issues with the instructions.

I have noticed that is still occurs at times, but it's better now.

Thanks,
Rydar

I have had this same issue for a while.  I have not been able to trace the cause yet, but I am trying to find it.  I do know that I seem to get the correct information if I just set all my torrents to queue and use my seeding rules.  It looks like when I do this Azureus will occationaly make a real connection to get the latest seeder / leecher counts.

Which version of Azurus are you using?