Azsrmc closes connection

Help
Flow
2009-09-29
2013-01-31
  • Flow
    Flow
    2009-09-29

    My Azsrmc (1.0.0) installation stops working after a while.
    The Client says that SSL wouldn´t be supported by the Server, but it has worked before. Also a telnet connection to the default port is made but gets immediately closed.
    I found no error messages at the azureus console.

     
  • Flow
    Flow
    2009-11-05

    A hint where to look for errors would be nice…
    Still the windows azsmrc clilent claims that the server wouldn´t support SSL. But the option is checked in the azsmrc plugin preferences. Also the SSL cert is created and a ".keystore" file exists

    And yes, I tried to restart azureus ;)

     
  • Is there also the note that SSL is supported should be in  in the azsmrc plugin prefs

     
  • Flow
    Flow
    2009-11-05

    is there….

     
  • Flow
    Flow
    2010-01-19

    I am stil having this problem. Also I checked for the .keystore file. I exists and looks valid.

    ~/.azureus $ keytool -list -keystore .keystore
    Enter keystore password:
    *****************  WARNING WARNING WARNING  *****************
    * The integrity of the information stored in your keystore  *
    * has NOT been verified!  In order to verify its integrity, *
    * you must provide your keystore password.                  *
    *****************  WARNING WARNING WARNING  *****************
    Keystore type: JKS
    Keystore provider: SUN
    Your keystore contains 1 entry
    azureus, Nov 5, 2009, PrivateKeyEntry,
    Certificate fingerprint (MD5): 9A:86:A2:65:A1:EF:90:94:A4:C5:78:80:EB:DA:5E:66
    

    Can someone point me to the right direction where to look next?

     
  • Flow
    Flow
    2010-01-25

    I was able to isolate the problem to the azsmrc client. The Azureus Plugin itself works flawless, as entering the the URL auf the AzSMRC Plugin in a browser with https shows the webUI. Also the Firefox Plugin http://www.alexisbrunet.com/ is able to send torrents via https.
    So this seems to be a Problem with the AzSMRC client (or a stupid user error) ;)

     
  • Flow
    Flow
    2010-01-25

    Here is some debug output from AzSMRC remote control:

    [7:36:13.427] {lbms.azsmrc : DEBUG} Connect!
    [7:36:13.429] {lbms.azsmrc : DEBUG} Changing Timer: GUI mode
    [7:36:13.429] {lbms.azsmrc : DEBUG} Connection State: 1
    [7:36:13.430] {lbms.azsmrc.client : DEBUG} Transaction Started
    [7:36:13.431] {lbms.azsmrc.client : DEBUG} Transaction Started
    [7:36:13.431] {lbms.azsmrc.client : DEBUG} Transaction Committed (8 items)
    [7:36:13.431] {lbms.azsmrc.client : DEBUG} Client connection already established, postponed transfer.
    [7:36:13.719] {lbms.azsmrc : DEBUG} Trusting Certificate: https://xxx.xxx:49009/process.cgi
    [7:36:13.722] {lbms.azsmrc : DEBUG} Connection State: -1
    [7:36:13.725] {lbms.azsmrc : WARN} Connection failed 1 times, delay: 30sec
    [7:36:13.726] {lbms.azsmrc : DEBUG} Changing Timer: GUI mode
    [7:36:13.734] {lbms.azsmrc : DEBUG} Disconnect!
    [7:36:13.734] {lbms.azsmrc : DEBUG} Connection State: 0
    [7:36:13.748] {lbms.azsmrc : ERROR} Connection Error: Server doesn't support SSL.
    
     
  • Flow
    Flow
    2010-01-28

    After digging into the source, I found the Problem:
    AzSMRC creates the ".cert" file in its installation directory, but under Vista (and Win7 I suppose) the java app has no rights to create new files. I gave the user group full access to the install directory and now the SSL connection is workig.

    I just found that there is already a issue in the AzSMRC tracker. Should have locked there first. do´h ;-)