rg65 Posted January 29 Posted January 29 For the last month or so I have been getting this error. It is on my ISY (5.3.4). It is getting more and more frequent. I have tried the following but the error keeps on showing up: Cleared Java Cache Deleted and reinstalled java Replaced microSD card (following procedure that is documented and restored from an old backup that was known to be good) Moved the ISY to the same network switch as well as a different switch Replaced ISY power supply Pulled out some of my hair. The error is: Socket Open Failed javax.net.sslSSLHandshakeException: Remote host terminated the handshake I know the ISY isn't really supported and I will eventually replace it with and Eisy, but they are backordered. Does anyone have any ideas what could cause this? Thank you in advance!
Techman Posted January 29 Posted January 29 Are you leaving your admin console open for an extended period?
rg65 Posted January 29 Author Posted January 29 I have been opening it up in the morning to see if this error occurs. I don't think it is open for hours at a time though. I'll shut it down and see if it still shows up. Thank you!
Geddy Posted January 29 Posted January 29 6 hours ago, rg65 said: Does anyone have any ideas what could cause this? Are you running any anti-virus or firewall software (other than Windows default programs)? Turn those completely off and try again. Maybe after disabling you should clear the cache, delete old start.jnlp/admin.jnlp files download fresh IoX Launcher from UD site ("My ISY" on top right) run new start.jnlp and accept any java alerts What address are you using in the ISY Finder window to access the ISY994? Are you using a local IP or Portal connection? When do you get this error? When logging in or after the window has been open (a while - hours)? Admin console is not designed to be open 24/7. Have you set any "funky" settings in Java to be high security? Make sure you're running "generic" java downloaded from https://www.java.com/en/download/ (current version is Version 8 Update 401).
rg65 Posted February 11 Author Posted February 11 Thank you for the replies! I gave up and switched over to a new Polisy I had not implemented yet and no longer have the issue.
Recommended Posts