apostolakisl Posted December 10, 2012 Posted December 10, 2012 Originally I posted this with the 3.3.5 update, but I think it is better posted here, even though it is a 3.3.5 new feature. I set the HTTPS Client settings via dashboard to: TLS 1.0, Strength Medium I set the Elk configuration via the admin console to: 2601, checked the SSL box, and the "enabled" box, then saved it. As soon as I hit save, a few seconds later the ISY lost comm with Elk, then it said it got it back, but it didn't actually do anything, and furthermore the ISY stopped working as an Insteon controller and dragged to a near standstill when navigating through the admin console. My Elk is using the default port 2601 for secure connection and I did confirm that on the xep console. Upon returning to an unchecked SSL box, and port 2101, and doing a reboot of ISY, all is functioning normal again.
apostolakisl Posted December 11, 2012 Author Posted December 11, 2012 Ideas? Am I doing something wrong or is the SSL function still a work in progress?
Michel Kohanim Posted December 12, 2012 Posted December 12, 2012 Hello apostolakisl, Please try this … In ElkRP, on the M1XP Setup screen, under the Passwords tab, try deleting all usernames/passwords there, SEND to the M1XEP, let it reboot, and try to connect securely again. With kind regards, Michel
apostolakisl Posted December 16, 2012 Author Posted December 16, 2012 Just loaded 3.3.6 and deleted the m1xep authentication item you indicated. All seems to be working at first check.
Michel Kohanim Posted December 17, 2012 Posted December 17, 2012 Hi apostolakisl, thank you. We should have that supported shortly. With kind regards, Michel
Recommended Posts
Archived
This topic is now archived and is closed to further replies.