I think you are stuck with browser hacks. The problem is that the
certificate needs to contain the hostname for the individual site which
is then used to check with DNS for that hostname to see if it matches
the IP.
You might have been able to circumvent it by using a wildcard
certificate and internal dns to resolve something like
192-168-1-1.pcswin.com, but then you would have to access the radios
with a longer name rather than by IP. But with the 5.6.4+ firmware I'm
not even sure if you can replace the certificate on the radio and have
it survive a reboot.
On 02/03/2017 09:04 AM, Steve Barnes wrote:
Having several thousand UBNT devices that use HTTPS, is there any way to get
around the: Your Connection is not private, then clicking advanced and then
Proceed to 10.0.0.1 (unsafe).
Some I have turned the HTTPS off but would like the extra security when doing
updates and the like.
I have 6 techs and 10 systems that access all these and wanted to know if there
was a work around.
Steve Barnes
Wireless Operations Manager
New Lisbon Broadband
NLBC.COM
PCSWIN.COM
765-584-2288 ext:1101
_______________________________________________
Ubnt_users mailing list
[email protected]
http://lists.wispa.org/mailman/listinfo/ubnt_users
_______________________________________________
Ubnt_users mailing list
[email protected]
http://lists.wispa.org/mailman/listinfo/ubnt_users
