Upcoming Maintenance Alert:

The UBNT Community will be upgraded at 5pm MDT on April 25th. During this time the community forums will be set to read-only status.

Learn more

×
Reply
New Member
Posts: 20
Registered: ‎07-18-2012
Kudos: 11
Accepted Solution

NanoBeam 5AC 19 8.3 to UNMS 0.8.0 - lws_ssl_client_connect2 failed

Tried upgrading a few of my NanoBeam's to 8.3 to try them with UNMS, added the same key that has worked with my EdgeMax units but receive the following error:

 

Sep 22 00:10:30 udapi-bridge[904]: connection error (dns.name.redacted:443): lws_ssl_client_connect2 failed
Sep 22 00:10:50 udapi-bridge[904]: connecting to dns.name.redacted:443

Accepted Solutions
Ubiquiti Employee
Posts: 546
Registered: ‎05-24-2016
Kudos: 341
Solutions: 70

Re: NanoBeam 5AC 19 8.3 to UNMS 0.8.0 - lws_ssl_client_connect2 failed

@nathanielban

Hi Nathaniel, you don't have a correct time on your device: Sep 22 00:10:30. It's not possible to verify SSL certificate without it. Could you please turn on NTP or fix your device time? There will be UI validation for this situation in the next FW. Plus you should copy UNMS key (connection string) from UNMS not from other devices. Depending on your EdgeMAX FW it could work but from 1.9.7beta1+ all devices have unique keys. 

View solution in original post


All Replies
Ubiquiti Employee
Posts: 546
Registered: ‎05-24-2016
Kudos: 341
Solutions: 70

Re: NanoBeam 5AC 19 8.3 to UNMS 0.8.0 - lws_ssl_client_connect2 failed

@nathanielban

Hi Nathaniel, you don't have a correct time on your device: Sep 22 00:10:30. It's not possible to verify SSL certificate without it. Could you please turn on NTP or fix your device time? There will be UI validation for this situation in the next FW. Plus you should copy UNMS key (connection string) from UNMS not from other devices. Depending on your EdgeMAX FW it could work but from 1.9.7beta1+ all devices have unique keys. 

Highlighted
New Member
Posts: 20
Registered: ‎07-18-2012
Kudos: 11

Re: NanoBeam 5AC 19 8.3 to UNMS 0.8.0 - lws_ssl_client_connect2 failed

This fixed it, unfortuantely I was forced to roll back due to unrelated issues. 

Reply